how to ignore symlink when use lerna bootstrap
See original GitHub issueWhen run lerna bootstrap
, lerna will create symlink for related dependencies, now I just want to use real npm install
but not symlink for dependencies.
Is there any method working for this scene?
Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
@lerna/bootstrap - npm Package Health Analysis | Snyk
Webstorm locks up when circular symlinks are present. To prevent this, add node_modules to the list of ignored files and folders in Preferences...
Read more >Can you undo a lerna bootstrap? - Stack Overflow
I've run a lerna bootstrap --hoist. I now want to undo this and unlink all of the created symlinks. Is there a command...
Read more >Starting with Monorepos using Lerna - Joel H. Gomez Paredes
Create a repository (use the common gitignore for nodejs) and clone it · Executes npm init · Create a folder called packages ·...
Read more >Why Lerna and Yarn Workspaces is a Perfect Match for ...
json files located at each project's root folder. Thereby, these tools make it obsolete to manually create symlinks or use "low-level" npm link ......
Read more >lerna - npm
Webstorm locks up when circular symlinks are present. To prevent this, add node_modules to the list of ignored files and folders in Preferences ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This might help. https://github.com/lerna/lerna/issues/1889
Hi Folks 👋
You will have seen in our message above that we at Nrwl are working really hard to bring the lerna repo up to date with what matters most to its community in June 2022.
As previously stated in that message, because we have not heard from the original author of this issue within the last 14 days, we are now automatically closing it.
If any users, including the original author, are still impacted by this issue then we still want to hear from you!
All we ask is that you first update to the latest lerna (
5.1.4
at the time of writing) to make sure it is still reproducible, and then fill out one of our new issue templates, providing all the requested details which apply to your situation:https://github.com/lerna/lerna/issues/new/choose
Many thanks again! 🙏
P.S. Over and above getting to grips with the repo, we have also been hard at work launching a new website, resolving all vulnerabilities, merging exciting new features and reigniting community PR contributions! 🚀
You can read our recent blog post to learn more about what we’ve been up to: https://blog.nrwl.io/lerna-5-1-new-website-new-guides-new-lerna-example-repo-distributed-caching-support-and-speed-64d66410bec7