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

refactor(builtin): npm_umd_bundle no longer allows directory sources #3010

Merged
merged 2 commits into from
Oct 11, 2021

Conversation

alexeagle
Copy link
Collaborator

We plan to change behavior under exports_directories_only so that they produce TreeArtifacts. They will therefore be a subfolder of the real package.
npm_umd_bundle is too hard to keep working with exports_directories_only because it relies on loading npm packages without the linker.

BREAKING CHANGE:
npm_umd_bundle users cannot use exports_directories_only

We plan to change behavior under exports_directories_only so that they produce TreeArtifacts. They will therefore be a subfolder of the real package.
npm_umd_bundle is too hard to keep working with exports_directories_only because it relies on loading npm packages without the linker.

BREAKING CHANGE:
npm_umd_bundle users cannot use exports_directories_only
It no longer works since npm_umd_bundle can't work with exports_directories_only.
Note: we have other examples that provide integration test coverage for exports_directories_only
@alexeagle alexeagle merged commit f31976e into bazel-contrib:5.x Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants