* feat(testing): move jest config to .ts
move jest config and preset to ts files
ISSUES CLOSED: #8344
* fix(testing): update tests for jest.config.ts changes
update tests broken by renaming jest fils to ts files
The current implementation of the node executor resolves all npm
modules that are referenced by the application from the root
node_modules folder. This behavior leads to runtime errors if any of
the project dependencies requires a different version of a package
than the project itself.
For example, if we have a project that depends on `express` in version
`4.17.3` (which on the other hand depends on `path-to-regexp` version
`0.1.7`) as well as on `path-to-regexp` in version `6.2.0`. In such
case `express` will throw a runtime error since it would load
`path-to-regexp` version `6.2.0` which is not API compatible.
For this reason, this commit changes the behavior of the node-executor
so that it completely ignores npm dependencies when calculating
resolve mappings.
* chore(js): rename GeneratorSchema to LibraryGeneratorSchema
* fix(js): add publishable to library generator schema
* feat(nest): use nrwl/js for library generator
* fix(js): update documentation about publishable
* chore(nest): fix depcheck for nrwl/js
* chore(nest): update test snapshot
* chore(nest): update nestjs/swagger version in node e2e
* chore(js): rename loadTsPlugins function
* fix(nest): default standaloneConfig for library generator to true
* feat(nest): rename tsPlugins to transformers and add tsPlugins to aliases
* chore(nest): fix e2e test on generate a new nest library
Co-authored-by: Chau Tran <ctran@Chaus-MacBook-Pro.local>
* fix(js): clean up swc
* fix(js): clean up swc
* fix(js): add incremental to TypeCheckOptions
* fix(js): use async iterator with tsc executor. remove rxjs deps
* chore(js): remove unnecessary test and commented out code
* fix(js): add else statement for readability
* fix(js): ensure error() and done() always set error and done fields
* chore(js): clean up create async iterable tests
* fix(js): ensure pushQueue is resolved first if there are still items to be resolved before done
Co-authored-by: Chau Tran <ctran@Chaus-MacBook-Pro.local>
disable name mangling when building for production with optimization on,
in order not to break
features relying on runtime reflection
ISSUES CLOSED: #8537
* 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>
