-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade version of node #47
Comments
I've had success in migrating Happy to open a PR 👍 |
@stephenwf Thanks for the tips! If you have cycles to draft a PR that would be amazing! ✨ |
@stephenwf We are needing to get this project updated to a new version of Node for both projects that use it at IU. You mentioned opening a PR back when this came up in 2022. Is that still a possibility? Thanks! |
I'll try and find some time this week 👍 |
@stephenwf Any thoughts on whether you think you'll have cycles to work on this in the next month? |
Have pushed up #68 |
Node 14 will be EOL in about half a year so timeliner needs to be upgraded by then. Currently building with the latest node release (node 18) fails due to package.json requirements on old dependencies. (I'm seeing that
@fesk/webpack-config
depends on an oldnode-sass
which may be the source of the failures.) Thus it may be a good time to reexamine the build process and see if it should be updated to move away from FESK and use more standard build tools.The text was updated successfully, but these errors were encountered: