-
Notifications
You must be signed in to change notification settings - Fork 522
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
Exclude files with spaces in bazel-managed node_modules #213
Comments
I don't know how much flexibility you want to provide here, but if you want to expand the flexibility, you could add an exclude attribute to yarn_install and npm_install. Or, for even greater flexibility, you could add a build_file attribute. |
Actually we want to move the other way and allow any files to be valid labels. I think this is already the case in the latest Bazel, what version are you on?
|
I'm on 0.13.0. I'll try the latest and see how it goes. I've noticed you use self-managed node_modules in angular. Is that the approach you personally would recommend? |
I think I am wrong, the repro above isn't sufficient to show that spaces aren't allowed in labels - @hansl had the same issue late last week. Angular would like to switch to bazel-managed node_modules, I expect many projects would follow the same path of starting out more similar to web ecosystem, and as they adopt Bazel more, they'd be comfortable switching. The self-managed node_modules is really there to make the on-ramp simpler. |
Files with spaces are excluded in bazel-managed npm deps (those created with |
Fixes bazel-contrib#213 Closes bazel-contrib#218 PiperOrigin-RevId: 200227472
Fixes bazel-contrib#213 Closes bazel-contrib#218 PiperOrigin-RevId: 200227472
Several npm packages have spaces in file names. This breaks the bazel-managed node_modules. Adding a line like this to the exclude attribute should solve the problem:
The text was updated successfully, but these errors were encountered: