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

PLAT-103297: Investigate and remove shrinkwrap when dependency issue is resolved #214

Merged
merged 5 commits into from
Mar 25, 2020

Conversation

JayCanuck
Copy link
Member

Deleted shrinkwrap then generated a clean new package-lock.json. Required a couple incidental additional updates for ESLint breaking changes that didn't follow semver.

Enact-DCO-1.0-Signed-off-by: Jason Robitaille jason.robitaille@lge.com

@ryanjduffy
Copy link
Contributor

@JayCanuck - Can you elaborate a bit for posterity on the eslint changes?

Copy link
Contributor

@germboy germboy left a comment

Choose a reason for hiding this comment

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

:shipit:

@germboy germboy merged commit 70abd56 into develop Mar 25, 2020
@ryanjduffy ryanjduffy deleted the feature/remove-shrinkwrap branch March 25, 2020 21:58
@JayCanuck
Copy link
Member Author

@JayCanuck - Can you elaborate a bit for posterity on the eslint changes?

For clarity/posterity, the eslint/prettier changes were a result the ^ usage in devDependencies.
I like to use ^ in devDependencies for flexibility, while direct dependencies are exact (and npm releases shrinkwrapped. Prettier and import eslint plugin introduced lint-breaking changes contrary to semver policy. The commands/pack.js change is a result of prettier improving it's parsing ability, detecting new things to format correct. And the import change sets an explicit order for importing. This is done as a result of a known existing bug import-js/eslint-plugin-import#601 which accidentally omits "interna". It's planned to be fixed plugin-side in their 3.0 release and they're not planning any interim fixes, sadly, so it's up to us to explicitly declare as a workaround.

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.

None yet

3 participants