Some gatsby package dependencies should be devDependencies
See original GitHub issueDescription
Migrate some dependencies in devDependencies for gatsby package.
At least these (non exhaustive):
- “@typescript-eslint/eslint-plugin”
- “@typescript-eslint/parser”
- “eslint”
- “eslint-config-react-app”
- “eslint-loader”
- “eslint-plugin-flowtype”
- “eslint-plugin-graphql”
- “eslint-plugin-import”
- “eslint-plugin-jsx-a11y”
- “eslint-plugin-react”
- “eslint-plugin-react-hooks”
Steps to reproduce
yarn install --production
npm install --production
Expected result
No dev packages should be installed.
Actual result
Load linting dependencies and others
Environment
All.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Question: Is Gatsby a devDependency or dependency? #832
A devDependency is for packages that are published to NPM so you need to differentiate between packages needed by "consumers" of a package...
Read more >eslint should be listed in the project's dependencies, not ...
Solved it with adding this to my .eslintrc : "import/no-extraneous-dependencies": ["error", {"devDependencies": true}].
Read more >Differences between dependencies, devDependencies, and ...
This is a summary of the differences between dependencies, devDependencies, and peerDependenceise in npm package.json.
Read more >gatsby-plugin-postcss - npm
Gatsby plugin to handle PostCSS. ... Start using gatsby-plugin-postcss in your project by running `npm i ... Dev Dependencies (4).
Read more >dependencies vs devDependencies - Medium
When you are installing some lib using npm, all needed info automatically ... devDependencies should contain packages which are used during ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can take this.
Can’t remove those deps or move to dev deps because of https://github.com/gatsbyjs/gatsby/issues/20815#issuecomment-577703587 - the additional 3 deps there are peer deps of
eslint-config-react-app
so they also need to stay