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.

Sign up for GitHub

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

Jump to bottom

Any plans to address deprecation warnings? #1062

Closed
jhfoo opened this issue Jul 23, 2018 · 2 comments
Closed

Any plans to address deprecation warnings? #1062

jhfoo opened this issue Jul 23, 2018 · 2 comments
Labels
good for beginners help wanted

Comments

@jhfoo
Copy link

jhfoo commented Jul 23, 2018

There's a list of deprecation warnings installing Strider. A sample as follows:

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: 'native-or-bluebird' is deprecated. Please use 'any-promise' instead.

Will the code author accept submissions to fix them?
@knownasilya
Copy link
Member

Would totally accept submissions. Although minimatch will be hard to address since it's in almost every dependency.

@snyk-bot snyk-bot mentioned this issue Feb 4, 2020
Merged
@murindwaz murindwaz mentioned this issue Feb 4, 2020
Open
@knownasilya
Copy link
Member

Closing for #1080, also v2.1.0 addressed a few.

@Bhanditz Bhanditz mentioned this issue Nov 25, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good for beginners help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@knownasilya @jhfoo