chore(deps): update gatsby monorepo #1046

renovate · 2020-05-31T05:27:22Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
babel-preset-gatsby	`0.4.7` -> `0.12.3`
gatsby (changelog)	`2.22.13` -> `2.32.13`
gatsby-image	`2.4.5` -> `2.11.0`
gatsby-link	`2.4.3` -> `2.11.0`
gatsby-plugin-feed	`2.5.3` -> `2.13.1`
gatsby-plugin-google-analytics	`2.3.2` -> `2.11.0`
gatsby-plugin-layout	`1.3.2` -> `1.10.0`
gatsby-plugin-lodash	`3.3.2` -> `3.10.0`
gatsby-plugin-manifest	`2.4.9` -> `2.12.1`
gatsby-plugin-netlify	`2.3.3` -> `2.11.1`
gatsby-plugin-offline	`3.2.7` -> `3.10.2`
gatsby-plugin-react-helmet	`3.3.2` -> `3.10.0`
gatsby-plugin-remove-trailing-slashes	`2.3.3` -> `2.10.0`
gatsby-plugin-sharp	`2.6.9` -> `2.14.4`
gatsby-plugin-styled-components	`3.3.2` -> `3.10.0`
gatsby-plugin-typescript	`2.4.3` -> `2.12.1`
gatsby-remark-autolink-headers	`2.3.3` -> `2.11.0`
gatsby-remark-copy-linked-files	`2.3.3` -> `2.10.0`
gatsby-remark-images	`3.3.8` -> `3.11.1`
gatsby-remark-prismjs	`3.5.2` -> `3.13.0`
gatsby-remark-smartypants	`2.3.2` -> `2.10.0`
gatsby-source-filesystem	`2.3.8` -> `2.11.1`
gatsby-transformer-remark	`2.8.13` -> `2.16.1`
gatsby-transformer-sharp	`2.5.3` -> `2.12.1`

Release Notes

gatsbyjs/gatsby

`v0.12.3`

Compare Source

Quick release to add this very nice UX improvement contributed by @LukeSheard and borrowed from Create React App's similar feature: facebook/create-react-app#101

gatsbyjs/gatsby#371

`v0.12.2`

Compare Source

eslint-plugin-jsx-a11y added a peerDependency on a patch update which meant NPM 2 users couldn't install Gatsby or starters. Pin eslint a11y plugin until move to eslint 3 gatsbyjs/gatsby#369 pins the plugin to the last good release.
@kennu fixed an instance where we were hiding important errors Show other wrapper require errors than MODULE_NOT_FOUND on console gatsbyjs/gatsby#366

`v0.12.1`

Compare Source

`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.1`

Compare Source

New tests!

@benstepp waded into the center of Gatsby and refactored one of the core functions AND setup a test framework AND added a number of tests. Awesome! gatsbyjs/gatsby#232

Bug fixes

@BerkeleyTrue fixed route => template matching which was broken for some edge cases Fix route -> parent template matching gatsbyjs/gatsby#230
@BerkeleyTrue pointed out that errors in gatsby-node.js were being swallowed. @kyleamathews fixed that in gatsbyjs/gatsby@859e412
The Autoprefixer plugin was being added to the Postcss multiple times which @kyleamathews fixed in gatsbyjs/gatsby@dd2e960

Developer Experience (DX) improvements

@michaeljdeeb added a check that hard-coded paths in pages have a path prefix. This is a problem that's bit several people as it's easy to miss Verifying that path strings are prepended a forward slash gatsbyjs/gatsby#223. Invariants are awesome!
@alehlopeh added a new cli command gatsby serve-build so you can easily check that your built site is working as expected. Add serve command in cli gatsbyjs/gatsby#237

Thanks everyone!

`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

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-05-31T05:27:25Z

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

vercel · 2020-05-31T05:27:29Z

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/jesses/jessesio/chayl4agn
✅ Preview: https://jessesio-git-renovate-gatsby-monorepo.jesses.vercel.app

[Deployment for bc26798 failed]

renovate bot added the renovate label May 31, 2020

renovate bot force-pushed the renovate/gatsby-monorepo branch from 1ea6537 to 278f287 Compare June 2, 2020 10:45

renovate bot changed the title ~~fix(deps): update dependency gatsby to v2.22.15~~ fix(deps): update gatsby monorepo Jun 2, 2020

vercel bot deployed to Preview June 2, 2020 10:45 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from 278f287 to e8dedef Compare June 2, 2020 12:28

renovate bot changed the title ~~fix(deps): update gatsby monorepo~~ chore(deps): update gatsby monorepo Jun 2, 2020

vercel bot deployed to Preview June 2, 2020 12:28 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from e8dedef to bdd2ee8 Compare June 2, 2020 12:41

vercel bot deployed to Preview June 2, 2020 12:41 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from bdd2ee8 to ce57b7c Compare June 3, 2020 11:54

vercel bot deployed to Preview June 3, 2020 11:55 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from ce57b7c to c2fbd44 Compare June 3, 2020 15:53

vercel bot deployed to Preview June 3, 2020 15:53 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from c2fbd44 to dfe4780 Compare June 3, 2020 17:42

vercel bot deployed to Preview June 3, 2020 17:42 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from dfe4780 to 3f51e2d Compare June 3, 2020 18:53

vercel bot deployed to Preview June 3, 2020 18:53 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from 3f51e2d to 9e03af3 Compare June 4, 2020 08:41

vercel bot deployed to Preview June 4, 2020 08:41 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from 9e03af3 to f1820a1 Compare June 4, 2020 09:04

vercel bot deployed to Preview June 4, 2020 09:04 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from f1820a1 to 2e68a7c Compare June 4, 2020 09:24

vercel bot requested a deployment to Preview June 4, 2020 09:24 Pending

vercel bot deployed to Preview June 4, 2020 09:30 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from 2e68a7c to 4f1d554 Compare June 4, 2020 16:24

vercel bot deployed to Preview June 4, 2020 16:24 View deployment

renovate bot force-pushed the renovate/gatsby-monorepo branch from 4f1d554 to 801d788 Compare June 4, 2020 21:11

vercel bot deployed to Preview June 4, 2020 21:11 View deployment

vercel bot had a problem deploying to Preview December 15, 2020 19:38 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from f236609 to 7d89780 Compare December 16, 2020 16:43

vercel bot had a problem deploying to Preview December 16, 2020 16:43 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 7d89780 to feb2e7d Compare December 16, 2020 17:52

vercel bot had a problem deploying to Preview December 16, 2020 17:52 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 953a406 to c4c5c71 Compare December 23, 2020 17:53

vercel bot had a problem deploying to Preview December 23, 2020 17:54 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from c4c5c71 to ec00740 Compare December 29, 2020 22:18

vercel bot had a problem deploying to Preview December 29, 2020 22:18 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from ec00740 to 221d5ea Compare January 5, 2021 19:38

vercel bot had a problem deploying to Preview January 5, 2021 19:38 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 221d5ea to 335dc57 Compare January 5, 2021 20:30

vercel bot had a problem deploying to Preview January 5, 2021 20:30 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 335dc57 to 330509e Compare January 6, 2021 13:42

vercel bot had a problem deploying to Preview January 6, 2021 13:42 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 330509e to 7935ca7 Compare January 13, 2021 11:49

vercel bot had a problem deploying to Preview January 13, 2021 11:49 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 7935ca7 to 5d54d50 Compare January 16, 2021 11:54

vercel bot had a problem deploying to Preview January 16, 2021 11:55 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 5d54d50 to a95f592 Compare January 23, 2021 02:58

vercel bot had a problem deploying to Preview January 23, 2021 02:58 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from a95f592 to d585c62 Compare February 1, 2021 13:56

vercel bot had a problem deploying to Preview February 1, 2021 13:57 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from d585c62 to 601ad25 Compare February 6, 2021 21:02

vercel bot had a problem deploying to Preview February 6, 2021 21:02 Failure

renovate bot force-pushed the renovate/gatsby-monorepo branch from 601ad25 to 1976b4f Compare April 26, 2021 16:43

vercel bot had a problem deploying to Preview April 26, 2021 16:43 Failure

chore(deps): update gatsby monorepo

bc26798

renovate bot force-pushed the renovate/gatsby-monorepo branch from 1976b4f to bc26798 Compare May 9, 2021 22:44

vercel bot had a problem deploying to Preview May 9, 2021 22:44 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update gatsby monorepo #1046

chore(deps): update gatsby monorepo #1046

renovate bot commented May 31, 2020 •

edited

renovate bot commented May 31, 2020

vercel bot commented May 31, 2020 •

edited

chore(deps): update gatsby monorepo #1046

Are you sure you want to change the base?

chore(deps): update gatsby monorepo #1046

Conversation

renovate bot commented May 31, 2020 • edited

Release Notes

Upgrade

Breaking changes

Other notable non-breaking changes

New tests!

Bug fixes

Developer Experience (DX) improvements

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 May 31, 2020

Branch automerge failure

vercel bot commented May 31, 2020 • edited

renovate bot commented May 31, 2020 •

edited

`gatsby serve` now `gatsby develop`

vercel bot commented May 31, 2020 •

edited