Error trying to use experimental-backend command line flag

nsw7 · August 14, 2023, 1:10am

getting an error trying to use the experimental-backend flag to create a new d1 db.

I am on wrangler 3.5.0

Unknown arguments: experimental-backend, experimentalBackend

anon9246926 · August 14, 2023, 4:55am

Based to the following pull request, the experimental backend is now the default ergo passing this option is no longer required.

github.com/cloudflare/workers-sdk

chore: make D1's experimental backend the default

cloudflare:main ← cloudflare:rozenmd/default-experimental-backend-on

opened 03:45PM - 24 Jul 23 UTC

rozenmd

+15 -15

Fixes #3667 **What this PR solves / how to test:** `wrangler d1 create <d…bname>` `wrangler d1 info <dbname>` **Associated docs issue(s)/PR(s):** - N/A **Author has included the following, where applicable:** - ~[ ] Tests~ - [x] Changeset ([Changeset guidelines](https://github.com/cloudflare/workers-sdk/blob/main/CONTRIBUTING.md#changesets)) **Reviewer is to perform the following, as applicable:** - Checked for inclusion of relevant tests - Checked for inclusion of a relevant changeset - Checked for creation of associated docs updates - Manually pulled down the changes and spot-tested

Version Packages

cloudflare:main ← cloudflare:changeset-release/main

opened 11:10AM - 21 Jul 23 UTC

github-actions[bot]

+99 -117

