Skip to content

Conversation

jvasseur
Copy link
Contributor

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other: dependencies fix.

What is the current behavior? (You can also link to an open issue here)

When installing babel-loader, @ava/babel is installed with it while it's not used

What is the new behavior?

It's not installed anymore.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information:

Adding it to dependencies instead of devDependencies was probably a mistake, this fixes it.

@nicolo-ribaudo
Copy link
Member

Whoops thanks!

@nicolo-ribaudo nicolo-ribaudo merged commit a4d17c0 into babel:main Nov 10, 2020
@jvasseur jvasseur deleted the ava-dev-dependencies branch November 10, 2020 14:13
@pieh
Copy link

pieh commented Nov 10, 2020

Any chance we could get patch release with this change?

On top of installing it unnecessarily, it also cause some problems due to engines.node - excerpt from yarn installation:

error @ava/[email protected]: The engine "node" is incompatible with this module. Expected version ">=10.18.0 <11 || >=12.14.0 <13 || >=13.5.0". Got "10.16.0"
error Found incompatible module.

(@ava/[email protected]'s engines.node is more strict that of babel-loader itself )

@nicolo-ribaudo
Copy link
Member

Yup, I will release later today.

@nicolo-ribaudo
Copy link
Member

Published as 8.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants