@pithy-sh/vite 0.6.1 → 0.7.0

package/dist/plugin.d.ts

@@ -89,8 +89,15 @@ export interface PithyPluginOptions {
     configFile?: string;
     /**
      * The environment this bundle is built for. Defaults to `ENVIRONMENT` in the process env, then
-     * `dev`. `pithy deploy --env <name>` is what threads a real value in, so a production bundle sees
-     * production's projection and a dev bundle sees dev's.
+     * `CLOUDFLARE_ENV`, then `dev`. `pithy deploy --env <name>` is what threads a real value in, so a
+     * production bundle sees production's projection and a dev bundle sees dev's.
+     *
+     * **`CLOUDFLARE_ENV` is in that chain because it is the name Cloudflare's own tooling uses (#579).**
+     * It is what `@cloudflare/vite-plugin` reads to select the wrangler stanza, so a hand-run
+     * `CLOUDFLARE_ENV=staging vite build` — the Cloudflare-native spelling, and what CI reaches for —
+     * produced staging's Worker config and this plugin's **dev** projections, silently. That is the same
+     * class of miss as the deploy defect itself: one environment, two names, and only one of them read.
+     * `ENVIRONMENT` stays first, so nothing that already sets it changes behavior.
      */
     environment?: string;
 }

package/dist/plugin.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"plugin.d.ts","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":"AAcA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,MAAM,WAAW,WAAW;IAC1B,mGAAmG;IACnG,IAAI,EAAE,MAAM,CAAC;IACb;;;OAGG;IACH,OAAO,EAAE,KAAK,CAAC;CAChB;AAED;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,YAAI,gBAAgB,EAAE,iBAAiB,EAAE,WAAW,EAAE,MAAM,EAAE,WAAW,CAAU,CAAC;AAEnH,yDAAyD;AACzD,MAAM,MAAM,eAAe,GAAG,CAAC,OAAO,kBAAkB,CAAC,CAAC,MAAM,CAAC,CAAC;AAElE,+FAA+F;AAC/F,MAAM,WAAW,kBAAkB;IACjC;;;OAGG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB;AAED;;;;;;;;GAQG;AACH,wBAAgB,KAAK,CAAC,OAAO,GAAE,kBAAuB,GAAG,WAAW,CA4FnE"}
+{"version":3,"file":"plugin.d.ts","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":"AAcA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,MAAM,WAAW,WAAW;IAC1B,mGAAmG;IACnG,IAAI,EAAE,MAAM,CAAC;IACb;;;OAGG;IACH,OAAO,EAAE,KAAK,CAAC;CAChB;AAED;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,YAAI,gBAAgB,EAAE,iBAAiB,EAAE,WAAW,EAAE,MAAM,EAAE,WAAW,CAAU,CAAC;AAEnH,yDAAyD;AACzD,MAAM,MAAM,eAAe,GAAG,CAAC,OAAO,kBAAkB,CAAC,CAAC,MAAM,CAAC,CAAC;AAElE,+FAA+F;AAC/F,MAAM,WAAW,kBAAkB;IACjC;;;OAGG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;;;;;;;;OAWG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB;AAED;;;;;;;;GAQG;AACH,wBAAgB,KAAK,CAAC,OAAO,GAAE,kBAAuB,GAAG,WAAW,CA4FnE"}

package/dist/plugin.js

@@ -37,7 +37,7 @@ const PITHY_PLUGIN_HOOKS = [
 * heard of: a screen branches on `enabled`, it does not guard on whether the module exists.
 */
 function pithy(options = {}) {
-	const environment = options.environment ?? process.env.ENVIRONMENT ?? "dev";
+	const environment = options.environment ?? process.env.ENVIRONMENT ?? process.env.CLOUDFLARE_ENV ?? "dev";
 	let configFile = "";
 	let loading = null;
 	let server;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pithy-sh/vite",
-  "version": "0.6.1",
+  "version": "0.7.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -33,7 +33,7 @@
     "reset": "bun run clean && rm -rf node_modules"
   },
   "peerDependencies": {
-    "@pithy-sh/core": "^0.6.1",
+    "@pithy-sh/core": "^0.7.0",
     "vite": "^6.1.0 || ^7.0.0 || ^8.0.0"
   },
   "devDependencies": {

package/src/plugin.ts

@@ -104,8 +104,15 @@ export interface PithyPluginOptions {
   configFile?: string;
   /**
    * The environment this bundle is built for. Defaults to `ENVIRONMENT` in the process env, then
-   * `dev`. `pithy deploy --env <name>` is what threads a real value in, so a production bundle sees
-   * production's projection and a dev bundle sees dev's.
+   * `CLOUDFLARE_ENV`, then `dev`. `pithy deploy --env <name>` is what threads a real value in, so a
+   * production bundle sees production's projection and a dev bundle sees dev's.
+   *
+   * **`CLOUDFLARE_ENV` is in that chain because it is the name Cloudflare's own tooling uses (#579).**
+   * It is what `@cloudflare/vite-plugin` reads to select the wrangler stanza, so a hand-run
+   * `CLOUDFLARE_ENV=staging vite build` — the Cloudflare-native spelling, and what CI reaches for —
+   * produced staging's Worker config and this plugin's **dev** projections, silently. That is the same
+   * class of miss as the deploy defect itself: one environment, two names, and only one of them read.
+   * `ENVIRONMENT` stays first, so nothing that already sets it changes behavior.
    */
   environment?: string;
 }
@@ -120,7 +127,7 @@ export interface PithyPluginOptions {
  * heard of: a screen branches on `enabled`, it does not guard on whether the module exists.
  */
 export function pithy(options: PithyPluginOptions = {}): PithyPlugin {
-  const environment = options.environment ?? process.env.ENVIRONMENT ?? "dev";
+  const environment = options.environment ?? process.env.ENVIRONMENT ?? process.env.CLOUDFLARE_ENV ?? "dev";
   let configFile = "";
   // Memoize the promise, not the value: `load` runs concurrently for every virtual module a bundle
   // imports, and each `runnerImport` builds a fresh environment. One promise means one config load.