-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update gatsby #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ad3c302 to
6662081
Compare
550e5cf to
ecb02c0
Compare
c271b21 to
3171590
Compare
3171590 to
de6582d
Compare
de6582d to
108342d
Compare
dbb8f21 to
cec9448
Compare
cec9448 to
ca12deb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^5.29.2->^5.30.00.10.0->0.12.3^2.30.1->^2.32.13^2.9.0->^2.11.0^2.8.0->^2.10.0^2.11.0->^2.13.1^1.8.0->^1.10.0^2.6.0->^2.8.0^2.10.0->^2.12.1^2.9.0->^2.11.1^4.8.0->^4.10.1^3.8.0->^3.10.2^3.8.0->^3.10.0^1.5.5->^1.6.2^3.0.0->^3.2.0^2.12.0->^2.14.4^2.10.0->^2.12.0^2.9.0->^2.11.0^2.8.0->^2.10.0^3.9.0->^3.11.1^3.8.0->^3.10.0^3.11.0->^3.13.0^2.9.0->^2.11.0^2.8.0->^2.10.0^2.9.0->^2.11.1^2.14.0->^2.16.1^2.10.0->^2.12.1Release Notes
getsentry/sentry-javascript
v5.30.0Compare Source
gatsbyjs/gatsby
v0.12.3Compare 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.2Compare Source
v0.12.1Compare Source
v0.12.0Compare 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 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
modifyWebpackConfigfunction ingatsby-node.jsadd this line:config.removeLoader('images')You'll also need to add
image-webpack-loaderto your site:npm install --save-dev image-webpack-loaderEnjoy!
v0.11.0Compare 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.jsmoved insidegatsby-node.js. If you had added apost-build.jsmodule to your code, this function should now be exported fromgatsby-node.js. A simple way to make the change is to simply requirepost-build.jsthere e.g.exports.postBuild = require('./post-build'). Thanks to @LukeSheard for this! #273staticis split into two stages,build-cssandbuild-htmlandproductionis 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 gatsbyjs/gatsby#279
Some highlights:
.babelrcpassed to webpack.react-hmrerather than being overwritten in develop.js.mdreizin/gatsby-plugin-robots-txt
v1.6.2Compare Source
Bug Fixes
v1.6.1Compare Source
Bug Fixes
v1.6.0Compare Source
Features
v1.5.6Compare Source
Bug Fixes
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.