-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Feature Request: NPM --no-bin-links #929
Comments
this is a blocker for me with a vm on windows |
facing the same issue ubuntu vm on Windows host I bypass the problem with --no-bin-links when using npm. yarn fails with:
|
Please use GitHub reactions and not add noise with |
Created #1651 to fix this, pending approval. |
* master: (66 commits) Add --no-bin-links flag - fixes yarnpkg#929 (yarnpkg#1651) Add option to change the prefix of the global bin folder - fixes yarnpkg#630 (yarnpkg#1654) patterns -> filteredPatterns Add helpful nudge to yarnpkg/rfcs on issue template (yarnpkg#1650) Change reporter.log to console.log in generate-lock-entry command - fixes yarnpkg#644 (yarnpkg#1652) Fixed add command flag (yarnpkg#1653) Nested executables fix (yarnpkg#1210) Added short-flags for yarn add (yarnpkg#1618) Add name lookups to ls command - fixes yarnpkg#1599 (yarnpkg#1643) Disable flaky secureUrl test (yarnpkg#1644) Add unit tests for `yarn why`. (yarnpkg#1544) Refine flow type for config.generateHardModulePath (yarnpkg#1642) Use ~/Library/Caches as default cache location on OSX - fixes yarnpkg#1637 (yarnpkg#1638) Update aliases.js (yarnpkg#1635) Update aliases.js (yarnpkg#1634) Add webhook to archive AppVeyor build artifacts (yarnpkg#1631) Attempt to fix failing Circle CI builds (yarnpkg#1629) Adding 'yarn global upgrade'(Issue yarnpkg#776) (yarnpkg#1616) Show error message in stdout. (yarnpkg#1502) Nicer permission errors when trying to write global binaries - fixes yarnpkg#1578 (yarnpkg#1592) ...
is there a way to set this option in |
@kittens I'm using latest yarn on an ubuntu 14.04 docker image running under Windows 10 Home on VirtualBox. I think I'm facing a similar issue: Running a normal EDIT: I'm sorry, I missed out on your comment about about using |
I still get this problem. I spawn a child_process and run the following command
And I still get the error
I also tried
and I get the same error Any suggestions? |
Host OS: Windows 10
Guest OS: Fedora 24
Hypervisor: VirtualBox 5.1.6
When running
yarn install
inside a VirtualBox Shared Folder, it will fail with an error similar to the following:Even though the Linux guest supports symlinks, they are unsupported inside VirtualBox Shared Folders.
Npm supports the
--no-bin-links
option to avoid using symlinks (which makes things slower but more reliable in this situation).To be clear, this is not an issue in Npm or Yarn but a deficiency in VirtualBox (that was supposed to be fixed but has resurfaced).
The text was updated successfully, but these errors were encountered: