[FEATURE] Allow custom node_modules path

[alfonsogrondo]

In my organization we have a monolith application that for a number of reasons has two root folders for front-end and back-end separation.

This means the Sonatype plugin cannot locate the node_modules folder since the config is tied to look for $PROJECT_ROOT/node_modules instead of (for example) $PROJECT_ROOT/frontend/node_modules

Is it possible to request a feature to specify a path to node_modules (possibly even multiple node modules)?

A suggestion for a solution is to add a free text field to the settings config to allow a comma separated list of node_module locations.

Ideally of course we would avoid such a project structure but I wanted to ask if it's something to consider as a feature?

Many Thanks

Al

cc @bhamail / @DarthHater

[DarthHater]

Hi @alfonsogrondo ! So recently we introduced a file that's called .sonatype-config. My thought is within this file, maybe we could add a npm block and under that the ability to provide config for npm/yarn specifically?

[alfonsogrondo]

Hey @DarthHater, let's pretend I didn't take a whole 14 months to reply here!

A npm block in the .sonatype-config file sounds ideal.