v2 you say? But we just released a v1???
Well… yes but we're on webpack 1 and webpack 3 is out and Babel 7 is almost out etc. so there's some breaking changes we need to make to upgrade so new major release it is!
The changes should be pretty minor for most sites. Unless you're directly modifying webpack/babel settings, nothing should change. Once it's out, you'll just need to upgrade Gatsby + any plugins you've added.
We'd love your help tackling the various TODOs. We're working on the v2 branch so jump in and start helping.
Check out the contributions docs if you're new to developing with Gatsby https://www.gatsbyjs.org/docs/how-to-contribute/
If there's not an issue already created for a TODO below, create one with any your ideas and ask for feedback/guidance.
pathContext to pageContext https://github.com/gatsbyjs/gatsby/issues/1456deleteNodes. Is potential efficiency gains worth extra code complexity? Could just standardize on bulk api and remove single shot API.Other breaking changes we should make? Add a comment!
maybe pass through the graphql in the plugin api to avoid some of the multiple instance issues?
Serve site over the local network.
Add service worker. Not sure, but having such a functionality out of the box is great.
Serve site over the network
@gagan0723 not sure what you mean here?
For service workers, there's gatsby-plugin-offline https://www.gatsbyjs.org/packages/gatsby-plugin-offline/
Serve site over the network
@KyleAMathews What I mean is, is there a way to serve site on the local network so that it may be viewed on other devices connected to the same network.
Oh ok, so like Create React App, tell you the address you can use to access the site. No that is a great idea. Adding it.
Closing this in favor of #2641
Most helpful comment
maybe pass through the
graphqlin the plugin api to avoid some of the multiple instance issues?