You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see we actually encourage people to use native modules. This is dangerous because every time we update Electron these native modules will not work anymore.
We should strongly advise AGAINST using native modules in extensions after all. And if nothing helps, tell people that each time we release a new version of VS Code they will have to recompile the prebundled native modules against the same node.js version that VS Code ships with.
Suggest to add a warning as @bpasero suggested to the question. We should keep the question.
Notice: native modules bundled with an extension must be recompiled with every new version of VS Code against the same node.js version that VS Code ships with.
Refs: https://code.visualstudio.com/docs/extensions/patterns-and-principles#_common-questions
I see we actually encourage people to use native modules. This is dangerous because every time we update Electron these native modules will not work anymore.
We should strongly advise AGAINST using native modules in extensions after all. And if nothing helps, tell people that each time we release a new version of VS Code they will have to recompile the prebundled native modules against the same node.js version that VS Code ships with.
/cc @egamma
The text was updated successfully, but these errors were encountered: