chore(deps): update gatsby monorepo #366

renovate · 2020-04-10T19:17:30Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
babel-preset-gatsby-package	`0.3.1` -> `0.12.0`
gatsby (changelog)	`2.20.16` -> `2.32.13`
gatsby-source-filesystem	`2.2.2` -> `2.11.1`

Release Notes

gatsbyjs/gatsby

`v0.12.0`

Compare Source

Gatsby now ships with richer support for images. Now you can "import" or "require" an image and use it within your React components and under the hood, the images will be automatically optimized.

import myImage from './my-image.jpg'

// in render function
<div>
  <h1>Hi friends!</h1>
  <img src={myImage} />
</div>

We're using the image-webpack-loader which uses the popular Imagemin project to minify your images.

There's future (responsive) image work planned! See gatsbyjs/gatsby#285 if you want to get involved.

Upgrade

This is marked as a breaking release as it could interfere with your Webpack config if you already have added image loader support.

If you have added custom image loaders already, to upgrade, in your modifyWebpackConfig function in gatsby-node.js add this line: config.removeLoader('images')

You'll also need to add image-webpack-loader to your site:

npm install --save-dev image-webpack-loader

Enjoy!

`v0.11.0`

Compare Source

The headliner of this release is you can now inline CSS in the <head> of your site. This is a best practice recommended by Google's AMP project among others as you then avoid additional requests which can signifcantly slow down your site. Testing using webpagetest.org showed that moving css inline improved the Speed Index 20-50%!! In one test on a simulated 3G connection, the time to initial render went from ~1.8 seconds to ~1 second.

It's a very simple switch to make. See this commit in the default starter gatsbyjs/gatsby-starter-default@1faecb5 It's also documented at https://github.com/gatsbyjs/gatsby#inline-css

Breaking changes

post-build.js moved inside gatsby-node.js. If you had added a post-build.js module to your code, this function should now be exported from gatsby-node.js. A simple way to make the change is to simply require post-build.js there e.g. exports.postBuild = require('./post-build'). Thanks to @LukeSheard for this! #273
The "stages" were renamed. If you override Webpack configs and are switching behavior based on the stage, static is split into two stages, build-css and build-html and production is now build-javascript. We think these are much more sensible names. Thanks to @scottnonnenberg for the this! #253

Other notable non-breaking changes

@benstepp did a deep refactor of how we're loading Babel plugins. There shouldn't be any breaking changes but it fixes a number of bugs gatsbyjs/gatsby#279

Some highlights:

User can override the .babelrc passed to webpack.
User can use whatever babel plugins they want.
User babel config is extended with react-hmre rather than being overwritten in develop.js.
Object.assign is now polyfilled by default.
Non breaking change as starters previously required a babelrc and gatsby will just read them as normal.
Fixes three issues #129, #235, #264

`v0.10.0`

Compare Source

Thanks to the efforts of @patrykkopycinski, Gatsby now supports React 15. This should be an easy upgrade for most people as long as your current site is showing deprecation warnings in the console.log. gatsbyjs/gatsby#252

@alampros also contributed a bug fix as he noticed that when setting the host option for gatsby develop and gatsby serve-build that the short version -h overrode the default help option. He changed that to -H so there would no longer be a conflict gatsbyjs/gatsby#247.

`v0.9.0`

Compare Source

Another release with two nice DX improvements.

Also we hit 2500 stars as I was writing this review 🎉

Babel 6

Gatsby started its life on Babel 5 but Babel 6 is out and stable so we'll upgrade along with the rest of the ecosystem and take advantage of its improved performance and awesome new plugin api.

Gatsby must now be installed as a dependency of the site

