-
Notifications
You must be signed in to change notification settings - Fork 519
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
rollup_bundle should be a separate npm package #724
Labels
Milestone
Comments
See also #740 - this is the majority of the work for that |
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 5, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 9, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 9, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
alexeagle
added a commit
to alexeagle/rules_nodejs
that referenced
this issue
Sep 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
right now rollup is in build_bazel_rules_nodejs
before we go stable, it should be in
@bazel/rollup
on npm and be distributed independentlyThat lets rules_nodejs users avoid the extra weight, and also makes it less important for users to keep their WORKSPACE versions updated.
The text was updated successfully, but these errors were encountered: