Update node-emoji #8
Conversation
|
@joelschou Sorry for not responding! Apparently I wasn't watching my own repo and didn't get any notification of your PR 🤦♂️ I have just upgraded all code and dependencies to match the master branch from yarn, so your PR should not be necessary anymore. I will release yurnalist 0.3.0 with the changes. |
|
Thanks! |
|
@joelschou FYI I decided to make it 1.0.0. And then I upgraded all dependencies to latest which resulted in 1.1.0 😄 |
|
Versioning is the worst! |
|
@joelschou I messed up something in the release so I unpublished the new versions for now. Not sure what happened yet... |
|
@joelschou all set now. Don't know how I messed it up. I unpublished 1.0.0 and 1.1.0 and because NPM didn't allow me to publish 1.0.0 again it became 1.0.1 😅 |
|
Damn it 😞 The problem still persisted. Locally everything is fine testing the build, but somehow after publishing the paths are messed up and the require call throws. I will have a look at it later with a fresh mind. Sorry for the noise. |
|
@joelschou I blindly copied the npmignore contents from the yarn repo which excluded the dist folder since yarn uses a different approach to publishing new versions. This messed up the module on publish. I could not re-publish 1.0.0 because it was already un-published (as was 1.0.1), so the latest version is now 1.0.2. |
|
Next time I'm doing a pre-release first, as I should have 😄 |
|
Thanks! |
Gatsby uses yurnalist in its CLI tools, but yurnalist uses an old version node-emoji which is missing quite a few really great ones, such as 🤷♂️. I can't use the newer node-emoji in my Gatsby-powered site, because yarn is too smart.