-
Notifications
You must be signed in to change notification settings - Fork 16
Skip some directory #12
Comments
Not at the moment, everything in the workspace will be installed by npm-workspace. |
I have currently 2 use cases: 1/ Speed up deployments. 2/ Simplify deployment.
My package.json would have this form: {
"name": "my-project",
"version": "1.0.0",
"dependencies": {
"npm-workspace": "^0.2.1"
},
"scripts": {
"postinstall": "npm-workspace install",
"clean": "npm-workspace clean"
}
} And installation would be in one single line: npm install I don't know your plans about workspace.json structure but we could imagine something like that: {
"links": {
"my-subproject-1": "my-subproject-1",
"my-subproject-2": "my-subproject-2"
},
"excludes": [
".",
"my-subproject-3"
]
} |
👍 I too think this would be a very helpful feature. My use case is I have all work projects in one root directory with the workspace.json. They are all private npm packages, but a few of them are public. Those public ones I don't need npm-workspace installed each time, but I still need the ability to npm-workspace install them when I do upgrade those public packages either for node version or whatever and being able to link them to the private packages for testing is extremely useful. |
Hi,
Is there currently a way to skip some dir (root dir or module) from npm-workspace process?
I didn't find it in code source.
Thanks in advance,
Mathieu
The text was updated successfully, but these errors were encountered: