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

[cli][redwood] Update frontend framework detection in vc dev #5036

Merged
merged 3 commits into from
Aug 13, 2020

Conversation

styfle
Copy link
Member

@styfle styfle commented Aug 13, 2020

This PR uses the the new property added in PR #5034 to determine if a framework has a frontend runtime defined.

It also reverts a couple workarounds add in PR #4937 which was added for RedwoodJS which is no longer necessary since RedwoodJS defines a frontend framework the same way Next.js does.

@styfle styfle changed the title [cli][redwood] Update frontend framework detection [cli][redwood] Update frontend framework detection in vc dev Aug 13, 2020
@styfle styfle marked this pull request as ready for review August 13, 2020 22:11
@styfle styfle requested a review from MaxLeiter August 13, 2020 22:11
Co-authored-by: Nathan Rajlich <n@n8.io>
@kodiakhq kodiakhq bot merged commit 6bb162e into master Aug 13, 2020
@kodiakhq kodiakhq bot deleted the ch1718/rw-dev-cleanup branch August 13, 2020 23:53
styfle added a commit that referenced this pull request Aug 14, 2020
The CLI doesn't depend on `@vercel/redwood` for `vc dev` since PR #5036 so we can remove it.

Similarly, zero config does not install `@vercel/next` or `@vercel/static-build` during `vc dev` so these can be removed too.

In the case where the user defines `builds` in vercel.json, the runtimes will be installed during the first run of `vc dev`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants