* Revert "feat(angular): add support for a target Builder (#4903)"
This reverts commit a78fe65d81600e2f1b522722b6ce6374b8c652d3.
* chore(angular): disable failing test
* feat(angular): upgrade Angular to v12.0.0-rc.3
* feat(angular): target Nx v12.4.0-beta.0 for Angular v12.0.0-rc.0 upgrade
* fix(angular): use defaultConfiguration if no other configuration is passed
* cleanup(angular): sync migration folder name to target version
* fix(repo): creating custom schema flattener for docs
* chore(repo): amend yarn.lock
* feat(angular): update angular storybook to use webpack 5
* fix(angular): add legacy peer deps for angular+jest
* fix(angular): move migrations to 12.3.0-rc.0
Co-authored-by: Zack DeRose <zack.derose@gmail.com>
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* feat(core): add --discardExistingLintConfig option to lint conversion generators
* fixup! feat(core): add --discardExistingLintConfig option to lint conversion generators
* chore(core): address PR feedback
* fix(linter): properly store defualts for converting tslint to eslint
* fix(linter): fix tests for set defaults
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
Before, the webpack-browser builder always directly scheduled @angular-devkit/build-angular:browser. Now, one can configure an
optional buildTarget that is scheduled instead. If this option is not used, the former behavior -- directly scheduling
@angular-devkit/build-angular:browser -- takes place.
* feat(linter): convert-tslint-to-eslint generators
* fix(core): remove generators in collection for ng and nest
* fix(core): update tao to support mixed generators and schematics
* fix(core): update tao to support mixed generators and schematics
* fix(core): address some PR feedback
* fix(core): fix snapshots after syncing up with master
* feat(core): store user preference for removeTSLintIfNoMoreTSLintTargets
* fix(linter): unit tests
* feat(core): apply root tslint.json conversion to root .eslintrc.json
The builder currently supports skipping the serve step by passing an empty value
for
devServerTarget. This is not intuitive and makes configuring this via the command line messy.
This
flag has the same behavior as passing an empty devServerTarget but is more user-friendly.
This
option can be useful for CI purposes where applications are previously built and want to use
the
same configuration for e2e testing but the serve step is unnecessary.
ISSUES CLOSED: #3744
* fix(nextjs): update babel setup to better support next apps
* fix(testing): remove babel-jest.config.json used in jest.config.js
- Fix `@nrwl/web/babel` to support Jest as well
