The tool now assumes not only namespaced packages but instead every npm package.
For some reason the specified folder for the dependency was not used but instead dependencies was splitted and we take the directory based on the name of the package. This was not intended bug the initial purpose of this library was to work with every package not only namespaced.
Hello, do you plan releasing a version that includes this change?
It's not included in the latest 0.9.2 version.
I ended up hacking a bit my deployment process to workaround exactly this issue.
Issue
Description
The tool now assumes not only namespaced packages but instead every npm package. For some reason the specified folder for the dependency was not used but instead dependencies was splitted and we take the directory based on the name of the package. This was not intended bug the initial purpose of this library was to work with every package not only namespaced.
Type of change