Clarify use and lifecycle of modules imports

[jpravetz]

Problem/Motivation

Clarify lifecycle of modules in documentation

Proposed changes

Provide documentation on

• how is the dependency list built (from config file, package.json, function node imports?)
  • CommonJS vs ES6 modules, can we use either?
• how to purge an old dependency
  • delete any reference will stop it from being loaded, but remains installed unless you clean out node_modules?
  • it is safe to delete node_modules?
• how to specify a new dependency including version (precise syntax), or does it every time always try to get the latest?
• Can we edit package.json? Or is that always generated? Must changes be in .config.modules.json,?

And hints as well, on how to make a module available globally in all function nodes. This seems the best approach, but it took me quite awhile to figure it out. Other people may also be as dense as I am:

• create a function node that runs on startup that imports a module
• the code within the function node then adds it to global

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!