Skip to content
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

Remove npm-run-all dependency from where it's not needed #8529

Merged
merged 1 commit into from
Sep 26, 2018

Conversation

lipis
Copy link
Contributor

@lipis lipis commented Sep 25, 2018

There is no need for unnecessary dev dependencies.

"gatsby-source-filesystem": "latest",
"gatsby-transformer-sharp": "latest",
"react": "^16.5.2",
"react-dom": "^16.5.2",
"react-helmet": "^5.2.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also updated to the latest.

Copy link
Contributor

@DSchau DSchau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty conflicted on this!

I like what you're doing, and I'm usually in favor of removing unnecessary dependencies, but we use npm-run-all in several, other places, so it's internally consistent.

What do you think @pieh?

@pieh
Copy link
Contributor

pieh commented Sep 25, 2018

Those aren't starters - they are not used by users, those are used for e2e tests and we use npm-run-all in other places anyway, so not sure if there is value in removing it

@lipis
Copy link
Contributor Author

lipis commented Sep 26, 2018

Overall it's better to have less and we don't gain anything from those here.. yes maybe in other places it makes sense to have the npm-run-all but let's keep the simple things.. simple.

@lipis lipis changed the title Remove npm-run-all dependency from the starter Remove npm-run-all dependency from where it's not needed Sep 26, 2018
Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this in, npm-run-all things doesn't really matter here, but package updates to use latest in integration tests sites is worth it

@pieh pieh merged commit d2a8302 into gatsbyjs:master Sep 26, 2018
@lipis lipis deleted the upgrade-runtime branch September 26, 2018 10:05
@lipis
Copy link
Contributor Author

lipis commented Sep 26, 2018

🍻

lipis added a commit to lipis/gatsby that referenced this pull request Sep 26, 2018
* 'master' of github.com:gatsbyjs/gatsby:
  feat(cache-dir): Add a button for custom 404s in development (gatsbyjs#8548)
  fix: add ecosystem team for starters YAML
  fix: fix displaying and hydrating 404 page in production builds (gatsbyjs#8510)
  fix: don't expect `application/json` type nodes to be files (gatsbyjs#8544)
  Delete cds-takeaways.md (gatsbyjs#8552)
  chore(release): Publish
  chore: remove npm-run-all dep and update deps in e2e tests (gatsbyjs#8529)
  [www] Site/Starter Showcase refactor, rinse II (gatsbyjs#8411)
  Rfc process doc (gatsbyjs#8537)
  [www] a11y improvements (gatsbyjs#8536)
  Update the GraphQL stitching blog post & docs (gatsbyjs#8516)
  fix: change teams to reduce noise for people
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants