-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add support for node 18 by updating node-sass #13493
Conversation
drop support for node 12
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
Reviewer - this PR has made changes to one or more package.json files. |
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13493/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/13493/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/13493/merge#BCU1XR#0 |
Was this checked on the forum before ? We can not ship this without an extensive set of tests and compatibility assessment from some of our existing dependencies. I will let @RaananW check tomorrow. |
Fair enough. I needed it, so I PR'd it. It'll have to happen eventually, feel free to treat it as a draft or to reject it. Cheers. |
It will for sure happen soon knowing @RaananW, I just want to be sure he can validate all the dependencies before merging it. |
@sebavan Oh by the way on the note of
There isn't really a "Development" section on the forum. Either that or I'm not invited :D . It would maybe be useful. |
You are correct, I think those conversations usually end up in either "feature requests" or "questions". cc @carolhmj our forum GURU |
Indeed, I also just realised "feature requests" doubles for this stuff. No worries, I'm happy knowing this now! |
Yup Feature Requests works fine for that :) |
Thanks so much for the PR. I would rather test before making changes. I agree - we should fully support node 18. But I am not 100% sure this is the only change. |
And drop support for node 12.
It's probably time, it's the next LTS :)
I have not fully tested it (too reliant on CI maybe), but it works in dev. It's possible it'll also work with node 19, but I did not try.