Use the webpack plugin system to create the package.json, this allows for developers to use plugins like
CleanWebpackPlugin which clears the dist before the compilation starts. If this plugin is used in
combination with the old method of generating the package.json, then it is deleted on compilation start.
* feat(js): implement a smarter compiler (tsc, swc) helper dependency detection
ISSUES CLOSED: #10270
* chore(js): add test to check for swc/helpers upon build lib
In Nx 15, we plan to clean up runExecutor and implement proper process handling in runExecutor
upstream. This is a workaround that fix some racing-condition in node:node exexecutor downstream
ISSUES CLOSED: #9305
* fix(testing): jest.preset.ts => jest.preset.js
* fix(testing): update to export default
* fix(testing): migration for moving to export default
* fix(testing): add eslint ignore comments for jest config properties
fixes: #10021
* fix(testing): update tsconfig.spec.json for next apps with project parserOptions
fixes: #9982
* fix(testing): prevent renaming root jest preset
fixes: #9973
* fix(testing): update snapshots for export default
* fix(testing): bump migration version to run
* fix(testing): make sure default jest tests pass for various projects
* fix(js): generate correct jest config for --compiler=swc --js
* 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>
