It's no possible to upgrade to the Gatsby v3 right now, because the nx gatsby plugin (code) doesn't support it
implicit - means some sort of manual configuration
npm i --save-dev @nrwl/gatsby gatsby-cli
nx serve <generated-site-name>
(on this example it was gatsby
)
when I tried to run the lint over the e2e tests of the gatsby I notice a wrong configuration on the workspace.json
which was set to the apps/gatsby-e2e
, where it should use the same lint runner as the apps/gatsby
when I runned the lint over the apps/gatsby
I get some warning messages, to remove them, I needed to change the lint configuration on the workspace.json
to ignore the apps/gatsby/public
folder
using the Gatsby inside of the Nx workspace it's basically like have 2 react applications, nothing special was notice to be able to use it
to map the libs/assets
into the gatsby application it was needed some extra manual steps because the gatsby doesn't supports the baseUrl
from the tsconfig.base.json
Nx: Extensible Dev Tools for Monorepos (React)
[YouTube] Nx Tutorial: High Quality React apps with Nx, Storybook & Cypress
Gatsby support, custom workspace layouts, and more in Nx 9.4! | Nrwl
[GitHub] nrwl/gatsby - Nx plugin for Gatsby
Storybook support, run-many command, UI improvements, and more in Nx 8.8 | Nrwl
Nx 8.8: Now You Can Write UI Tests with Storybook and Cypress | Nrwl
Creating a Storybook instance including stories from multiple libraries in a Nrwl Nx workspace
React Microfrontends and Monorepos: A Perfect Match | Nrwl - demo | code
to make my life easier I have the current node_modules
from the project mapped to the PATH env variable, that enables me to run the command nx
directly, if you don't have if you must use the short cut mapped on the package.json
, using it like npm run nx ...
or it's also possible to use like npx nx ...
(the npx
will look into the local installed packages ./node_modules/
and on the global installed packages)
./node_modules/.bin
gatsby-plugin-typescript caveats
Does not support baseUrl. Workaround: use gatsby-plugin-root-import and configure it to point the baseUrl value (also set baseUrl option in tsconfig.json file).