This PR was opened by the [Changesets release](https://github.com/changesets/act…ion) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## [email protected] ### Minor Changes - [#3604](https://github.com/cloudflare/workers-sdk/pull/3604) [`c3ff1c2b`](https://github.com/cloudflare/workers-sdk/commit/c3ff1c2b599c99f4915dad0362c7570cc2fa2bf3) Thanks [@dario-piotrowicz](https://github.com/dario-piotrowicz)! - Add the option to add the `eslint-plugin-next-on-pages` eslint plugin to developers creating a new Next.js app with eslint enabled ## @cloudflare/[email protected] ### Minor Changes - [#3675](https://github.com/cloudflare/workers-sdk/pull/3675) [`f753f3af`](https://github.com/cloudflare/workers-sdk/commit/f753f3afb7478bb289b39c44b33acbcefe06e99a) Thanks [@1000hz](https://github.com/1000hz)! - chore: upgrade `miniflare` to [`3.20230724.0`](https://github.com/cloudflare/miniflare/releases/tag/v3.20230724.0) ## [email protected] ### Minor Changes - [#3649](https://github.com/cloudflare/workers-sdk/pull/3649) [`e2234bbc`](https://github.com/cloudflare/workers-sdk/commit/e2234bbc2fc06c201dd5f256357084c86789891c) Thanks [@JacobMGEvans](https://github.com/JacobMGEvans)! - Feature: 'stdin' support for 'secret:bulk' Added functionality that allows for files and strings to be piped in, or other means of standard input. This will allow for a broader variety of use cases and improved DX. This implementation is also fully backward compatible with the previous input method of file path to JSON. ```bash # Example of piping in a file > cat ./my-file.json | wrangler secret:bulk # Example of piping in a string > echo '{"key":"value"}' | wrangler secret:bulk # Example of redirecting input from a file > wrangler secret:bulk < ./my-file.json ``` - [#3675](https://github.com/cloudflare/workers-sdk/pull/3675) [`f753f3af`](https://github.com/cloudflare/workers-sdk/commit/f753f3afb7478bb289b39c44b33acbcefe06e99a) Thanks [@1000hz](https://github.com/1000hz)! - chore: upgrade `miniflare` to [`3.20230724.0`](https://github.com/cloudflare/miniflare/releases/tag/v3.20230724.0) ### Patch Changes - [#3610](https://github.com/cloudflare/workers-sdk/pull/3610) [`bfbe49d0`](https://github.com/cloudflare/workers-sdk/commit/bfbe49d0d147ab8e32944ade524bc85f7f6f0cf3) Thanks [@Skye-31](https://github.com/Skye-31)! - Wrangler Capnp Compilation This PR replaces logfwdr's `schema` property with a new `unsafe.capnp` object. This object accepts either a `compiled_schema` property, or a `base_path` and array of `source_schemas` to get Wrangler to compile the capnp schema for you. - [#3579](https://github.com/cloudflare/workers-sdk/pull/3579) [`d4450b0a`](https://github.com/cloudflare/workers-sdk/commit/d4450b0a095c3b31fdc09a7af2e3336048c7be70) Thanks [@rozenmd](https://github.com/rozenmd)! - fix: remove --experimental-backend from `wrangler d1 migrations apply` This PR removes the need to pass a `--experimental-backend` flag when running migrations against an experimental D1 db. Closes #3596 - [#3623](https://github.com/cloudflare/workers-sdk/pull/3623) [`99baf58b`](https://github.com/cloudflare/workers-sdk/commit/99baf58b7c35e85c90e1f6df4cea841f31c0a709) Thanks [@RamIdeas](https://github.com/RamIdeas)! - when running `wrangler init -y ...`, the `-y` flag is now passed to npx when delegating to C3 - [#3668](https://github.com/cloudflare/workers-sdk/pull/3668) [`99032c1e`](https://github.com/cloudflare/workers-sdk/commit/99032c1e500132e16f0c1027cb4cba0c59823656) Thanks [@rozenmd](https://github.com/rozenmd)! - chore: make D1's experimental backend the default This PR makes D1's experimental backend turned on by default. - [#3579](https://github.com/cloudflare/workers-sdk/pull/3579) [`d4450b0a`](https://github.com/cloudflare/workers-sdk/commit/d4450b0a095c3b31fdc09a7af2e3336048c7be70) Thanks [@rozenmd](https://github.com/rozenmd)! - feat: implement time travel for experimental d1 dbs This PR adds two commands under `wrangler d1 time-travel`: Use Time Travel to restore, fork or copy a database at a specific point-in-time. Commands: wrangler d1 time-travel info <database> Retrieve information about a database at a specific point-in-time using Time Travel. Options: --timestamp accepts a Unix (seconds from epoch) or RFC3339 timestamp (e.g. 2023-07-13T08:46:42.228Z) to retrieve a bookmark for [string] --json return output as clean JSON [boolean] [default: false] wrangler d1 time-travel restore <database> Restore a database back to a specific point-in-time. Options: --bookmark Bookmark to use for time travel [string] --timestamp accepts a Unix (seconds from epoch) or RFC3339 timestamp (e.g. 2023-07-13T08:46:42.228Z) to retrieve a bookmark for [string] --json return output as clean JSON [boolean] [default: false] Closes #3577 - [#3592](https://github.com/cloudflare/workers-sdk/pull/3592) [`89cd086b`](https://github.com/cloudflare/workers-sdk/commit/89cd086ba0429651a30e8287c1e9e660d2fef6d0) Thanks [@penalosa](https://github.com/penalosa)! - fix: Only log dev registry connection errors once - [#3384](https://github.com/cloudflare/workers-sdk/pull/3384) [`ccc19d57`](https://github.com/cloudflare/workers-sdk/commit/ccc19d57e0b6a557c39bedbbb92ec4e52c580975) Thanks [@Peter-Sparksuite](https://github.com/Peter-Sparksuite)! - feature: add wrangler deploy option: --old-asset-ttl [seconds] `wrangler deploy` immediately deletes assets that are no longer current, which has a side-effect for existing progressive web app users of seeing 404 errors as the app tries to access assets that no longer exist. This new feature: - does not change the default behavior of immediately deleting no-longer needed assets. - allows users to opt-in to expiring newly obsoleted assets after the provided number of seconds hence, so that current users will have a time buffer before seeing 404 errors. - is similar in concept to what was introduced in Wrangler 1.x with <https://github.com/cloudflare/wrangler-legacy/pull/2221>. - is careful to avoid extension of existing expiration targets on already expiring old assets, which may have contributed to unexpectedly large KV storage accumulations (perhaps why, in Wrangler 1.x, the reversion <https://github.com/cloudflare/wrangler-legacy/pull/2228> happened). - no breaking changes for users relying on the default behavior, but some output changes exist when the new option is used, to indicate the change in behavior. - [#3678](https://github.com/cloudflare/workers-sdk/pull/3678) [`17780b27`](https://github.com/cloudflare/workers-sdk/commit/17780b279998db00732406633958dc35eecaa70f) Thanks [@1000hz](https://github.com/1000hz)! - Refined the type of `CfVars` from `Record<string, unknown>` to `Record<string, string | Json>`