List view
Regular cadence for major releases
Due by February 1, 2022•14/14 issues closedNext breaking changes for summer 2021, following our 6mo major release cadence
Due by July 2, 2021•14/14 issues closedCurrently a dumping ground for breaking changes we want to make post-2.0
No due date•13/13 issues closedWith 1.0 released and the holidays over, it's time to start planning our 2.0 milestone (and set a target date). Thanks to everyone who contributed to 1.0 and to our users for stress testing us! We got a lot in for 1.0 but we also left a lot on the table to achieve for 2.0. Major themes proposed for 2.0: watch mode for all, replacement ts_library & ng_module rules, yarn workspaces, better examples of using generated bin rules such as jest_test & mocha_test, improved docker support.
No due date•29/29 issues closedPlans to ship Bazel support as a stable API for Angular CLI users. See https://dev.to/bazel/angular-bazel-leaving-angular-labs-51ja
No due date•2/2 issues closedThings we might do sometime
No due date•8/8 issues closedTake away the "experimental" label. We think we are done with big breaking changes. Broadly, this includes: - Lay out the `node_modules` in the workspace identically to how the user would if running `npm`/`yarn` directly - Guidelines for publishing npm packages, ensuring that the accompanying starlark code is loaded at a matching version - Remove the extra `yarn_install`s in `node_repositories.bzl` which take extra install time
Due by May 22, 2019•5/5 issues closedSupport 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_modules` directory that works with the standard module loader * user facing APIs (BUILD files) are stable and don't need changes
Due by December 11, 2019•32/32 issues closed