[D1] initial wrangler d1 export

[rozenmd]

LDW CR: CR-851796

Author has addressed the following

• Tests
  • TODO (before merge)
  • Included
  • Not necessary because: calling an internal endpoint with its own tests (Update: these will be added as a fast-follow -- see [D1] initial wrangler d1 export #5425 (comment))
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Included
  • Not necessary because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s): Add wrangler d1 export command cloudflare-docs#13683
  • Not necessary because:

[changeset-bot]

🦋 Changeset detected

Latest commit: fe7114c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
wrangler	Minor
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-wrangler-5425

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/5425/npm-package-wrangler-5425

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-wrangler-5425 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-create-cloudflare-5425 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-cloudflare-kv-asset-handler-5425

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-miniflare-5425

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-cloudflare-pages-shared-5425

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8472051916/npm-package-cloudflare-vitest-pool-workers-5425

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.39.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240320.0
workerd	1.20240320.1	1.20240320.1
workerd --version	1.20240320.1	2024-03-20

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[codecov]

Codecov Report

Attention: Patch coverage is 30.76923% with 27 lines in your changes are missing coverage. Please review.

Project coverage is 72.24%. Comparing base (3e5a932) to head (fe7114c).
Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##           main    #5425       +/-   ##
=========================================
+ Coverage      0   72.24%   +72.24%     
=========================================
  Files         0      324      +324     
  Lines         0    16752    +16752     
  Branches      0     4283     +4283     
=========================================
+ Hits          0    12102    +12102     
- Misses        0     4650     +4650     

Files	Coverage Δ
packages/wrangler/src/d1/index.ts	88.88% <100.00%> (ø)
packages/wrangler/src/d1/export.ts	28.94% <28.94%> (ø)

... and 322 files with indirect coverage changes

[mrbbot]

Approved, but I think this should still have tests for argument validation, accepting multiple tables and sending a correctly structured request. I recognise timing is tight here though, and the functionality looks good. Would you be able to create a ticket to track adding testing as a fast-follow?

[rozenmd]

Yep @mrbbot, can do

[lrapoport-cf]

Approved, but I think this should still have tests for argument validation, accepting multiple tables and sending a correctly structured request. I recognise timing is tight here though, and the functionality looks good. Would you be able to create a ticket to track adding testing as a fast-follow?

for posterity: it appears the fast follow issue is #5442, to be closed by #5444