Skip to content
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

Migrate to React Hot Loader v4 #4500

Merged
merged 1 commit into from
Mar 13, 2018
Merged

Migrate to React Hot Loader v4 #4500

merged 1 commit into from
Mar 13, 2018

Conversation

noelebrun
Copy link

Simple migration to React Hot Loader v4 done. All in-browser test works fine on my side.

Unit test are not passing. They were already failing on origin/v2 before my changes.

Thanks,

Noé

@noelebrun
Copy link
Author

#4314

@KyleAMathews
Copy link
Contributor

Thanks!

@KyleAMathews KyleAMathews merged commit 7a5adb1 into gatsbyjs:v2 Mar 13, 2018
@noelebrun noelebrun deleted the topic/4314-react-hot-loader-v4 branch March 13, 2018 11:47
@noelebrun
Copy link
Author

Np 😃For the v2 change, should we use the v2 branch? Cause there's a few test failing on the branch and the branch can't be merged.
Thx!

@KyleAMathews
Copy link
Contributor

What v2 change? This PR was to v2 :-)

@noelebrun
Copy link
Author

I mean for the next PR on the v2 😃

@KyleAMathews
Copy link
Contributor

Oh right :-) yeah! Keep them coming!

m-allanson added a commit to m-allanson/gatsby that referenced this pull request Apr 4, 2018
* v2:
  Docgen improvements (gatsbyjs#4757)
  adjust createLocation calls after gatsbyjs#4714 (gatsbyjs#4805)
  Update breaking changes doc
  use basename for router instead of prefixing in link (gatsbyjs#4714)
  Fix inlined styles with path-prefixing (gatsbyjs#4717)
  Publish
  Upgrade & format
  [v2][wip] Upgrade Gatsby v2 to webpack 4 (gatsbyjs#4588)
  fix some jsdoc parsing bits (gatsbyjs#4675)
  [v2] fix wrong merge
  Publish
  Migrate to React Hot Loader v4 (gatsbyjs#4500)
  [v2] Fix deleteNodes deprecation (gatsbyjs#4453)
  Publish
  Switch to latest version of sharp to prevent yarn/npm errors (gatsbyjs#4417)

# Conflicts:
#	packages/gatsby/package.json
#	packages/gatsby/src/utils/webpack-utils.js
#	yarn.lock
@jlengstorf
Copy link
Contributor

Hiya @noelebrun! 👋

This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here.

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

  1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (We’ve got t-shirts and hats, plus some socks that are really razzing our berries right now.)
  2. If you’re not already part of it, we just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again! 💪💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants