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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade deprecated npm packages #743

Closed
szyn opened this issue Mar 29, 2018 · 5 comments 路 Fixed by #940
Closed

Upgrade deprecated npm packages #743

szyn opened this issue Mar 29, 2018 · 5 comments 路 Fixed by #940
Assignees

Comments

@szyn
Copy link
Member

szyn commented Mar 29, 2018

When installing packages with npm, I get the following warnings:

npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated babel-preset-es2015@6.24.1: 馃檶  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

It's just a warning, but I think it's a good idea to upgrade the packages!
If you don't mind, I'll make changes that and create pull requests.

@hiroyuki-sato
Copy link
Contributor

hiroyuki-sato commented Jun 15, 2018

@szyn JFYI. #797 has been created. It update babel-preset-es2015.

@muga
Copy link
Member

muga commented Jun 15, 2018

@szyn @hiroyuki-sato sorry, I was not aware of this ticket. We started working on upgrading Node.js v8.x #797. Please take a look and let me know if you have any concerns/suggestions.

@muga
Copy link
Member

muga commented Jun 19, 2018

I will merge #797 into master and include it in next version. Please take a look and feel free to comment anywhere when you get a chance.

@hiroyuki-sato
Copy link
Contributor

@muga I succeed build dda03af (merged #797) in my enviromnet. Thank you!

@muga
Copy link
Member

muga commented Jun 20, 2018

@hiroyuki-sato thank you for testing. It looks like other warnings are still there though:-)

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 a pull request may close this issue.

3 participants