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>
* fix(testing): add .test. files to spec tsconfig template
add support for .test.ts and with supportTsx .test.{js|tsx|jsx} files
in the tsconfig.spec.json template.
Note each package that excludes testing files will need to be updated to
exclude the new files (coming in future commits)
* fix(angular): add .test.ts support in tsconfigs
add .test.ts in angular jest template
update angular generators to exclude test files
* fix(gatsby): add .test. file prefixes to tsconfig ignore
ignore the new .test.{js|ts|jsx|tsx} files added to jest configs
* fix(react): add .test. file prefix to app/lib tsconfigs
add .test.{ts|js|tsx|jsx} files to be excluded by app/lib tsconfig
* fix(node): add .test. file prefix to app/lib tsconfig
add .test.{ts|js|tsx|jsx} files to be excluded by app/lib tsconfig
ISSUES CLOSED: #7263
* fix(nest): update tests for new .test.ts files in tsconfig
update tests to account for changes in node generators which add .test.ts to the exclude of
tsconfigs
* fix(express): update tests to account for new tsconfig changes
updated snapshots
added new patterns for tsconfig
* fix(linter): update snapshots for new tsconfig changes
snapshot updated to include new .test.ts file changes for tsconfig
* fix(node): update testing to account for spec tsconfig changes
add .test.ts files in e2e tests
* fix(testing): add migration for tsconfig changes
initial migration and test for tsconfig changes
* chore(testing): add to migrations collection
add the update-ts-config-for-test-filenames to migrations
* fix(testing): fix filesystem issue with jest tests
mock readConfig to always return an basic config to prevent issues of not finding a config in non
linux environments, aka missing /root
* cleanup(testing): update error message
update message logged when tsconfig isn't found to mention what was trying to be accompished so it
can be manually updated if desired.
node:build currently has tsPlugins options to invoke TypeScript Plugins (transformers). This PR
brings the same functionality to node:package
ISSUES CLOSED: #7420
* 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
