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 am a developer on VSCode and wanted to reach out to inform you that this extension is either using or having a dependency to a node module "natives" that will soon no longer be supported in VSCode once we updated to node.js 8.x (as part of our Electron 2.0 update which is planned for the near term).
It would be great if this dependency could be avoided by either not depending on it anymore or updating the dependencies to newer versions so that this module is no longer pulled in.
As soon as any code in your extension (including node_modules) calls require("natives") we will throw an exception to prevent this module from getting loaded.
If this is just a devDependency and the module is never loaded in production, then you can ignore this issue and just close it!
Thanks for the heads up, It looks like natives is a dependency of Gulp which is not part of the distribution, just part of the testing story, so I don't anticipate this causing any issues.
I'll verify that Gulp isn't declared in the distribution dependencies (since it is dev only) and update if needed.
Hi,
I am a developer on VSCode and wanted to reach out to inform you that this extension is either using or having a dependency to a node module "
natives
" that will soon no longer be supported in VSCode once we updated to node.js 8.x (as part of our Electron 2.0 update which is planned for the near term).The full graph is:
It would be great if this dependency could be avoided by either not depending on it anymore or updating the dependencies to newer versions so that this module is no longer pulled in.
As soon as any code in your extension (including
node_modules
) callsrequire("natives")
we will throw an exception to prevent this module from getting loaded.If this is just a
devDependency
and the module is never loaded in production, then you can ignore this issue and just close it!More details in microsoft/vscode#47569
Thanks!
Ben
VSCode Team
The text was updated successfully, but these errors were encountered: