Update Vercel config to replace depricated build base #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates to use @vercel/go instead of @now/go for build, as @now/go is depricated and no longer functions
|
Hey @someshkar, hope you're okay? Cheers, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hiya @someshkar
Love your project :)
I just went to try it out on Vercel, and noticed that build fails because the base in the now.json is still using the older
@now/goimage, which is deprecated.Here's a quick PR which updates that to the newer
@vercel/go:)I've tested it out by deploying a demo instance to
https://whois-api-zeta.vercel.app/and it seems to work all great.