svend Comments - Answer Overflow

svend

•Created by Silvan on 3/24/2025 in #workers-and-pages-discussions

.dev.vars end up in server bundle

.dev.vars is also present in server folder with cloudflare/vite-plugin v0.1.15 used and react-router v.7. Wrangler (as of v4.4) does complain that there is no environment found in the redirected wrangler.json though. (build/server/wrangler.json) - maybe it is including .dev.vars as fallback in these cases? Ref https://github.com/cloudflare/workers-sdk/commit/1987a79d43158ebc6eeb54b2102214060266b6d7 Would prefer .dev.vars to <not go anywhere near the server build 😉

26 replies

CDCloudflare Developers

•Created by zsmooth on 3/18/2025 in #wrangler

that wasn't it... it turns out that the

Will just steal this thread to follow up on the "deploy" command and use of cloudflare-vite plugin 🙈 It seems wrangler now: - appends to worker name on its own initiative and doing it twice, also including CLOUDFLARE_ENV? - Goes into build/server and finds wrangler.json without any reference to it in my config files? Can find it in .wrangler/deploy/config.json, but not sure where that file comes from. Vite plugin perhaps? Is this also documented somewhere? Edit: appending is mentioned here, but not the twice part: https://github.com/cloudflare/workers-sdk/tree/main/packages/vite-plugin-cloudflare#cloudflare-environments Example 1 gives worker name workername-production:

 
.env.production:
RUNTIME_ENV=production
CLOUDFLARE_ENV=$RUNTIME_ENV

./wrangler.json
{
"name": "workername",
"env": {
   "production": {
       "name": "workername",
    }
  }
}

 
.env.production:
RUNTIME_ENV=production
CLOUDFLARE_ENV=$RUNTIME_ENV

./wrangler.json
{
"name": "workername",
"env": {
   "production": {
       "name": "workername",
    }
  }
}

Example 2 gives worker name workername-production-production...:

 
.env.production:
RUNTIME_ENV=production
CLOUDFLARE_ENV=$RUNTIME_ENV

./wrangler.json
{
"name": "workername",
"env": {
   "production": {//no name key here}
  }
}

 
.env.production:
RUNTIME_ENV=production
CLOUDFLARE_ENV=$RUNTIME_ENV

./wrangler.json
{
"name": "workername",
"env": {
   "production": {//no name key here}
  }
}

Deploy command is:

vite build --mode production && wrangler deploy --env production

vite build --mode production && wrangler deploy --env production

Wrangler 4.4, @cloudflare/vite-plugin: 0.1.15 Warning during deploy:

Using redirected Wrangler configuration.
 - Configuration being used: "build/server/wrangler.json"
 - Original user's configuration: "wrangler.json"
 - Deploy configuration file: ".wrangler/deploy/config.json"
▲ [WARNING] Processing build/server/wrangler.json configuration:

    - No environment found in configuration with name "production".
      Before using `--env=production` there should be an equivalent environment section in the
  configuration.
  
      Consider adding an environment configuration section to the wrangler.json file:

      [env.production]

Using redirected Wrangler configuration.
 - Configuration being used: "build/server/wrangler.json"
 - Original user's configuration: "wrangler.json"
 - Deploy configuration file: ".wrangler/deploy/config.json"
▲ [WARNING] Processing build/server/wrangler.json configuration:

    - No environment found in configuration with name "production".
      Before using `--env=production` there should be an equivalent environment section in the
  configuration.
  
      Consider adding an environment configuration section to the wrangler.json file:

      [env.production]

15 replies

CDCloudflare Developers