-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update dependencies #34
Comments
This will imply some rewriting in the |
I would suggest to migrate to |
"easier to maintain" -> sounds great! |
Hey, I took care for some - see the last pull request: Accessing PropTypes via the main React module is deprecated, use PropTypes instead. npm WARN deprecated [email protected]: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers npm WARN deprecated [email protected]: We're super 😸 excited that you're trying to use ES2015 syntax, but instead of continuing yearly presets 😭 , we recommend using babel-preset-env: npm install babel-preset-env. preset-env without options will compile ES2015+ down to ES5. And by targeting specific browsers, Babel can do less work and you can ship native ES2015+ to users 😎 ! Also, we are in the process of releasing v7, so give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and test it! Thanks so much for using Babel 🙏 , please give us a follow @babeljs for updates, join slack.babeljs.io for discussion and help support at opencollective.com/babel npm WARN deprecated [email protected]: Use uuid module instead npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support |
Thanks @noVaSon! I already merged the changes. Are other dependencies still outdated? |
Yes, there were depreciation warnigns about calling PropTypes from React main package. |
When all current Pull Requests are reviewed and merged - I think it is time to do an npm prune . |
These seem to be out of date again.. any plans to update? |
Hi @carthach! |
Better late than never! Cheers for replying Eric! |
We have outdated dependencies, nooooo :(
The text was updated successfully, but these errors were encountered: