Determine what, if any, third party NPM modules should be installed by default

[lance]

The runtime image could install a curated set of NPM modules that are there by default. This would allow users to avoid having to specify these in a package.json file. In simple cases, this would mean that the user could avoid an npm install step altogether.

[lance]

Based on off-github conversations with @slinkydeveloper, we should at least consider bundling the top three or four test frameworks with the runtime image.

[lance]

I am moving this issue to faas-js-runtime-image since whatever modules are installed will be installed globally on the image itself, and not as a part of this framework.

[slinkydeveloper]

Sorry I badly explained myself. I mean that in kfn we should support them to install locally and let the generated package.json use them. But the runtime image itself don't need it at all imo

[lance]

@slinkydeveloper I think having a handful of pre-installed modules on the image is potentially good for build time - less to install. Then, if kfn has a --test-framework=[jest|mocha|jasmine|tape], a package.json can be written with the appropriate test script, and there is nothing to install if we have all of those already in the global node_modules.