* feat(testing): add projects into jest config
* chore(testing): update unit tests and fix presets with spreading a default
* chore(testing): fix node e2e
* chore(testing): review comment changes
* feat(react): wip: initial e2e test by jack and web package builder fix
Updated some commnets about versions of Storybook, extra config files, and how to treat these
* fix(web): preserve the target set in tsconfig.lib.json
ISSUES CLOSED: #3601
* fix(react): preserve the target set in tsconfig.lib.json
ISSUES CLOSED: #3601
* fix(react): preserve the target set in tsconfig.lib.json
ISSUES CLOSED: #3601
On Windows, the paths were using backslashes and this was causing `globby` inside `rollup-plugin-copy` to not match any pattern, and thus ignoring all assets during the build. This commit ensures that all paths passed to `rollup-plugin-copy` use only forward slashes.
ISSUES CLOSED: #3328
* 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
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
