3 ms·

If you're a Node/JavaScript developer, you might want to keep code in Dropbox, but putting node_modules in there will tank it.

• b3kart 7y ago
  Does it not suggest that node_modules in the source directory isn't a good idea to begin with?
  • gitgud 7y ago
    The project directory would contain everything needed for that project including node_modules (which is generated from the package.json) Every nodejs project is structured this way... node_modules is always sitting next to your src...
  • edanm 7y ago
    It is usually git-ignored, which means it isn't part of the "real" source directory (the one that is shared with other devs). It's a temporary output of the build process, in essence.
• dylan604 7y ago
  I don't use Dropbox, nor am I a Node dev. Why would a node_modules directory tank Dropbox?
  • somehnguy 7y ago
    Because NPM's first operation is to pull in half the internet as modules so you can write 'Hello World' on your webpage. Thats too many files for the Dropbox client to handle.
  • deleted 7y ago
    [deleted]