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

build: update configstore to include patched legacy dot-prop #187

Closed
wants to merge 64 commits into from
Closed

build: update configstore to include patched legacy dot-prop #187

wants to merge 64 commits into from

Conversation

cmdcarini
Copy link

This continues the work from sindresorhus/configstore#72 and sindresorhus/dot-prop#61 and updates update-notifier to include these changes.

Please merge to a branch other than master and publish to v2.5.1

sindresorhus and others added 30 commits August 16, 2020 15:07
We rewrite `options.pkg` to hold only the information we need (name and
version). So when we call node with check.js we no longer pass the
entire content of package.json as a command line argument.

This resolves #57.
And extract most of the code into a separate module.
The number of modules pulling update-notifier in as a dependency has ballooned from 100+ to [600+](https://www.npmjs.com/browse/depended/update-notifier?offset=606)
* feat: center-align message via boxen@0.6.0

* test: simplify use of clear-require
@ruyadorno
Copy link

Given that dot-prop is a transitive dependency and the configstore declaration in the package.json file uses the caret range definition, this change is not really needed.

Any consumer of update-notifier just needs to run npm audit fix OR npm install update-notifier@2.5.0 in order to fix the vulnerability warning from dot-prop.

Thanks for the contribution! 😊

@ruyadorno ruyadorno closed this Aug 18, 2020
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.