A command-line tool for local Gatsby development. When doing development work on Gatsby core, this tool allows you to copy the changes to the various Gatsby packages to Gatsby sites that you’re testing your changes on.
npm install -g gatsby-dev-cli
The gatsby-dev-cli tool needs to know where your cloned Gatsby repository is located. You typically only need to configure this once.
gatsby-dev --set-path-to-repo /path/to/my/cloned/version/gatsby
Navigate to the project you want to link to your forked Gatsby repository and run:
The tool will then scan your project’s package.json to find its Gatsby dependencies and copy the latest source from your cloned version of Gatsby into your project’s node_modules folder. A watch task is then created to re-copy any modules that might change while you’re working on the code, so you can leave this program running.
Typically you’ll also want to run
npm run watch in the Gatsby repo to set up
watchers to build Gatsby source code.
More detailed instruction for setting up your Gatsby development environment can be found here.
You can prevent the automatic dependencies scan and instead specify a list of
packages you want to link by using the
gatsby-dev --packages gatsby gatsby-transformer-remark
With this flag, the tool will do an initial scan and copy and then quit. This is useful for setting up automated testing/builds of Gatsby sites from the latest code. Gatsby’s main website (and example websites) are built from HEAD using this flag, see https://github.com/gatsbyjs/gatsby/blob/master/scripts/publish-site.sh.
Don’t output anything except for a quit message when used together with
Copy all modules/files in the gatsby source repo in packages/