BUG: CLI-getting "axe: command not found " even after successfully installed CLI

[padmavemulapati]

Product

cli

Product Version

4.7.4-f03670b.0

Latest Version

• I have tested the issue with the latest version of the product

Issue Description

Expectation

After @axe-core/cli installed successfully, axe --help or axe with url should give respective output

Actual

MacBook-Pro:cli dq_user$ axe --version
bash: axe: command not found
MacBook-Pro:cli dq_user$ axe --help
bash: axe: command not found

How to Reproduce

1. Created a Directory and created a package.json using npm init -y
2. Insalled axe-core/cli canary version ('npm install @axe-core/cli@next) (Installed gobally using -g and locally both)
3. Tried to run the command axe --version to make sure correct canary is installed

Issue: its giving

MacBook-Pro:cli dq_user$ axe --version
bash: axe: command not found
MacBook-Pro:cli dq_user$ axe --help
bash: axe: command not found

Additional context

Tried in Windows and MAC both , issue is there on both OS

Environment:

Label	Value
Product	axe-core-npm
Version	4.7.4-f03670b.0
OS-Details	_MAC- Intel Core i7 - 11.6.8 & Windows11 _
BrowserDetails	Chrome Version 117.0.5938.88 (Official Build) (64-bit) & Firefox 117.0

[padmavemulapati]

Verified with the latest fix, now not getting axe not found error.

Environment:

Label	Value
Product	axe-core-npm
Version	4.7.4-62fd241.0
OS-Details	_MAC- Intel Core i7 - 11.6.8 & Windows11 _
BrowserDetails	Chrome Version 117.0.5938.88 (Official Build) (64-bit) & Firefox 117.0

[davereid]

We are still seeing this bug with the recent 4.8.0 release as of three hours ago. Do we need another release with this fix?

[davereid]

You can see on https://www.npmjs.com/package/@axe-core/cli?activeTab=code that the dist directory is still missing. I think this issue needs to be re-opened.

[davereid]

I can also validate that https://registry.npmjs.org/@axe-core/cli/-/cli-4.8.0.tgz is missing the dist directory from the contents of the tarball.

[dbjorge]

Just confirming that we agree this affects 4.8.0 - we've begun a new release process for a v4.8.1 which will contain the fix for this, and we'll be investigating how to avoid this mismatch of which version gets QA tested vs released to prevent issues from accidentally escaping to production like this in the future.

[dbjorge]

Clarification for QA: the fix for this is already merged in #851, which would normally mean we'd have closed this issue. I'm leaving it open for the purposes of users being able to track the outage in the published version. We can close this once we've verified that npx @axe-core/[email protected] --help is available and working.

[padmavemulapati]

We have a similar ticket for windows , but when we set the PATH in environment variables it is working as expected. As @dbjorge said, once we have verified the patch release 4.8.1we can close this .

[dbjorge]

4.8.1 has been released. Verified that it fixes the issue:

> npx -y @axe-core/[email protected] --version
4.8.1