-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
chore(deps): update dependencies #338
chore(deps): update dependencies #338
Conversation
Jest 26 dropped node 8 support jestjs/jest#9423
Codecov Report
@@ Coverage Diff @@
## master #338 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 208 208
Branches 42 42
=========================================
Hits 208 208 Continue to review full report at Codecov.
|
Hi @hamzahamidi! I saw at #275 (comment) that you're taking over maintainership of this repo. Thanks a lot! Thanks for these updates here. This one, in particular, looks like it's necessary for guaranteed support of ESLint 6: - "@typescript-eslint/parser": "^1.10.2",
+ "@typescript-eslint/parser": "^3.0.0", because
It looks like there were several automatically generated PRs from the in-between-maintainers times, that look like they would have granted ESLint 6 support (with ESLint 5 compatibility) before the 10.0.0 release of this package. This would have been done by using Thanks again! |
perf: Trigger patch release since commit message in #338 was malformed.
since commit message in prettier#338 was malformed.
since commit message in #338 was malformed.
🎉 This PR is included in version 10.1.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Thank you!! |
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those.
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those.
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those. Closes: zulip#4120
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those. Fixes: zulip#4120
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those. Also run `yarn yarn-deduplicate && yarn` as prompted by `tools/test deps`. Fixes: zulip#4120
We're not quite ready for ESLint 7 because several of our plugins don't support it yet. Fair enough; 6.8.0 is the latest on ESLint 6. Apart from that, I was aware of some specific minimum versions of things we'll need, so I just made those tweaks on that basis: - `prettier-eslint` at 10.1.1 is the minimum that I'm confident has full ESLint 6 support; see my comment there at prettier/prettier-eslint#338 (comment). - `eslint-config-airbnb` at 18.1.0, I'd discovered earlier, has 6.8.0 as a peer dep. I checked to see if 18.1.0 is the latest version, and it is. Otherwise, I just followed the trail of peer dependency warnings until I could run `rm -rf node_modules && yarn` without any warnings. It's likely that this would have given the same outcome for `prettier-eslint` and `eslint-config-airbnb`, but it's not what I did for those. Fixes: zulip#4120
This reverts commit 01593b3. We should redo the upgrade when we can take a version of `prettier-eslint` in which `core-js` is re-introduced as a dependency; prettier/prettier-eslint#348 is the closest issue for that. The commands listed in 01593b3 should make it easy to redo the upgrade mechanically, and without having to think about rebase conflicts. The version (11.0.0) of `prettier-eslint` that we got in 01593b3 was affected by a bug with symptoms quite similar to ones we see with the Prettier VSCode extension (a.k.a. `esbenp.prettier-vscode`) at version 5 and above [1]. We'll have to resolve the problem with the VSCode extension at some point (see discussion for a likely way we'll do that), since we can't assume it will always be fine to stay below version 5, and version 5 causes problems because of an intentional design change. But, from experimentation, it appears that this time the problem is just caused by `prettier-eslint` not having the right version of `core-js`. At 10.1.0, the latest version before the problem starts happening, we can remove `node_modules/prettier-eslint/node_modules/core-js`, and we see the problem. Version 10.1.1, which ships with the problem, removed `core-js` as a dependency, and an issue with a different bad symptom (prettier/prettier-eslint#348) was soon filed, and a PR (prettier/prettier-eslint#359) came along to add `core-js` back in. We can't just back up to version 10.1.0, because then we're at risk of it not working with ESLint 6 [2]. So, just revert the entire ESLint 6 upgrade. [1] https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/SOLVED.3A.20Prettier.20auto-formatting/near/893164 [2] prettier/prettier-eslint#338 (comment)
This reverts commit 01593b3. We should redo the upgrade when we can take a version of `prettier-eslint` in which `core-js` is re-introduced as a dependency; prettier/prettier-eslint#348 is the closest issue for that. The commands listed in 01593b3 should make it easy to redo the upgrade mechanically, and without having to think about rebase conflicts. The version (11.0.0) of `prettier-eslint` that we got in 01593b3 was affected by a bug with symptoms quite similar to ones we see with the Prettier VSCode extension (a.k.a. `esbenp.prettier-vscode`) at version 5 and above [1]. We'll have to resolve the problem with the VSCode extension at some point (see discussion for a likely way we'll do that), since we can't assume it will always be fine to stay below version 5, and version 5 causes problems because of an intentional design change. But, from experimentation, it appears that this time the problem is just caused by `prettier-eslint` not having the right version of `core-js`. At 10.1.0, the latest version before the problem starts happening, we can remove `node_modules/prettier-eslint/node_modules/core-js`, and we see the problem. Version 10.1.1, which ships with the problem, removed `core-js` as a dependency, and an issue with a different bad symptom (prettier/prettier-eslint#348) was soon filed, and a PR (prettier/prettier-eslint#359) came along to add `core-js` back in. We can't just back up to version 10.1.0, because then we're at risk of it not working with ESLint 6 [2]. So, just revert the entire ESLint 6 upgrade. [1] https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/SOLVED.3A.20Prettier.20auto-formatting/near/893164 [2] prettier/prettier-eslint#338 (comment)
A redo of 01593b3, after we reverted it in e3e8d9a. One thing we realized [1] is that we don't have to wait for `prettier-eslint` to fix the problem of its missing `core-js` dependency; we can provide it ourselves. We do so by just adding it directly to our own `dependencies`. So, in addition to the commands listed in 01593b3, also run `yarn add core-js@^3.1.4`. We choose ^3.1.4 because that's what was there before prettier/prettier-eslint#338. The open PR I mention in e3e8d9a (prettier/prettier-eslint#359) suggests ^3.6.5, but it seems to do so at random; might as well approach as closely as possible a configuration that we know works. Now, we have the ESLint upgrade, and format-on-save works as expected. [1] https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/SOLVED.3A.20Prettier.20auto-formatting/near/982426 Fixes: #4120
dependencies
devDependencies