You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yep, I've pointed that out also to ZEIT team and we need to colaborate on it.
I picture it like this:
now
composer deps are installed if composer.json is in place
now dev
vendor is in .gitignore
composer deps are installed if composer.json is in place only once, for the first time
we need to track if composer.json or composer.lock is changed and re-install composer deps
There is way I think, but it takes so much time to do it, because you have to publish pkg on npmjs to use it in now dev, thus we need to cooperate with ZEIT in this thing.
At this moment my project has a
.nowignore
file to prevent the composervendor
directory from uploading to now.When I run this same project with
now dev
I get an error because thevendor
directory is not found. This makes sense because it is ignored.This should however be resolved by either:
now dev
, but this seems to make it really slow.vendor
directory during a development run. But how can that be done?The text was updated successfully, but these errors were encountered: