{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 霸刀☆藐视天下 的问题《Laravel Homestead - where to run npm (virtual mach》','https://www.manongdao.com/q-989174.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am running a Laravel Homestead Vagrant box on Windows 10 host. Currently, I am compiling assets (running npm run dev) inside the vm. It's pretty slow at times, and I usually have problems with symlinks, running watchers etc. - in short, there is more configuration required that I think is necessary,
Would it be better to compile assets directly on the host (Windows) machine? Are there any 'gotchas' I should have in mind? Does it really matter on what machine JavaScript assets are compiled? That is, will the compiled version work 'in production' no matter where I compiled it?
YES. It is all right. I just tested it with laravel 5.6.