You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I provided the reproduction with a local installation because it makes things easier to check.
I have the same behavior using a npm script calling fxparser in the project shared in the issue description.
Installing globally is worse: I got an error like this when I run the command in a directory where there is no package.json file. If there is a package.json file, I have the same behavior as when installing fxparser locally.
toma@myPC:~/fxp/GH_issue_735$ fxparser --version
node:fs:574
return binding.open(
^
Error: ENOENT: no such file or directory, open '/home/toma/fxp/GH_issue_735/package.json'
at Object.openSync (node:fs:574:18)
at Object.readFileSync (node:fs:453:35)
at file:///home/toma/.nvm/versions/node/v20.18.3/lib/node_modules/fast-xml-parser/src/cli/man.js:4:31
at ModuleJob.run (node:internal/modules/esm/module_job:234:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:122:5) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/home/toma/fxp/GH_issue_735/package.json'
}
Node.js v20.18.3
Did you try online tool?not relevant hereHave you checked the docs for helpful APIs and examples?not relevant hereDescription
Installing fast-xml-parser with the following package.json
The
fxparser
version is wrong: it should be 5.0.8Possible root cause
This behavior has probably been introduced in 8f6e089 to fix #718
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: