-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
node V12 test is really needed? #2660
Comments
I tried a new JS feature |
from my side the v12 tests could be removed, I never saw a different result between v12 and v14 as long as I look at them. End of life of v12 is 2022-04-30.
there is already #2408 but I found no time so far to start with this. |
Thanks for your input and I understand your reasoning , alas:
As for your usecase: Would be easy to polyfill the replaceAll and add it to the code with a little note to remove it once node12 support is removed |
Yes, I can make a polyfill for BTW, for But to test browser(or electron)-sided parts, I still think that v12 test is meaningless. Of course, there could be cases of really old browsers like Midori or IE, but MM is supporting them still? (I'm not sure.) Especially Anyway, I understand your points. This issue could be closed. |
Node V12 is not
Active LTS
. It is on theMaintenance LTS
stage.Current dependency
Electron 13.2.3
is based on Node v14.17, Chromium 91, V8 9.1And upcoming
Electron 14.0.0
will be based on Node v14.17, Chromium 93, V8 9.3So the node V12 test is obsoleted at this moment, I think.
The text was updated successfully, but these errors were encountered: