chore(deps): update gatsby monorepo - autoclosed #284

renovate · 2020-04-24T05:52:37Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
babel-preset-gatsby	`0.3.1` -> `0.12.3`
gatsby (changelog)	`2.20.17` -> `2.32.13`
gatsby-image	`2.3.2` -> `2.11.0`
gatsby-plugin-emotion	`4.2.1` -> `4.5.0`
gatsby-plugin-manifest	`2.3.3` -> `2.12.1`
gatsby-plugin-react-helmet	`3.2.2` -> `3.10.0`
gatsby-plugin-sharp	`2.5.4` -> `2.14.4`
gatsby-source-filesystem	`2.2.2` -> `2.11.1`
gatsby-transformer-screenshot	`2.2.1` -> `2.10.0`
gatsby-transformer-sharp	`2.4.4` -> `2.12.1`
gatsby-transformer-yaml	`2.3.1` -> `2.11.0`

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 #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.6`

Compare Source

`v0.3.5`

Compare Source

`v0.3.4`

Compare Source

`v0.3.3`

Compare Source

`v0.3.2`

Compare Source

Configuration

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

🚦 Automerge: Disabled due to failing status checks.

♻️ Rebasing: Whenever PR becomes conflicted, 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 bot force-pushed the renovate/gatsby-monorepo branch 17 times, most recently from f49767e to 51bd9aa Compare April 30, 2020 10:48

renovate bot force-pushed the renovate/gatsby-monorepo branch 13 times, most recently from 967c842 to 6852376 Compare May 7, 2020 10:26

renovate bot force-pushed the renovate/gatsby-monorepo branch 6 times, most recently from 5d40b59 to bb3c26f Compare March 3, 2021 23:19

renovate bot force-pushed the renovate/gatsby-monorepo branch 2 times, most recently from 2ddfef5 to 2411976 Compare March 9, 2021 22:35

renovate bot force-pushed the renovate/gatsby-monorepo branch 6 times, most recently from 1eff4b4 to 4e57ffd Compare March 31, 2021 03:09

renovate bot force-pushed the renovate/gatsby-monorepo branch 2 times, most recently from 9e48aeb to 1bd44ca Compare April 7, 2021 13:29

renovate bot force-pushed the renovate/gatsby-monorepo branch 3 times, most recently from c2f20d6 to c6d55cf Compare April 27, 2021 17:50

renovate bot force-pushed the renovate/gatsby-monorepo branch 3 times, most recently from d55ad4c to 6835258 Compare May 5, 2021 22:11

renovate bot force-pushed the renovate/gatsby-monorepo branch 3 times, most recently from a74ec0d to e9a6785 Compare May 12, 2021 09:40

chore(deps): update gatsby monorepo

d612e40

renovate bot force-pushed the renovate/gatsby-monorepo branch from e9a6785 to d612e40 Compare May 13, 2021 11:16

renovate bot changed the title ~~chore(deps): update gatsby monorepo~~ chore(deps): update gatsby monorepo - autoclosed May 27, 2021

renovate bot closed this May 27, 2021

renovate bot deleted the renovate/gatsby-monorepo branch May 27, 2021 14:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update gatsby monorepo - autoclosed #284

chore(deps): update gatsby monorepo - autoclosed #284

renovate bot commented Apr 24, 2020 •

edited

Loading

chore(deps): update gatsby monorepo - autoclosed #284

chore(deps): update gatsby monorepo - autoclosed #284

Conversation

renovate bot commented Apr 24, 2020 • edited Loading

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 Apr 24, 2020 •

edited

Loading

`gatsby serve` now `gatsby develop`