* fix(misc): allow --js flag to be passed to @nrwl/web:lib schematic
creates js files instead of ts files
s
ISSUES CLOSED: #2985
* fix(misc): add tests for --js flag in workspace
* fix(node): use typescript directly to emit files rather than calling tsc
* chore(node): add migration to remove root dir from projects using @nrwl/node:package
* chore(node): fix unit tests
* chore(node): update package spec and e2es
* feat(angular): add an option to add strict type checking
Adding support for strict type checking to Angular application and library generate schematics.
E.g.
`nx generate application myapp --strict`
`nx generate lib mylib --strict`
Closes#3383.
Performs the following configuration changes:
- Enables strict mode in TypeScript, as well as other strictness flags recommended by the TypeScript team. Specifically, forceConsistentCasingInFileNames, noImplicitReturns, noFallthroughCasesInSwitch.
- Turns on strict Angular compiler flags strictTemplates and strictInjectionParameters
These match the flags used in the standard CLI strict mode.
* cleanup(misc): updating import path
Co-authored-by: Ashley Hunter <ashley.hunter@hotmail.co.uk>
* fix(core): resolve webpack loaders with `require.resolve()`
With strict package managers such as pnpm or Yarn PnP, transitive
dependencies are *not* hoisted to the root node_modules folder. This
means that a webpack config defined within a package like
'@nrwl/cypress' cannot resolve loaders like 'ts-loader', unless
'ts-loader' is declared in the workspace's own package.json.
This is a problem because the workspace might define a different version
of 'ts-loader', incompatible with the version declared by
'@nrwl/cypress/package.json'. The workspace should not need to declare
a dependency on 'ts-loader' anyway.
See also:
* https://github.com/pnpm/pnpm/issues/801
* https://github.com/webpack/webpack/issues/5087
* fix(core): resolve absolute 'raw-loader' path
When replacing the 'raw-loader' rule in the `getStylesPartial` function,
check for the absolute path of 'raw-loader' rather than just the name.
Just as the default rollup config is a function of builder options, so too should-be/could-be userland rollup configuration
Pass in full options to userland rollup config function