The global Gatsby install now defers to the local install of Gatsby (and throws if it can't find one). This means you can build a site and not worry about needing to upgrade it again as Gatsby accumulates breaking changes. This also helps ensure Gatsby works in environments where you don't want a global install e.g. build servers.

Upgrade instructions

Install Gatsby — npm install --save gatsby
Install new Babel 6 dependencies (they must be installed locally) — npm install --save babel-plugin-add-module-exports babel-preset-es2015 babel-preset-react babel-preset-stage-1 and npm install --save-dev babel-preset-react-hmre.
Uninstall old Babel 5 dependencies (if you added any).
The link function from gatsby-helpers.js was renamed to prefixLink to clarify its purpose.
Your .babelrc file needs to be upgraded to look like:

{
  "presets": ['react', 'es2015', 'stage-1'],
  "plugins": ['add-module-exports']
}

If you modified the default Webpack config in gatsby.config.js, this functionality is now moved to gatsby-node.js and instead of using module.exports, export your config modification function as modifyWebpackConfig. See the updated instructions in the README.
If you were differentiating between pages with content (like .md files) and pages without (like pages/profile.js) by looking for truthy page.data, you'll now need check for truthy page.data.body.
If your site is under version control, you might want to ignore the new auto-written module .gatsby-context.js.
rare if you used the rewritePath, onRouteChange hooks in your app.js — app.js is now not supported. Instead you should export rewritePath in gatsby-node.js and onRouteChange in gatsby-browser.js. The function signatures didn't change. These new files will be gaining more functionality in future releases.

That's it! See you in the issue queues :-)

`v0.8.0`

Compare Source

`v0.7.0`

Compare Source

Update to React 0.14

The big change for this release was updating React to 0.14. Thanks to @patrykkopycinski for his PR!

We're still on the 0.13 series of React Router as their recent 1.0 release will require internal updates to Gatsby. Follow along at gatsbyjs/gatsby#32 if interested.

`gatsby serve` now `gatsby develop`

Serve implied Gatsby was just serving up files. Develop conveys the idea better that you're starting up a full-fledged development server with the intent to start developing.

Can now do webpack requires in your html.jsx

Previously you couldn't do webpack requires in your html component as the development server was requiring the module in node context. But with the help of @petehunt's webpack-require project, you can now require css or anything else you'd like in your html.jsx.

Improved support for prefixing site links e.g. when building for Github Pages.

See the documentation that's been added to the README.

How to upgrade

You'll need to update React in your project to React 0.14 as well as upgrade any React components that relied on older React APIs. Make sure to not install the latest react-router.

`v0.6.0`

Compare Source

Bug fix

Previously Gatsby was compiling the production bundle.js with source-maps inlined. @fson noticed this and wrote a PR to fix this which reduced bundle.js size by 3x! Change devtool for production build to source-map gatsbyjs/gatsby#48

Gatsby previously was crashing when trying to copy assets in the post-build step where the asset was not in a directory with a page.

#39

Fixed in gatsbyjs/gatsby@55fee06

`v0.4.0`

Compare Source

@fson added SVG support to the Webpack config in #34

`v0.3.2`

Compare Source

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate · 2020-04-10T19:17:33Z

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

Branch has one or more failed status checks

renovate bot added the renovate label Apr 10, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from b852193 to 8e21ef3 Compare April 11, 2020 12:40

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.17~~ chore(deps): update dependency gatsby to v2.20.18 Apr 11, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch 3 times, most recently from 11bdbff to 9328fbb Compare April 14, 2020 07:03

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.18~~ chore(deps): update dependency gatsby to v2.20.19 Apr 14, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from 9328fbb to 569118d Compare April 14, 2020 13:20

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.19~~ chore(deps): update dependency gatsby to v2.20.20 Apr 14, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from 569118d to 84a1a10 Compare April 15, 2020 04:36

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.20~~ chore(deps): update dependency gatsby to v2.20.21 Apr 15, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from 84a1a10 to ae57d12 Compare April 15, 2020 09:19

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.21~~ chore(deps): update dependency gatsby to v2.20.22 Apr 15, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from ae57d12 to 80dd0ea Compare April 16, 2020 15:40

renovate bot changed the title ~~chore(deps): update dependency gatsby to v2.20.22~~ chore(deps): update gatsby monorepo Apr 16, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch 14 times, most recently from 5b0cba6 to 3d2065b Compare April 20, 2020 17:30

renovate bot force-pushed the renovate/gatsby-monorepo branch 9 times, most recently from afc34ef to d5db726 Compare July 10, 2020 10:33

renovate bot force-pushed the renovate/gatsby-monorepo branch 8 times, most recently from f0ea0b5 to bbf0b8a Compare July 22, 2020 09:06

renovate bot force-pushed the renovate/gatsby-monorepo branch 3 times, most recently from 5b62d8b to aee1338 Compare July 24, 2020 09:31

renovate bot force-pushed the renovate/gatsby-monorepo branch from aee1338 to 6a9df20 Compare August 26, 2020 06:57

renovate bot force-pushed the renovate/gatsby-monorepo branch from 6a9df20 to edeaf52 Compare October 28, 2020 05:59

renovate bot force-pushed the renovate/gatsby-monorepo branch from edeaf52 to c2c07e9 Compare November 27, 2020 05:01

renovate bot force-pushed the renovate/gatsby-monorepo branch from c2c07e9 to caf1fa2 Compare December 10, 2020 21:00

renovate bot force-pushed the renovate/gatsby-monorepo branch from caf1fa2 to bd5d5ad Compare January 7, 2021 16:58

renovate bot force-pushed the renovate/gatsby-monorepo branch from bd5d5ad to 9e04853 Compare January 24, 2021 16:49

renovate bot force-pushed the renovate/gatsby-monorepo branch from 9e04853 to c83781d Compare February 6, 2021 12:57

renovate bot force-pushed the renovate/gatsby-monorepo branch from c83781d to f5ec792 Compare April 26, 2021 17:36

chore(deps): update gatsby monorepo

5d3fffa

renovate bot force-pushed the renovate/gatsby-monorepo branch from f5ec792 to 5d3fffa Compare May 9, 2021 23:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update gatsby monorepo #366

chore(deps): update gatsby monorepo #366

renovate bot commented Apr 10, 2020 •

edited

renovate bot commented Apr 10, 2020

chore(deps): update gatsby monorepo #366

Are you sure you want to change the base?

chore(deps): update gatsby monorepo #366

Conversation

renovate bot commented Apr 10, 2020 • edited

Release Notes

Upgrade

Breaking changes

Other notable non-breaking changes

Babel 6

Gatsby must now be installed as a dependency of the site

Upgrade instructions

Update to React 0.14

gatsby serve now gatsby develop

Can now do webpack requires in your html.jsx

Improved support for prefixing site links e.g. when building for Github Pages.

How to upgrade

Bug fix

Configuration

renovate bot commented Apr 10, 2020

Branch automerge failure

renovate bot commented Apr 10, 2020 •

edited

`gatsby serve` now `gatsby develop`