We seem to have reached a pace where we are aligning each subsequent V8 release with a new Module Version number, which is currently off by three
https://github.com/nodejs/node/blob/master/src/node_version.h#L71-L105
Should we consider bumping Module version number to 63 in https://github.com/nodejs/node/pull/16271
/cc @nodejs/tsc @nodejs/v8
I think we already discussed this somewhere. The current module version is aligned with Electron IIRC.
@targos I've pinged the people over in the electron maintainers slack to chime in
A couple things:
From Electron's point of view, most tools that help people with automatically rebuilding Node modules against a certain target use node-abi, which contains a rather simple map and doesn't really care about the logic behind the number.
Without electron-rebuild, we're currently telling people to configure npm. I can't really see how this would break people, but @zcbenz might have more informed opinions.
@addaleax I totally agree with all of those points, just figured that bumping by three isn't likely to break anything and will make things less confusing. Open to closing this if you think it is a non starter
@MylesBorins I鈥檓 just worried it gives the false impression that alignment with the V8 version is something we want to provide in the future, even though that鈥檚 not really what鈥檚 happening and we can鈥檛 promise it
I agree with @addaleax
I agree with @addaleax.
I agree with @addaleax as well.
I agree with @addaleax as well.
Closing
Most helpful comment
@MylesBorins I鈥檓 just worried it gives the false impression that alignment with the V8 version is something we want to provide in the future, even though that鈥檚 not really what鈥檚 happening and we can鈥檛 promise it