-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ENOENT: no such file or directory" with scoped package names #1
Closed
Comments
Thanks for the detailed description. I'll try to fix it tomorrow |
nicojs
added a commit
that referenced
this issue
Jun 22, 2017
* Add support for scoped packages: @scope/name -> scope-name-x.x.x.tgz * Add an integration test and unit test for this fix. Fixes issue #1
nicojs
added a commit
that referenced
this issue
Jun 22, 2017
* Add support for scoped packages: @scope/name -> scope-name-x.x.x.tgz * Add an integration test and unit test for this fix. Fixes issue #1
Its released in v0.4. Could you verify it works? |
Working. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A package with the name @scope/module will be packed by
npm pack
to scope-module-version.tgz.install-local then triess to look for %TEMP%/@scope/module-version.tgz, when
npm pack
has created %TEMP%/scope-module-version.tgz.The text was updated successfully, but these errors were encountered: