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

Using "next" NPM packages would allow using latest Gatsby releases #11

Closed
PEM-- opened this issue Sep 17, 2018 · 3 comments
Closed

Using "next" NPM packages would allow using latest Gatsby releases #11

PEM-- opened this issue Sep 17, 2018 · 3 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@PEM--
Copy link

PEM-- commented Sep 17, 2018

In package.json, using something like:

...
    "gatsby": "next",
    "gatsby-image": "next",
    "gatsby-plugin-offline": "next",
    "gatsby-plugin-react-helmet": "next",
    "gatsby-plugin-sharp": "next",
    "gatsby-plugin-sitemap": "next",
...

would allow using latest Gatsby v2 releases.

If you want, I can PR it easily.

@fabe fabe added enhancement New feature or request wontfix This will not be worked on labels Sep 17, 2018
@fabe
Copy link
Owner

fabe commented Sep 17, 2018

Hey, thanks for your feedback! I lock the gatsby versions because I want to make sure things don't break after a fresh install. There were some breaking changes e.g. to the routing during the beta phase that would've completely broken the site out of the blue. Plus, Gatsby v2 will be out of beta very shortly 👍

@fabe fabe closed this as completed Sep 17, 2018
@PEM--
Copy link
Author

PEM-- commented Sep 17, 2018

OK, thanks for the starter. It's very easy to work with 👍

@fabe
Copy link
Owner

fabe commented Sep 17, 2018

Happy to hear that! Let me know if you have any other feedback or suggestions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants