* chore(angular): support angular 13
Support Angular 13
chore(angular): support ng 13 next 11
chore(angular): upgrade tslib dep
chore(angular): update package and ng-packagr-lite executors to align with ng-packagr v13
chore(angular): update test snapshots with ts version
fix(angular): buildable lib tsconfig transform test
* chore(angular): sync ng-packagr changes to the package and ng-packagr-lite executors
* chore(angular): add migrations
* chore(angular): rxjs7
* feat(angular): check rxjs version to install
* feat(angular): update jest resolver to resolve esm
* chore(angular): fix version
* chore(angular): support jest-preset-angular
* fix(angular): tests
* fix(angular): fix e2e tests and add .angular to gitignore
* fix(angular): fix jest transformers ignore pattern
* fix(angular): fix node test
* fix(angular): fix workspace test
* fix(angular): import marble utils from jasmine-marbles instead of @nrwl/angular/testing
* feat(angular): update ngrx to 13.0.0-beta.;0
* fix(angular): temporarily skip test with pnpm
* fix(angular): bump jest-preset-angular to fix jest performance issues
* fix(angular): webpack-browser and server schema changes
Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* feat(core): standalone project configuration is default
* chore(core): changes to e2e tests
* fix(core): intuit projects when inside their directories when using project.json files
* chore(core): e2e changes
* fix(core): standalone configurations work with npm-project generator
* chore(core): e2e tests should use standalone configurations
* chore(core): e2e fixes per review
This commit checks if the target dev server supports the watch option before forwarding it to, this is relevant for running Cypress against dev server target that does not support this option, for instance "@nguniversal/builders:ssr-dev-server".
* 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>
- Single char alternation (e.g. a|b|c|d) in a RegExp can be simplified to use a character class ([abcd]) instead.
This usually also provides slightly better matching performance.
- Character escapes that are replaceable with the unescaped character without a change in meaning. Inside the square brackets of a character class, many escapes are unnecessary that would be necessary outside of a character class. For example the regex [\.] is identical to [.]
- If several qualified expressions occur after the qualifier having been checked for nullable, they can be replaced with optional chaining
* 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
