feat(gatsby-plugin-emotion): update plugin for emotion v10

[wKovacs64]

🎉 Emotion v10 is here! 🎉

• Update dependencies
• Update critical style handling
• Add Babel config for jsx pragma
• Update plugin install instructions
• Update Gatsby tutorial (part 4)
• Update the "using emotion" example

[emmatown]

FYI, we're likely going to be adding a babel preset for automatically adding the jsx pragma (emotion-js/emotion#1049)

[DSchau]

So, this seems to work for me but it isn't backwards compatible... what's the best way to deal with that

The peerDep handles it right? Requiring v10 of packages as peerDependencies should cover our bases there.

[wKovacs64]

The peerDep handles it right? Requiring v10 of packages as peerDependencies should cover our bases there.

Cool with me if peerDep bumps are good enough, just wasn't sure since bumping this plugin version by a minor or patch would convey non-breaking changes but an emotion v9 consumer's build will explode because the plugin now imports from @emotion/core. SSR critical styles are handled differently too, so those would be broken as well (if they got that far by bringing in the new peerDeps). I might be overthinking it, though. 😅

[DSchau]

since bumping this plugin version

Oh yeah. This would be a major version bump for this plugin! Misunderstood you there.

[wKovacs64]

Oh yeah. This would be a major version bump for this plugin! Misunderstood you there.

Cool. I bumped it to 10.0.0 to match emotion, but let me know if you/the team aren't a fan of skipping semver majors like that and I'll drop it to 3.0.0.

[DSchau]

@wKovacs64 I'm so sorry, that's my fault on that one!

If you could, could you revert that commit, e.g.

git revert f05f5a2

and then push that up to this branch. We actually use lerna to manage version bumping, so in this example, we'll automatically bump this plugin up to the next major version with lerna (which will create the patch) rather than as part of this commit!

Before we merge, we'll want to edit the description with something like

BREAKING: moved to emotion10, which changes some core APIs and switches to scoped packages

so that we can get that info in the changelog.

[wKovacs64]

@DSchau Sure, no problem. Will that handle bumping the using-emotion example project, too?

[DSchau]

Will that handle bumping the using-emotion example project, too

It will!

[wKovacs64]

Word.

[wKovacs64]

Before we merge, we'll want to edit the description

I assume whoever merges do that, but let me know if you need me to do something else in that regard.

[joe-bell]

❤️

[DSchau]

@wKovacs64 I'll take a look at this today and get it merged in. Thanks to both you and @mitchellhamilton!

[DSchau]

Let's merge. Thanks again!

[DSchau]

Successfully published:
 - gatsby-plugin-emotion@3.0.0

[wKovacs64]

Before we merge, we'll want to edit the description with something like

BREAKING: moved to emotion10, which changes some core APIs and switches to scoped packages

so that we can get that info in the changelog.

😅

[wKovacs64]

Doesn't look like lerna updated the example, I'll send another PR for that.

[DSchau]

@wKovacs64 ah, yep 😢 Good catch on the missed breaking change. My fault!