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

Update debug package to version 4.0.0 #8674

Open
ryanelian opened this Issue Sep 11, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@ryanelian

ryanelian commented Sep 11, 2018

Bug Report

Current Behavior

I am getting warnings in my CI due to updated debug package:

warning @babel/core > debug@3.2.4: `debug` versions 3.2.0-3.2.2 break Node 4. Users of node LTS and onward (modern Node versions): please upgrade to `debug@4` or above as soon as possible. Node 4 users: please pin to `debug@>=3.2.3 <4` as it will be the last version range that supports Node@4.
warning @babel/core > @babel/traverse > debug@3.2.4: `debug` versions 3.2.0-3.2.2 break Node 4. Users of node LTS and onward (modern Node versions): please upgrade to `debug@4` or above as soon as possible. Node 4 users: please pin to `debug@>=3.2.3 <4` as it will be the last version range that supports Node@4.

Input Code

npm install

Expected behavior/code

No warnings in my CI.

Babel Configuration (.babelrc, package.json, cli command)

Not applicable

Environment

  • Babel version(s): @babel/core@7.0.0, @babel/traverse@7.0.0
  • Node/npm version: 10/6.2.0
  • OS: Linux, Windows
  • Monorepo [e.g. yes/no/Lerna]: no
  • How you are using Babel: Node API

Possible Solution

npm install debug

On both @babel/core and @babel/traverse packages.

Additional context/Screenshots

image

@babel-bot

This comment has been minimized.

Show comment
Hide comment
@babel-bot

babel-bot Sep 11, 2018

Collaborator

Hey @ryanelian! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

Collaborator

babel-bot commented Sep 11, 2018

Hey @ryanelian! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment