5b6df632cb
* 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.
{{links}}
React Plugin for Nx
{{what-is-nx}}
{{getting-started}}
? Workspace name (e.g., org name) happyorg
? What to create in the new workspace react [a workspace with a single React application]
? Application name myapp
? Default stylesheet format CSS
If it's your first Nx project, the command will recommend you to install the nx package globally, so you can invoke nx directly without going through yarn or npm.
Serving Application
- Run
nx serve myappto serve the newly generated application! - Run
nx test myappto test it. - Run
nx e2e myapp-e2eto run e2e tests for it.
Adding React Plugin Into an Existing Workspace
You can always add the React plugin to an existing workspace by installing @nrwl/react and then generating an React application, as follows: nx g @nrwl/react:app myapp.
Quick Start Videos
{{resources}}