-
Notifications
You must be signed in to change notification settings - Fork 101
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
bug with meta npm link --all #292
Comments
I ended up writing this script as a workaround It runs a command in all project to link all the projects #!/usr/bin/env node
const metaLoop = require('meta-loop')
const fs = require('fs')
// build the command to link all projects
const {projects} = JSON.parse(fs.readFileSync('./.meta').toString())
const command = `npm link ${Object.keys(projects).map(project => project.split('/').pop()).join(' ')}`
console.log(`meta exec "${command}"`)
metaLoop(command)
console.log('done') |
Was looking for a solution to this, thank you @lexoyo. From what I could find, it seems related to the code in the https://github.com/mateodelnorte/meta-npm repository (maybe this file). Since you've already worked around it, and are most familiar with the problem+solution, you could probably make a PR that fixes it for good and get it integrated. |
Hi @acrois |
I can review a PR @lexoyo |
Hi |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Yep
…On Sun, Apr 3, 2022 at 9:00 PM Alex Hoyau ***@***.***> wrote:
Hi @acrois <https://github.com/acrois>
I don't really remember but I guess I could check it out
@mateodelnorte <https://github.com/mateodelnorte> are you still around
and accepting PRs?
—
Reply to this email directly, view it on GitHub
<#292 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEHOXZDSEUHEXNRHSWNKR3VDJSOFANCNFSM5Q4GNHCA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
🐛 Bug Report
When I run
meta npm link && meta npm link --all
my projects do not build anymore because theirnode_module/.bin
folders are not populated anymore with all the scripts they needTo Reproduce
Steps to reproduce the behavior:
=> missing scripts for libs that are not linked
Expected behavior
.bin
should contain all the same script as before linking, except for the linked libsThe text was updated successfully, but these errors were encountered: