Specifying a `-- <command>` or `--proxy` is deprecated and will be removed

Recently noticed this warning when running wrangler pages dev -- vite:

[WARNING] Specifying a `-- <command>` or `--proxy` is deprecated and will be removed in a future version of Wrangler.
 
   Build your application to a directory and run the `wrangler pages dev <directory>` instead.
   This results in a more faithful emulation of production behavior.

[WARNING] Specifying a `-- <command>` or `--proxy` is deprecated and will be removed in a future version of Wrangler.
 
   Build your application to a directory and run the `wrangler pages dev <directory>` instead.
   This results in a more faithful emulation of production behavior.

I'm curious what the suggestion is for users of vite or similar framework where there is no directory in dev mode?

2 Replies

Hello, I’m Allie!•9mo ago

Currently, some frameworks support using bindings in regular dev mode(see this blog post for details on which). As for other frameworks, the reason it was removed was that it doesn’t provide much functionality

The Cloudflare Blog

Blazing fast development with full-stack frameworks and Cloudflare

You can now use your framework’s development server while accessing D1 databases, R2 object stores, AI models, and more. Iterate locally in milliseconds to build sophisticated web apps that run on Cloudflare

Hello, I’m Allie!•9mo ago

Most frameworks don’t dump _headers, _redirects, or the _worker.js file until you build, in which case the wrangler proxy would just be straight proxying the framework dev server without any changes

Gaming

Programming

Specifying a `-- <command>` or `--proxy` is deprecated and will be removed