chore(deps): update gatsby monorepo (major) #209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.5.0
->^1.0.0
^2.13.31
->^3.0.0
^2.0.23
->^3.0.0
^2.1.17
->^3.0.0
^1.1.14
->^2.0.0
2.3.14
->3.5.0
^2.1.31
->^3.0.0
^2.0.6
->^3.0.0
^4.1.6
->^5.0.0
^3.0.4
->^4.0.0
^2.0.7
->^4.0.0
^2.2.9
->^3.0.0
^2.0.7
->^4.0.0
^3.1.6
->^5.0.0
^2.0.26
->^3.0.0
^2.1.31
->^3.0.0
^2.6.9
->^4.0.0
^2.1.9
->^3.0.0
Release Notes
gatsbyjs/gatsby
v1.5.0
Compare Source
v1.4.0
Compare Source
Added
Fixed
modifyWebpackConfig
docs #1613 @KyleAMathewsv1.3.0
Compare Source
Added
Fixed
v1.2.0
Compare Source
A few more days, another minor release 😎
Highlight of this release is @felixjung adding support for hot reloading changes to site's html.js during development in #1473
Beyond that, lots of bug fixes and small feature additions from the community!
Added
Fixed
v1.1.1
Compare Source
v1.1.0
Compare Source
Continuing our blistering development pace, in the five days since our initial 1.0.0 release there's been 44 merged PRs by 20 different authors. Thanks everyone!
Added
gatsby-plugin-emotion
#1447 @rawrmonstarFixed
owner
assignation to prevent error #1454 @sebastienfiv1.0.0
Compare Source
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: facebookincubator/create-react-app#101
#371
v0.12.2
Compare Source
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.
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 #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 ingatsby-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-cssBreaking changes
post-build.js
moved insidegatsby-node.js
. If you had added apost-build.js
module to your code, this function should now be exported fromgatsby-node.js
. A simple way to make the change is to simply requirepost-build.js
there e.g.exports.postBuild = require('./post-build')
. Thanks to @LukeSheard for this! #273static
is split into two stages,build-css
andbuild-html
andproduction
is nowbuild-javascript
. We think these are much more sensible names. Thanks to @scottnonnenberg for the this! #253Other 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 #279
Some highlights:
.babelrc
passed to webpack.react-hmre
rather than being overwritten in develop.js.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. #252
@alampros also contributed a bug fix as he noticed that when setting the host option for
gatsby develop
andgatsby 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 #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! #232
Bug fixes
gatsby-node.js
were being swallowed. @kyleamathews fixed that in859e412
dd2e960
Developer Experience (DX) improvements
gatsby serve-build
so you can easily check that your built site is working as expected. #237Thanks 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
andnpm install --save-dev babel-preset-react-hmre
.Uninstall old Babel 5 dependencies (if you added any).
The
link
function fromgatsby-helpers.js
was renamed toprefixLink
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 togatsby-node.js
and instead of using module.exports, export your config modification function asmodifyWebpackConfig
. 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 truthypage.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 exportrewritePath
ingatsby-node.js
andonRouteChange
ingatsby-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
nowgatsby 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
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.