fabe/gatsby-universal

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

PEM-- opened this issue · 3 comments

PEM-- commented

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 commented

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 👍

PEM-- commented

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

fabe commented

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