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
It'd be nice to not rely on npmjs.com during install/runtime of the extension, from a very quick sketch:
# cd yaml.novaextension
tar -zcvf node_modules.tar.gz package.json package-lock.json node_modules
du -hs node*# 18M node_modules# 3.3M node_modules.tar.gz
Then the extension could untar the node_modules on startup and remove the tar (or rename to something like node_modules.tar.gz.bk so it knows not to do it again, but the tar is still there if needed. Alternatively it could update the package.json (and lock?) version(s) to that of the extension and only run the untar if the version has changed.
There could be a command to reinstall if required too, e.g. Extensions → YAML → Reinstall Server perhaps.
The text was updated successfully, but these errors were encountered:
It'd be nice to not rely on npmjs.com during install/runtime of the extension, from a very quick sketch:
Then the extension could untar the node_modules on startup and remove the tar (or rename to something like
node_modules.tar.gz.bk
so it knows not to do it again, but the tar is still there if needed. Alternatively it could update the package.json (and lock?) version(s) to that of the extension and only run the untar if the version has changed.There could be a command to reinstall if required too, e.g. Extensions → YAML → Reinstall Server perhaps.
The text was updated successfully, but these errors were encountered: