deps: upgrade several more deps' majors #879
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- @types/node v13 -> v14
- Node 13.x was EoL at the beginning of June per
https://github.com/nodejs/Release
- @types/fs-extra was recently updated to v9, so can bump it to match
the recent upgrade of fs-extra itself to v9
- rollup-plugin-sourcempas v0.5 -> v0.6
- requires Node 10+, which we've already bumped to in the last dep
upgrade, otherwise no breaking changes
- @rollup/plugin-node-resolve v7 -> v9
- requires Node 10+, which we've already bumped to in the last dep
upgrade, other breaking changes don't affect our usage
- use the new `DEFAULTS` variables to pull out the extensions instead
of having a comment referencing them
- rename this `DEFAULTS` to `RESOLVE_DEFAULTS` and Babel's
`DEFAULT_EXTENSIONS` to `DEFAULT_BABEL_EXTENSIONS` so that there's
less naming confusion around these
- fix execa being pinned to v4.0.0 exactly
- this was probably accidentally added as such because sometimes
`yarn add dep@x` sets it exactly instead of to the caret version
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/formium/tsdx/m11oys6lt |
agilgur5
added
the
scope: dependencies
agilgur5
commented
Sep 21, 2020
This was referenced Sep 21, 2020
|
Deleted all the stale old Greenkeeper branches associated with all versions of the deps upgraded: |
paul-vd
pushed a commit
to EezyQuote/tsdx
that referenced
this pull request
Dec 1, 2020
- @types/node v13 -> v14
- Node 13.x was EoL at the beginning of June per
https://github.com/nodejs/Release
- @types/fs-extra was recently updated to v9, so can bump it to match
the recent upgrade of fs-extra itself to v9
- rollup-plugin-sourcempas v0.5 -> v0.6
- requires Node 10+, which we've already bumped to in the last dep
upgrade, otherwise no breaking changes
- @rollup/plugin-node-resolve v7 -> v9
- requires Node 10+, which we've already bumped to in the last dep
upgrade, other breaking changes don't affect our usage
- use the new `DEFAULTS` variables to pull out the extensions instead
of having a comment referencing them
- rename this `DEFAULTS` to `RESOLVE_DEFAULTS` and Babel's
`DEFAULT_EXTENSIONS` to `DEFAULT_BABEL_EXTENSIONS` so that there's
less naming confusion around these
- fix execa being pinned to v4.0.0 exactly
- this was probably accidentally added as such because sometimes
`yarn add dep@x` sets it exactly instead of to the caret version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
@types/node v13 -> v14
https://github.com/nodejs/Release
@types/fs-extra was recently updated to v9, so can bump it to match
the recent upgrade of fs-extra itself to v9
rollup-plugin-sourcempas v0.5 -> v0.6
upgrade, otherwise no breaking changes
@rollup/plugin-node-resolve v7 -> v9
upgrade, other breaking changes don't affect our usage
DEFAULTSvariables to pull out the extensions insteadof having a comment referencing them
DEFAULTStoRESOLVE_DEFAULTSand Babel'sDEFAULT_EXTENSIONStoDEFAULT_BABEL_EXTENSIONSso that there'sless naming confusion around these
fix execa being pinned to v4.0.0 exactly
yarn add dep@xsets it exactly instead of to the caret versionTags
This is basically a follow-up to #678 , including fixing the accidental exact
execapin created. Also adds the@types/fs-extraupgrade that didn't exist back then.Closes a few related Greenkeeper PRs: