Skip to content

chore(core): fix lodash resolution #869

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

Closed
wants to merge 2 commits into from
Closed

chore(core): fix lodash resolution #869

wants to merge 2 commits into from

Conversation

L2jLiga
Copy link

@L2jLiga L2jLiga commented Nov 27, 2019

Description

Changed lodash version in resolution field of main package.json

Motivation and Context

All packages has lodash 4.17.15 pinned but in main package.json resolution is lodash 4.17.14

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

All packages has lodash 4.17.15 pinned but in main package.json resolution is lodash 4.17.14
@escapedcat
Copy link
Member

looks ok to me, what do you think @byCedric ?

@neerajvkarma
Copy link

Is this issue related to https://www.npmjs.com/advisories/1065.

@L2jLiga
Copy link
Author

L2jLiga commented Feb 4, 2020

close since it was done in #886

@L2jLiga L2jLiga closed this Feb 4, 2020
@L2jLiga L2jLiga deleted the chore/fix-lodash-resolution branch February 4, 2020 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants