Gathering detailed insights and metrics for gatsby-dev-cli
Gathering detailed insights and metrics for gatsby-dev-cli
Gathering detailed insights and metrics for gatsby-dev-cli
Gathering detailed insights and metrics for gatsby-dev-cli
The best React-based framework with performance, scalability and security built in.
npm install gatsby-dev-cli
Typescript
Module System
Min. Node Version
Node Version
NPM Version
gatsby-source-shopify@9.0.0
Updated on Jan 07, 2025
gatsby-link@5.14.1
Updated on Jan 07, 2025
gatsby-source-contentful@8.15.0
Updated on Jan 07, 2025
v5.14.0
Updated on Nov 06, 2024
gatsby-source-shopify@8.13.2
Updated on Oct 28, 2024
gatsby-source-wordpress@7.13.5 and 6 more...
Updated on Oct 28, 2024
JavaScript (58.91%)
TypeScript (38.71%)
CSS (1.05%)
HTML (0.69%)
MDX (0.45%)
Shell (0.13%)
Dockerfile (0.03%)
PHP (0.02%)
EJS (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
55,909 Stars
21,738 Commits
10,289 Forks
719 Watchers
316 Branches
3,966 Contributors
Updated on Jul 15, 2025
Latest Version
5.14.0
Package Id
gatsby-dev-cli@5.14.0
Unpacked Size
93.66 kB
Size
21.35 kB
File Count
18
NPM Version
lerna/3.22.1/node@v20.11.1+arm64 (darwin)
Node Version
20.11.1
Published on
Nov 06, 2024
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
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:
gatsby-dev
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.
If you've recently run gatsby-dev
your node_modules
will be out of sync with currently published packages. In order to undo this, you can remove the node_modules
directory or run:
1git checkout package.json; yarn --force
or
1git checkout package.json; npm install --force
More detailed instructions for setting up your Gatsby development environment can be found here.
--packages
You can prevent the automatic dependencies scan and instead specify a list of
packages you want to link by using the --packages
option:
gatsby-dev --packages gatsby gatsby-transformer-remark
--scan-once
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 CI is using this for its tests.
--quiet
Don't output anything except for a success message when used together with
--scan-once
.
--copy-all
Copy all modules/files in the gatsby source repo in packages/
--force-install
Disable copying files into node_modules and force usage of local npm repository.
--external-registry
Run yarn add
commands without the --registry
flag. This is helpful when using yarn 2/3 and you need to use yarn config set npmRegistryServer http://localhost:4873
and echo -e 'unsafeHttpWhitelist:\n - "localhost"' >> .yarnrc.yml
before running gatsby-dev-cli
.
No vulnerabilities found.
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
GitHub workflow tokens follow principle of least privilege
Details
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
Found 20/25 approved changesets -- score normalized to 8
Reason
8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8
Reason
SAST tool is not run on all commits -- score normalized to 8
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
100 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More