TypeScript dependency (70MB) is installed athough not really used by package

[medikoo]

Originally reported at serverless/serverless#7640

It attributes to way heavier (+70MB) Framework installation, and heavier standalone size (+30MB)

Regression was introduced with #375, which taken on board dependency-tree dependency which lists TypeScript as its prod dependency.

We probably should find some alternative for dependency-tree

[stevewillard]

Hmm... ok here is kind of a crazy idea:

What if we installed the enterprise-plugin (not the SDK, but the CLI command dependencies themselves) to another folder instead of node_modules. I'm not totally clear of the logistics around making that possible, and it would probably make development on the plugin more annoying since all the require paths would be relative (unless we somehow modified the NODE_PATH).

Anyways, the reason I'm throwing this idea out there is because it seems silly that node_modules, strictly necessary for the CLI, are getting bundled with functions. We can look for an alternative to dependency-tree, but I think the core issue is unnecessary dependencies are getting bundled.

[medikoo]

@stevewillard moving our dependencies around, wouldn't reduce project and binary size

Source of the issue is, that we've started to bundle/install TypeScript which is not needed and not used by the by project, and we need to recover from that.

I believe it's actually a bug on dependency-tree side that it unconditionally requires typescript.
I've opened a dedicated issue over there: dependents/node-dependency-tree#117

If they wouldn't want to opt-out, we would need to find some alternative, e.g. we can use https://github.com/medikoo/ncjsm#getdependeciesmodulepath-options---ignoremissing-false- which I believe would also be faster, I will just have to introduce an option to not resolve external (from node_modules) depenencies.