Confusing way of working

[leoj3n]

This threw me off:

./node_modules/bit-docs/lib/configure/node_modules/bit-docs-generate-html/site/static/build/917c51373c902dc4a003c7fd949774c5/node_modules/

As you can see, bit-docs/lib/configure/node_modules/bit-docs-generate-html has yet another nested node_modules directory... So therefore, changes made to for instance:

./node_modules/bit-docs/lib/configure/node_modules/bit-docs-prettify/prettify.less

Will not show up, because bit-docs-generate-html is downloading bit-docs-prettify into it's own node_modules directory.

This was confusing to me when trying to see changes I was making in the bit-docs-prettify that was one nested node_modules up.

Not sure if this can be avoided, but this issue will at least serve as a reminder to myself, and might help someone else who isn't seeing their changes when trying to make edits in the same naive way.

[leoj3n]

Really, this compounds the "nannying" problem that I had mentioned here:

bit-docs/bit-docs#22

Because, even if you symlink the second-level nested node_modules or use file: syntax, the remote npm package will ultimately be getting downloaded into the third-level nested build/HASH/node_modules directory.

[leoj3n]

Related: bit-docs/bit-docs#25