* feat(react): Add MFE Generator for Host and Remote Apps
Host generator will be able use the mfe-remote generator when remotes are passed into the CLI for the mfe-host command
* docs(react): React Documentation Update
Co-authored-by: Nicholas Cunningham <nico@Nicholass-MacBook-Pro.local>
Co-authored-by: Nicholas Cunningham <ndcunningham>
* fix(misc): avoid issues with refs in SVGs
The previous "import friendly" syntax was actually disabling refs in SVGs parsed by svgr.
I found 3 possible solutions:
1. Removing "![path]"
2. Separating "+ref![path]" with another comma: "+ref,![path]"
3. Rewriting the loader entry in the style of the other loader entries
I chose the last one for added clarity within the file.
* fix(core): fix compilation errors
* chore(react): update emotion to new versions and new package names on react plugin
* chore(nextjs): update emotion to latest version and the new package names
* feat(misc): have react and next plugin migrations update emotion imports
* add renamePackageImports and renameNpmPackage rules to workspace utils
* update migrations to update emotion imports to the new name and version
* 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.
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
- removes the `differentialLoading` build option
- differential loading is always enabled for prod builds
BEFORE (without ESM):
Benchmark #1: nx build demo --prod
Time (mean ± σ): 13.834 s ± 1.731 s [User: 11.817 s, System: 1.352 s]
Range (min … max): 11.947 s … 16.015 s 10 runs
AFTER (with ESM):
Benchmark #1: nx build demo --prod
Time (mean ± σ): 18.711 s ± 1.310 s [User: 12.172 s, System: 1.394 s]
Range (min … max): 17.232 s … 20.770 s 10 runs
