-
-
Notifications
You must be signed in to change notification settings - Fork 391
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
🐠️ babel@7 📦️ upgrades #31
Conversation
Tried to do this as Tests all pass and build is working. This may be a decent first step for prep with #4.
|
😅 Whew. |
Hey @JeromeFitz thanks very much for the PR 💪 I haven't had a chance just yet to have a look, but hope to get it over the weekend. |
Very cool. As a heads up, in testing some stuff locally I was inadvertently using the Sorry about that. I look to have blown up the spot in the free tier for December. 😞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @JeromeFitz, just testing this out and everything is looking good. Just have some questions.
🐠️ babel@7 - ⬆️ Upgrade from babel@6 ✨️ taskr - Instead of babel/cli 📦️ package.json - ⬆️ upgrades TODO: Verify Major Version Upgrades of: - eslint-plugin-jest@22.1.2 - react-testing-library@5.4.2 - regenerator-runtime@0.13.1
⬆️ - eslint-plugin-jest@22.1.2 - react-testing-library@5.4.2 - regenerator-runtime@0.13.1 📈️ Test Suites: 1 passed, 1 total Tests: 10 passed, 10 total Snapshots: 4 passed, 4 total
This should get travis working.
Cypress is not keen on babel.config.js (babel@7) just yet.
We probably don't want these in the repo.
- Prefer @babel/cli over taskr - Move __tests__ as they are not being ignored
Thanks for looking into this @garmeeh ! Removed One caveat, I couldn't get the |
`next@7.0.2-canary.35` was the implementation - Dedupe only items with unique key: [5800](vercel/next.js#5800) In upgrading all the packges in this PR, some versions were not working (not sure why). I've tested with the latest `canary` from `next` and everything is passing.
🐠️ next/babel Since we rely on `next` they handle presets through `next/babel` and we can modify if we want. (skeleton left in place) 🔥️ unused packages These are all handled by `next`: - @babel/runtime (`regenerator-runtime`) - @babel/preset-env - @babel/preset-react - babel-core - babel-loader And not used by `next-seo` I believe. `flatten` should have been removed via `taskr` commit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good 💪, just two small comments. Once they are addressed I am happy to merge 😄
If the suggested change works for excluding the tests from compiling, let's move the tests back.
📦️ #.#.# = Specific Versions - Was having a terrible time with `npm install` and `^` in package.json. - Is it cool to do this for now? - - I didn't want to just move to `yarn` because I was running into npm troubles 🐠️ babel Added: - babel-core@7.0.0-bridge.0 => needed until jest moves to babel@7 - babel-minify Presets: - Removed the empty objects 🃏️ jest - Putting in the blank values was breaking the tests 🔥️ @babel/plugin-proposal-object-rest-spread 🚚️ test - Moved __tests__ back - Have an extra `rimraf` removing them from the `build`.
Can't seem to dismiss, let me know if you'd like anything else. 👍 Added Should reduce the size a bit: packagephobia?next-seo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💪 Nice one!
Word up. Thanks for going over everything! 💯️ |
🐠️ babel@7
📦️ package(-lock).json
next
)