@donpuerto what peoblems exactly are you running into?
Installing NPM can be a real PITA but at the end it'll work.
afaik there's no way to get the dir downloaded - would'nt make any sense either - and it's realy a whole bunch of files as well...

@frezno I have the latest installed vagrant, homestead box, and node.js. I also updated npm. But when i install using npm install --no-bin-links, i got multiple errors. Either locally or in VM. So i was thinking if it is possible to download manually the node module folder.

Disadvantage what i noted installing NPM.

• -It takes your precious time to dowload the file, about 120mb. This is a huge file per download per project.
• -I think it is incompatible in windows, i google this around even on this thread i heard alot of unsuccessfull stories during installation.

@donpuerto I have running npm on Win 7 and Win 10 - but on both OS it took me several tries to get it installed.
not running vagrant and homestead though.

sometimes an unsuccessfull install is caused by a cache problem.:
First of all clear the cache: npm cache clean
Now create a separate cache dir, eg md c:\npm-cache
And now let npm know where the new cache dir is located: npm config set cache c:\npm-cache

if that doesn't help, maybe you will find an answer here:
https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

@frezno, i followed your procedure mate, but still i got error.

VM Trial

• npm cache clean
• c:\npm-cache
• npm config set cache c:\npm-cache
• npm install --global gulp ### ===> Error

npm install --global gulp

npm install --no-bin-links

@donpuerto you must not use /home/vagrant/Code/projectflyer/c:nmp-cache but you have to use an valid path, eg /usr/bin/nmp-cache for the cache directory. The c:/ i mentioned in my post is the drive and the path is just an example. You have to modify it that it fits your system.

But setting a different cache director might not help.
As said, read the npm wiki at the link i mentioned above and take a look further down at that wiki as well:
https://github.com/npm/npm/wiki/Troubleshooting#running-a-vagrant-box-on-windows-fails-due-to-path-length-issues

I can't be much of a help when it comes to vagrant and homestead since i don't use it and am not familiar with it.

@frezno ok, i tried also in local, but still got error.

npm install --no-bin-links

Running Elixir Gulp

did you do what the error message suggested:
run npm rebuild node-sass