Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[now dev] Installed packages in vendordo not exists #12

Open
ties-v opened this issue Aug 8, 2019 · 1 comment
Open

[now dev] Installed packages in vendordo not exists #12

ties-v opened this issue Aug 8, 2019 · 1 comment

Comments

@ties-v
Copy link
Contributor

ties-v commented Aug 8, 2019

At this moment my project has a .nowignore file to prevent the composer vendor directory from uploading to now.

When I run this same project with now dev I get an error because the vendor directory is not found. This makes sense because it is ignored.

This should however be resolved by either:

  • Also run composer install in now dev, but this seems to make it really slow.
  • Also copy the vendor directory during a development run. But how can that be done?
@f3l1x
Copy link
Collaborator

f3l1x commented Aug 8, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants