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

Upgrade lodash version as they have fixed one vulnerability #11828

Closed
1 task
sukrut-gs opened this issue Jul 13, 2020 · 2 comments
Closed
1 task

Upgrade lodash version as they have fixed one vulnerability #11828

sukrut-gs opened this issue Jul 13, 2020 · 2 comments
Labels
i: enhancement i: needs triage outdated A closed issue/PR that is archived due to age. Recommended to make a new issue

Comments

@sukrut-gs
Copy link

Feature Request

  • I would like to work on this feature!

Is your feature request related to a problem?
A concise description of what the problem is. Ex. I have an issue when [...]

Describe the solution you'd like

Describe alternatives you've considered.

Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?
Upgrade lodash version as they have fixed one vulnerability.

@babel-bot
Copy link
Collaborator

Hey @sukrut-gs! 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."

@existentialism
Copy link
Member

@sukrut-gs thanks for the issue, but this is fixed in #11818 (and since we use ^ range for the dep you shouldn't need to wait for a Babel release, you can either remove node_modules or remove it from your lockfile and reinstall)

@JLHwung JLHwung closed this as completed Jul 13, 2020
@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 Oct 13, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
i: enhancement i: needs triage outdated A closed issue/PR that is archived due to age. Recommended to make a new issue
Projects
None yet
Development

No branches or pull requests

4 participants