angular/.ng-dev
Paul Gschwendtner f4fd488d4d build: update tooling to use new entry-point for dev-infra exports (#45206)
Previously, dev-infra only bundled the CLI with all its dependencies, while
we still also kept all bundled dependencies in the `dependencies`. This basically
meant that the CLI bundling did not provide any value at all.

We fixed this upstream and now dependencies are still bundled, but no longer
also declared as `dependencies`. We also stopped shipping deep JS files, only
shipping the bundles now.

As part of this deep file removal, we introduced a runtime entry-point for
exports/types. This one will also benefit from the bundling and it will be
predictable what symbols dev-infra consumer projects rely on (allowing us to
also have an API guard or something in the future).

PR Close #45206
2022-02-28 17:38:26 +00:00
..
caretaker.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
commit-message.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
config.ts build: update to the latest version of @angular/dev-infra-private (#43541) 2021-10-04 10:51:01 -07:00
format.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
gitconfig build: adding shared .ng-dev/gitconfig file for convenience and consistent git config (#37951) 2020-07-13 09:23:03 -07:00
github.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
pullRequest.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
release.ts build: update tooling to use new entry-point for dev-infra exports (#45206) 2022-02-28 17:38:26 +00:00
tsconfig.json build: check .ng-dev tool configuration in CI (#43322) 2021-09-02 21:18:36 +00:00