shouldn't you be putting your code repositories in something like c:/www folder, and using purely git to track it?
There's lots of 3rd party solutions for .dropboxignore personally I've used many of them and am not a fan of it (perl scripts, 3rd party apps, etc). I wish dropbox would natively implement .dropboxignore, but its probably never going to happen since only a small % of users voice their concerns for it. Average dropbox user probably doesn't care or doesn't know what a .dropboxignore is.
I do use git too. But it's nice to be able to jump between multiple computers without needing to push an incomplete commit to remote (when I get tired from sitting in front of desktop I switch to laptop to code in bed).
Also dropbox's 30 day version history did save me a couple times when I accidentally deleted something before committing. And not having to worry about losing the day's work even if your computer fails is good for peace of mind.
That said this hits a lot of edge cases with dropbox syncing since it's not built for this kind of workflow. Every time you do npm install it will cause thousands of files to sync. I have had the .git folder get corrupted when I start using it before it has fully synced. Or git would handle syncing internal symlinks/permissions/casing differently and I would need to rely on git to restore.
The only problem with using dropbox in this case, is if you accidentally dump node_modules inside of there, it really makes your file history revisions in dropbox messy.
That and if you have to sync with another PC at home makes your computer sluggish for like half an hour while its syncing
My solution to you is to have your code repos in another storage solution (not dropbox). Unfortunately you would have to pay for that too
Or, you could use a built in IDE that has a autosave local revision history. I know most of the brainstorm products have this feature, such as PHPstorm. This would prevent accidentally deleting something before committing
For incomplete commits / switching computers, I can't really think of any workarounds for this unfortunately. Dropbox is very convenient here. The only solution is to use something like teamViewer and remote into your desktop PC from your laptop
There's lots of 3rd party solutions for .dropboxignore personally I've used many of them and am not a fan of it (perl scripts, 3rd party apps, etc). I wish dropbox would natively implement .dropboxignore, but its probably never going to happen since only a small % of users voice their concerns for it. Average dropbox user probably doesn't care or doesn't know what a .dropboxignore is.