-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Is Gatsby a devDependency or dependency? #832
Comments
A Gatsby site without Gatsby can't do anything so it's a dependency. A devDependency is for packages that are published to NPM so you need to differentiate between packages needed by "consumers" of a package vs. "producers". Since anyone using a Gatsby repo is a producer, everything goes in dependencies. |
@KyleAMathews I think that's good as a general rule, but it seems like it may be overly restrictive. For instance, a library with documentation generated by Gatsby might want to have |
@michaek good point. Yeah there are definitely cases where
|
If nothing else, checking for |
I have looked at some of the starters, and they all seem to specify Gatsby under
dependencies
inpackage.json
: gatsby-starter-default, gatsby-starter-kitchen-sink, gatsby-starter-documentationIs there a reason it's not under
devDependencies
instead?The text was updated successfully, but these errors were encountered: