* 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): detect package manager used to invoke create-nx-(plugin|workspace)
When consumers create a new Workspace (or Plugin) using the create-nx-workspace (or
create-nx-plugin) generator, the package manager used to invoke the generator will be detected and
used as packageManager. For example: pnpx create-nx-workspace will use pnpm, yarn create
nx-workspace will use yarn. Explicit `--packageManager` flag will be priority over the detection.
* cleanup(core): reassign SELECTED_PM after each test run
* fix(core): augment args instead of hardcode --packageManager flag
* cleanup(core): use packageManagerLockFile instead of magic strings
* cleanup(core): fix typo in create-nx-workspace
* cleanup(core): ensure new workspace name for every test
* feat(core): detect package manager used to invoke create-nx-(plugin|workspace)
When consumers create a new Workspace (or Plugin) using the create-nx-workspace (or
create-nx-plugin) generator, the package manager used to invoke the generator will be detected and
used as packageManager. For example: pnpx create-nx-workspace will use pnpm, yarn create
nx-workspace will use yarn. Explicit `--packageManager` flag will be priority over the detection.
* cleanup(core): reassign SELECTED_PM after each test run
* fix(core): augment args instead of hardcode --packageManager flag
* cleanup(core): use packageManagerLockFile instead of magic strings
* cleanup(core): fix typo in create-nx-workspace
* cleanup(core): ensure new workspace name for every test
* fix(core): move detectInvokedPackageManager off of tao
Co-authored-by: Chau Tran <ctran@Chaus-MacBook-Pro.local>
* 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>
- 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
Yarn was wrongly interpreting `nxWorkspaceRoot` when current working directory was ending in backslash, for example `E:\` in Windows. This commit makes sure that `nxWorkspaceRoot` parameter uses only forward slashes that work in all cases.
Closes#4363
