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
With command like npm publish /path/to/tarball/from/npm-pack.tgz, npm will error with:
$ npm publish ./dr-js-core-0.4.0-dev.8.tgz
npm ERR! code ENOTDIR
npm ERR! syscall open
npm ERR! path ./dr-js-core-0.4.0-dev.8.tgz/package.json
npm ERR! errno -20
npm ERR! ENOTDIR: not a directory, open './dr-js-core-0.4.0-dev.8.tgz/package.json'
npm ERR! A complete log of this run can be found in:
npm ERR! /home/dr/.npm/_logs/2020-10-26T08_40_37_321Z-debug.log
This was something we intentionally dropped support for, but not for any strong principled reason, just that we weren't sure anyone was using it. Happy to bring support for that back, since I have some other small fixes to do in libnpmpublish anyway.
Current Behavior:
With command like
npm publish /path/to/tarball/from/npm-pack.tgz
, npm will error with:And the log file:
[/home/dr/.npm/_logs/2020-10-26T08_40_37_321Z-debug.log]
Expected Behavior:
Should just publish the tarball, currently npm seem to think this is a folder to run
npm pack
with.Steps To Reproduce:
Should be able to test with:
mkdir -p ./test-npm-publish cd ./test-npm-publish npm init --yes npm pack npm publish test-npm-publish-1.0.0.tgz
Environment:
The text was updated successfully, but these errors were encountered: