I want to try allure 3 but I'm getting a TypeError ERR_INVALID_ARG_TYPE

[cb-jarunmadhesh]

Hi I want to try allure3 awesome report.
So, I downloaded allure 3 by npm i -g allure
and ran npx allure generate test-results to generate the report.
While doing so, I'm getting this error:

can't read directory TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at validateString (node:internal/validators:162:11)
    at join (node:path:1175:7)
    at AllureReport.readDirectory (file:///Users/cb-it-01-1772/.nvm/versions/node/v20.10.0/lib/node_modules/allure/node_modules/@allurereport/core/dist/report.js:54:53)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async CAC.GenerateCommandAction (file:///Users/cb-it-01-1772/.nvm/versions/node/v20.10.0/lib/node_modules/allure/dist/commands/generate.js:8:5) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Version:

- npx allure -version                
allure/3.0.0-beta.9 darwin-arm64 node-v20.10.0

What am I missing here?

[epszaw]

Hey there. It's strange because I do the same thing and it works.

Even if the test results directory doesn't exist, I see another kind of error:

λ npx allure generate not-found-dir
/Users/epszaw/Code/allure3/packages/sandbox
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, opendir '/Users/epszaw/Code/allure3/packages/sandbox/allure-results1'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'opendir',
  path: '/Users/epszaw/Code/allure3/packages/sandbox/allure-results1'
}

Node.js v20.12.0

Could you provide more detail about the problem? Do you use allurerc.js config file, or you just try to run the command as is (it's ok to do that, it should work)? Does the test results directory exist?

[cb-jarunmadhesh]

Ohh is it!
I'm trying to run the command as is.. I just moved some test results into allure3 folder in path test-results.

Since you mentioned allurerc.js, when I ran that command from the root, I got this error:

node:internal/modules/esm/resolve:844
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'allure' imported from /Users/cb-it-01-1772/work/allure3/allurerc.mjs
    at packageResolve (node:internal/modules/esm/resolve:844:9)
    at moduleResolve (node:internal/modules/esm/resolve:901:20)
    at defaultResolve (node:internal/modules/esm/resolve:1121:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.10.0

Any idea?

Also, If I run the generate command with a path with no tests results, its generating an empty report.

[todti]

Hi, @cb-jarunmadhesh!

When you provide allurerc.mjs you should install Allure locally using npm or yarn, that's why you encountered the error above.

Please, provide all terminal commands you used and we will help you troubleshoot the issue.

[cb-jarunmadhesh]

Hi @todti
Yeah I did install allure both globally and locally.

1. installed it globally using npm i -g allure
2. Installed it locally using yarn install
3. used this command to generate the report: npx allure generate test-results
4. If I run the said command in step 2 from the root of the allure3 repo, I get this error:
   https://github.com/orgs/allure-framework/discussions/2915#discussioncomment-12421877
5. If I run it from elsewhere, I get this error:
   https://github.com/orgs/allure-framework/discussions/2915#discussion-8047395

[todti]

Inside allure3 repo

If you are trying to generate a report inside the Allure3 repository by copying your test result directory to the root of the repo (e.g., allure3/test-results) and then generating the report, follow these steps:

• yarn install
• yarn build
• yarn allure generate <pathToYourDir> for example yarn allure generate ./test-results

Note: In the root directory of the Allure3 repository, you will find the allurerc.mjs file, which contains reportName and other configuration options.
You can read more about how allurerc.mjs works in the README.md

---

Anywhere on your machine(real use case)

If you want to generate reports inside your own project (outside the Allure3 repository), use the following commands:

• npm i -g allure
• npx allure generate <YourDirWithTestResults>

[cb-jarunmadhesh]

@todti Followed whatever you said.. didn't work.. still getting the same error

[dutyfree123123123]

Also happens to me when trying to generate report. I installed it globally then tried to ran allure generate with the test results from junit5 project (no allurerc.js).

Running with version allure/3.0.0-beta.9 win32-x64 node-v18.18.0

can't read directory TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:405:5)
    at validateString (node:internal/validators:162:11)
    at join (node:path:429:7)
    at AllureReport.readDirectory (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/allure/node_modules/@allurereport/core/dist/report.js:54:53)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async CAC.GenerateCommandAction (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/allure/dist/commands/generate.js:8:5) {
  code: 'ERR_INVALID_ARG_TYPE'

[todti]

Hi, @dutyfree123123123 !
Please, provide all terminal commands you used and the correct directory path to the test results

[dutyfree123123123]

Path to results is C:\Users\Administrator\Desktop\junit5\build\allure-results
I ran inside build dir:
npm install -g allure
npx allure generate allure-results
Also happened if I use full path to results or surround with quotes
@todti

[epszaw]

Hey there! The fix is ready and will be available in the next release.

[epszaw]

The version is available – 3.0.0-beta.10

[cb-jarunmadhesh]

Great.. it works now.. thanks @epszaw

[epszaw]

No problem, you're welcome! :)