Repository navigation
Replace stale vercel scripts with wrangler equivalents - #29
Merged
Merged
Conversation
Vercel was removed from the actual deployment (now a Cloudflare Worker via wrangler.jsonc / worker/index.js), but package.json still pointed dev/deploy at the vercel CLI.
This file contains hidden or 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
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.
package.json still had
vercel dev/vercel --prodfrom before the migration to Cloudflare Workers. This repo now deploys via wrangler (see wrangler.jsonc and .github/workflows/deploy.yml), so the scripts now call wrangler directly.No vercel dependency was present in package.json, and there's no lockfile in this repo. README does not reference the vercel commands.
Tested with
npm test— all 20 tests pass.