sanguine

A node change did it for me, I installed `v16.14.0` via `nvm` and also downgraded `appium` to `2.0.0-beta.46` and it worked

> Hey there! You don't need to import `commands`. Add just this import to make the integration works: > > ```js > import "allure-cypress"; > ``` It doesn't work, the...

> Could you provide the process log? Do you see any runtime error? ``` 0 verbose cli /Users/sanguine/.nvm/versions/node/v18.14.0/bin/node /Users/sanguine/.nvm/versions/node/v18.14.0/lib/node_modules/npm/bin/npm-cli.js 1 info using [email protected] 2 info using [email protected] 3 timing npm:load:whichnode...

@dayaneCsantos check my comment below. if it works for you, help me vote for my answer on stackoverflow as well https://stackoverflow.com/questions/77067015/cypress-allure-reports-are-not-getting-generated/78487640#78487640

I eventually fixed this issue. The workaround is to downgrade to `v.2.14.0`. If you're installing for the first time install using `npm i -D [email protected]` else just change the version...

> Even following [#934 (comment)](https://github.com/allure-framework/allure-js/issues/934#issuecomment-2114032056), I get build errors: > > `Error: Cannot find module 'allure-cypress/commands' from '/e2e/cypress/support' at /e2e/node_modules/resolve/lib/async.js:46:17 at process (/e2e/node_modules/resolve/lib/async.js:173:43) at ondir (/e2e/node_modules/resolve/lib/async.js:188:17) at load (/e2e/node_modules/resolve/lib/async.js:69:43) at...

> The problem has been already resolved in the next `allure-cypress` version. Stay in touch to get information about the new releases! Looking forward to it

@RobertBattaglia use this for a workaround https://github.com/allure-framework/allure-js/issues/934#issuecomment-2114032056 until @epszaw releases the fix