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

Can we strip any packages that rely on deprecated dependencies? #239

Open
rednax1994 opened this issue Mar 10, 2017 · 1 comment
Open

Can we strip any packages that rely on deprecated dependencies? #239

rednax1994 opened this issue Mar 10, 2017 · 1 comment
Assignees
Labels

Comments

@rednax1994
Copy link

There are a couple of packages that are still using old packages as dependacies. When installing using meteor npm install, the following give a message:
npm WARN deprecated [email protected]: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
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]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: use uuid module instead

Could this be updates so packages like jade don't get used anymore?

@themeteorchef themeteorchef self-assigned this Mar 13, 2017
@themeteorchef
Copy link
Owner

I'd have to look at what package is dependent on Jade, but will consider this in the 5.0 release (since it's a WARN it's fairly low priority).

@themeteorchef themeteorchef changed the title update packages using depreciated packages Can we strip any packages that rely on deprecated dependencies? Mar 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants