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
mkdir rimraf-test
cd rimraf-test
npm init -y
npm i rimraf -D
npx rimraf --help
<nothing>
Interesting part: directly calling node node_modules/rimraf/dist/esm/bin.mjs --help works.
I'm guessing it's a file mode thingy. If the mjs is generated, npm i didn't get to set its mode, like it does for bin entrypoints.
Possible fix, create a static bin entry that imports that file. e.g. https://github.com/wixplosives/pleb/blob/main/bin/pleb.js (see that GitHub says "executable file")
The text was updated successfully, but these errors were encountered:
Not file mode, was detecting main-module status incorrectly.
I could have sworn that node realpath'ed argv[1], but I guess it doesn't do that anymore, or my brain is just lying about history, it does do that sometimes.
Noticed calls to rimraf are no-op. Even --help.
Interesting part: directly calling
node node_modules/rimraf/dist/esm/bin.mjs --help
works.I'm guessing it's a file mode thingy. If the mjs is generated,
npm i
didn't get to set its mode, like it does for bin entrypoints.Possible fix, create a static bin entry that imports that file. e.g. https://github.com/wixplosives/pleb/blob/main/bin/pleb.js (see that GitHub says "executable file")
The text was updated successfully, but these errors were encountered: