chore: migrate wrangler commands to deno tasks#275
Conversation
- Add wrangler npm specifier to imports - Add wrangler:* tasks for dev, deploy, and tail commands - Enables removal of package.json and package-lock.json Co-Authored-By: Warp <agent@warp.dev>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
adblock-compiler | 8e76b52 | Feb 09 2026, 02:50 AM |
There was a problem hiding this comment.
Pull request overview
This PR aims to finish migrating Wrangler usage from npm scripts to deno task commands, aligning worker development/deploy operations with the repo’s Deno-based workflow.
Changes:
- Adds a set of
wrangler:*Deno tasks for local dev, deploy, and tailing logs. - Adds a Wrangler npm specifier to
deno.jsonimports.
| "wrangler": "deno run -A npm:wrangler", | ||
| "wrangler:dev": "deno run -A npm:wrangler dev", | ||
| "wrangler:deploy": "deno run -A npm:wrangler deploy", | ||
| "wrangler:tail": "deno run -A npm:wrangler tail", | ||
| "wrangler:tail:deploy": "deno run -A npm:wrangler deploy --config wrangler.tail.toml", | ||
| "wrangler:tail:dev": "deno run -A npm:wrangler dev --config wrangler.tail.toml", | ||
| "wrangler:tail:logs": "deno run -A npm:wrangler tail adblock-compiler-tail" |
There was a problem hiding this comment.
The new tasks invoke npm:wrangler without a version, while the import map pins Wrangler to npm:wrangler@^4.63.0. Using the unversioned specifier can cause Deno to resolve a different Wrangler version (and churn deno.lock) than the one you intended to pin. Consider updating the tasks to call the versioned specifier (or otherwise ensure they resolve via the pinned version) so local dev/deploy stays deterministic.
| "wrangler": "deno run -A npm:wrangler", | |
| "wrangler:dev": "deno run -A npm:wrangler dev", | |
| "wrangler:deploy": "deno run -A npm:wrangler deploy", | |
| "wrangler:tail": "deno run -A npm:wrangler tail", | |
| "wrangler:tail:deploy": "deno run -A npm:wrangler deploy --config wrangler.tail.toml", | |
| "wrangler:tail:dev": "deno run -A npm:wrangler dev --config wrangler.tail.toml", | |
| "wrangler:tail:logs": "deno run -A npm:wrangler tail adblock-compiler-tail" | |
| "wrangler": "deno run -A npm:wrangler@^4.63.0", | |
| "wrangler:dev": "deno run -A npm:wrangler@^4.63.0 dev", | |
| "wrangler:deploy": "deno run -A npm:wrangler@^4.63.0 deploy", | |
| "wrangler:tail": "deno run -A npm:wrangler@^4.63.0 tail", | |
| "wrangler:tail:deploy": "deno run -A npm:wrangler@^4.63.0 deploy --config wrangler.tail.toml", | |
| "wrangler:tail:dev": "deno run -A npm:wrangler@^4.63.0 dev --config wrangler.tail.toml", | |
| "wrangler:tail:logs": "deno run -A npm:wrangler@^4.63.0 tail adblock-compiler-tail" |
| "wrangler": "deno run -A npm:wrangler", | ||
| "wrangler:dev": "deno run -A npm:wrangler dev", | ||
| "wrangler:deploy": "deno run -A npm:wrangler deploy", |
There was a problem hiding this comment.
PR description says this “completes the migration to Deno” and that package.json/package-lock.json/node_modules can be removed after merge, but the repo still relies on Node/Wrangler in CI (e.g., npm install -g wrangler) and workflows/scripts reference package.json for version bumps. Either adjust the PR description/usage notes to reflect the remaining Node dependency, or include follow-up changes to workflows/versioning to make package.json truly optional.
Summary
Completes the migration to Deno by adding wrangler tasks to
deno.json.Changes
wranglernpm specifier to importswrangler:*tasks for dev, deploy, and tail commandsUsage
After merging, you can remove
package.json,package-lock.json, andnode_modules/:Then use:
deno task wrangler:devinstead ofnpm run devdeno task wrangler:deployinstead ofnpm run deploydeno task wranglerfor arbitrary wrangler commandsCo-Authored-By: Warp agent@warp.dev