Wednesday, 11 December 2019

best practise for nested projects?

I'm building a CLI tool to bundle multiple purpose-build nodejs script tools to create, validate and delete cloud resources on AWS and soon Azure.The problem is that, if I load all of these as submodules I have to reinstall the AWS-SDK every time.I also tried installing them as dependancies, but our bitbucket enterprise is causing issues which results in timeouts and errors in npm install.Does anyone have any advice? maybe something with npm link or something else that I haven't considered yet?

Submitted December 11, 2019 at 02:26PM by Delta4o

No comments:

Post a Comment