1.0
Closed Dec 20, 2019
100% complete
Support the launch of Bazel 1.0 by having all dependencies of Bazel for Web be stable APIs
- Provider API for JS rule interop
- (?) Figure out if we want to keep our custom module loader, vs. an action that lays out a runtime
node_modulesdirectory that works with the standard module loader - user facing APIs (BUILD files) are stable and don't need changes
Support the launch of Bazel 1.0 by having all dependencies of Bazel for Web be stable APIs
- Provider API for JS rule interop
- (?) Figure out if we want to keep our custom module loader, vs. an action that lays out a runtime
node_modulesdirectory that works with the standard module loader - user facing APIs (BUILD files) are stable and don't need changes
This milestone is closed.
No open issues remain. View closed issues or see open milestones in this repository.