Skip to content
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

Binary exported by workspace package causes "bolt install" failure #126

Closed
bengummer opened this issue Jan 18, 2018 · 5 comments
Closed

Comments

@bengummer
Copy link
Contributor

Title Description
Version 0.19.2
Type Issue
node 8.9.4
Operating System macOS 10.13.2
Short Description Binary exported by workspace package causes "bolt install" failure
Detailed description If I have a bolt workspace containing a package that has a "bin" entry in its package.json file, and also have another package in the same workspace that depends on the first bin-exporting package, then running bolt results in an error.

The error displayed is:

$ bolt
⚡️   bolt v0.19.2 (node v8.9.4)
🔎   [1/3] Validating project...
📦   [2/3] Installing project dependencies...
yarn install v1.3.2
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
✨  Done in 0.14s.
🔗   [3/3] Linking workspace dependencies...
error my-bin is linked to a location outside of project node_modules: ../../packages/my-bin/index.js

Demo repo here: https://github.com/bengummer/bolt-binary-issue-demo

yarn install works in the demo repo, bolt install doesn't

@lukebatchelor
Copy link
Member

Ah. Thats interesting. We probably need to either symlink workspace's bins to the project bin, then dependents symlink to that, or modify this check to not happen with internal deps.

Probably option 2

@bengummer
Copy link
Contributor Author

Yeah the following tests looks like they test internal dependencies so i'm not sure why my demo repo has the issue.

https://github.com/boltpkg/bolt/blob/41e1ed61b2/src/utils/__tests__/symlinkPackageDependencies.test.js#L104

@jamiehodge
Copy link

I ran into this issue as well

@jamiebuilds
Copy link
Member

Moving to #157

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants