Skip to content
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: pin stack-utils to 1.0.2 on legacy node tests #12365

Merged
merged 1 commit into from
Nov 16, 2020

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Nov 16, 2020

Q                       A
Fixed Issues? Fixes failing main tests on Node.js 6
License MIT

Will mark as ready for review once CI is green.

Closes #12364

Note that this PR does not mean Babel 7 does not support Node.js 6 because stack-utils is only used in jest-message-utils, it is not in Babel dependencies so we can pin it to a working version.

@babel-bot
Copy link
Collaborator

babel-bot commented Nov 16, 2020

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/32725/

@codesandbox-ci
Copy link

codesandbox-ci bot commented Nov 16, 2020

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 90abf24:

Sandbox Source
babel-repl-custom-plugin Configuration
babel-plugin-multi-config Configuration

@JLHwung JLHwung force-pushed the fix-broken-node-6-tests branch 2 times, most recently from a4cef0b to 3f1330a Compare November 16, 2020 14:49
yarn remove jest
yarn add --dev jest@24
# Pin stack-utils to 1.0.2 https://github.com/tapjs/stack-utils/issues/56
yarn set resolution --save stack-utils@npm:^1.0.1 1.0.2
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@merceyz Per docs

yarn set resolution --save stack-utils@^1.0.1 1.0.2

should work but it turns out the npm: protocol is required. Is that expected?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bug - yarnpkg/berry#1598

Copy link
Contributor Author

@JLHwung JLHwung Nov 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not meant for

yarn set resolution stack-utils 1.0.2

I mean the example usage

yarn set resolution stack-utils@^1.0.1 1.0.2

does not do the trick, but if I add npm:, it works as expected.

yarn set resolution stack-utils@npm:^1.0.1 1.0.2

Copy link
Contributor

@merceyz merceyz Nov 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, right, it's expected see yarnpkg/berry#1598 (comment). Though we might improve that

@JLHwung JLHwung marked this pull request as ready for review November 16, 2020 15:01
@JLHwung JLHwung merged commit 7850682 into babel:main Nov 16, 2020
@JLHwung JLHwung deleted the fix-broken-node-6-tests branch November 16, 2020 15:16
@github-actions github-actions bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Feb 16, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Fixes failing main
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants