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

Warnings during npm install #50

Open
anvk opened this issue Jan 7, 2016 · 5 comments
Open

Warnings during npm install #50

anvk opened this issue Jan 7, 2016 · 5 comments
Assignees
Milestone

Comments

@anvk
Copy link
Collaborator

anvk commented Jan 7, 2016

I get those errors every single time I run npm install

npm WARN package.json [email protected] license should be a valid SPDX license expression
npm WARN deprecated [email protected]: use gulp-rimraf instead
npm WARN deprecated [email protected]: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0

We should resolve those.

@anvk anvk added this to the 1.0.0 milestone Jan 7, 2016
@anvk anvk mentioned this issue Jan 7, 2016
@carloscarcamo
Copy link
Collaborator

I already fixed the first two warnings (I can send a pull request if you want) but, I don't know why the warning about lodash, maybe some of the dependencies require an old version of lodash...
I also have the following, do you have those also?

> [email protected] postinstall /home/carloscarcamo/workspace/node/TweetGeoViz/node_modules/history
> node ./npm-scripts/postinstall.js

npm WARN deprecated [email protected]: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
npm WARN optional dep failed, continuing [email protected]
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm

Maybe we could get a badge from https://david-dm.org/JaredHawkins/TweetGeoViz to check which modules are out of date.

@anvk
Copy link
Collaborator Author

anvk commented Jan 7, 2016

@carloscarcamo just feel free to change lo-dash version in package.json.

Feel free to update modules to make them up to date. But what I would do is - test app every time you update a module. usually React libraries have big changes in them, you would bump one version up and then the whole app stops working. But if it works - then why not.

What about fsevents and npmconf I believe other libraries rely on those, so we cannot do much about them

@carloscarcamo
Copy link
Collaborator

In package.json you have: "lodash": "^3.10.1", I think another library uses a previous version of lodash. I will try to update the outdated modules and test the project locally before send a pull request.

carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
carloscarcamo added a commit to mozillaSv/TweetGeoViz that referenced this issue Jan 8, 2016
- Some dependencies updated
- Dependencies status badges
@anvk
Copy link
Collaborator Author

anvk commented Jan 15, 2016

Looks like it is complete

@anvk anvk closed this as completed Jan 15, 2016
@carloscarcamo
Copy link
Collaborator

I have new warnings during npm install

npm WARN deprecated [email protected]: WARNING: This package has been renamed to react-router-redux. See https://github.com/rackt/react-router-redux/issues/80
npm WARN deprecated [email protected]: Please use postcss-loader instead of autoprefixer-loader
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]

I didn't change any package related to react because I'm still learning react...

@carloscarcamo carloscarcamo reopened this Jan 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants