Skip to content

CHANGELOG.md

Latest commit

 

History

History
270 lines (155 loc) · 15.8 KB

CHANGELOG.md

File metadata and controls

270 lines (155 loc) · 15.8 KB

@varlock/vite-integration

1.2.0

2026-06-23

  • #827 (minor) - SvelteKit on Cloudflare now works with the standard varlockVitePlugin() — it auto-detects the @sveltejs/adapter-cloudflare adapter (configured in svelte.config.js or inline in vite.config) and injects the Workers env loader automatically. The same import now works across all deploy targets. varlockSvelteKitCloudflarePlugin is deprecated; install @varlock/cloudflare-integration alongside the vite plugin for Cloudflare deploys.

1.1.3

2026-06-03

  • #656 (patch) - add @encryptInjectedEnv and @disableProcessEnvInjection root decorators for encrypted deployments

1.1.2

2026-05-24

  • #708 - set __VARLOCK_ENV on failure so ENV proxy can initialize with partial data
  • #708 - styled html error page for varlock load failures in dev mode

1.1.1

2026-05-06

  • #690 - fix cloudflare + tanstack start + vite 6/7/8 compatibility

1.1.0

2026-05-02

  • #681 - Add --summary-stderr/--summary-file flags to varlock load and fullResult option to execSyncVarlock

1.0.1

2026-04-29

  • Bump to avoid conflict with accidental 1.0.0 publish (long time ago)

1.0.0

2026-04-29

  • Updated dependency varlock v1.0.0

0.2.10

Patch Changes

  • #542 02e82d0 - Fix Vitest workspace projects in monorepos: when running Vitest from the monorepo root using the projects config, varlock now correctly resolves .env.schema and .env files from each child package's directory instead of only looking in the monorepo root.

  • Updated dependencies [2022ef7, 74752a3, 0ea6641, 6ab2d31, 01c9a6a, 1a4b0cf, 02e82d0, 0c27ed1]:

    • varlock@0.7.2

0.2.9

Patch Changes

  • #527 e67ee2f - Improve invalid config handling in CLI and Vite integration

    • varlock load --format json-full now outputs partial JSON (with errors field) even when validation fails, enabling consumers to access sources and valid config items
    • Vite plugin gracefully handles invalid config in dev mode: shows error page and automatically recovers when the config is fixed
    • Vite build output now includes specific error details when config validation fails

  • Updated dependencies [0d25aa5, 004e181, e67ee2f]:

    • varlock@0.7.1

0.2.8

Patch Changes

  • #480 39d88a9 - New @varlock/cloudflare-integration package for Cloudflare Workers

    • varlockCloudflareVitePlugin() — Vite plugin that reads secrets from Cloudflare bindings at runtime instead of bundling them into worker code
    • varlock-wrangler CLI — drop-in wrangler replacement that uploads non-sensitive values as vars and sensitive values as secrets on deploy; injects env into miniflare via Unix named pipe in dev; watches .env files for changes; generates correct Env types
    • @varlock/cloudflare-integration/init — standalone init module for non-Vite workers Refactors @varlock/vite-integration to remove Cloudflare-specific logic and add generic extension points (ssrEntryCode, ssrEdgeRuntime, ssrEntryModuleIds) for platform integrations.

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8, 7f32751]:

    • varlock@0.7.0

0.2.7

Patch Changes

  • #459 763b4fc - detect cloudflare/worker-entry as additional entry point

  • #453 bb1c075 - Add support for configuring the default env file load path via package.json.

    You can now set a varlock.loadPath key in your package.json to configure the default path used when loading .env files:

    {
  "varlock": {
    "loadPath": "./envs/"
  }
}

    This is useful when you store your .env files in a custom directory (e.g., when using Vite's envDir option). The CLI --path flag continues to override this setting when provided.

    The Vite integration will also now show a warning if envDir is set in your Vite config, with instructions to use varlock.loadPath in package.json instead.

  • Updated dependencies [bb1c075]:

    • varlock@0.6.3

0.2.6

Patch Changes

0.2.5

Patch Changes

  • #402 f1873ec - Fix ENV.* static replacement being skipped for Vite dev module IDs with query suffixes (e.g. ?tsr-split=component from TanStack Router split routes). The file extension is now extracted from the path portion of the ID only, ignoring any query string or hash fragment.

  • Updated dependencies [4d436ff, ca51993]:

    • varlock@0.5.0

0.2.4

Patch Changes

0.2.3

Patch Changes

  • Updated dependencies [e30ec1f]:
    • varlock@0.4.0

0.2.2

Patch Changes

0.2.1

Patch Changes

0.2.0

Patch Changes

0.1.1

Patch Changes

  • #221 8d2d284 - fix for local dev with cloudflare+vite

1.0.0

Patch Changes

0.0.11

Patch Changes

  • #163 8d31513 - fix issue with executable path when running directly instead of via package manager

  • Updated dependencies [b6fc6dd, 8d31513]:

    • varlock@0.0.15

0.0.10

Patch Changes

0.0.9

Patch Changes

  • Updated dependencies [9d9c8de]:
    • varlock@0.0.13

0.0.8

Patch Changes

0.0.7

Patch Changes

  • #132 330bd92 - fix logic around setting process.env and handling empty/undefined vals

  • Updated dependencies [330bd92]:

    • varlock@0.0.11

0.0.6

Patch Changes

  • Updated dependencies [17206e8]:
    • varlock@0.0.10

0.0.5

Patch Changes

  • #116 9e8b40a - - make Vite plugin work for SSR scenarios, injecting code and resolved env (in some cases)
    • detect Cloudflare Vite plugin
    • make compatible with React Router 7
    • simplify astro integration to rely on vite integration more
  • Updated dependencies [9e8b40a, 86c02bf]:
    • varlock@0.0.9

0.0.4

Patch Changes

0.0.3

Patch Changes

0.0.2

Patch Changes

  • #91 186d6ed - fix vite reloading logic

  • #91 186d6ed - use ast-based replacement method instead of naive string replacement

  • Updated dependencies [186d6ed]:

    • varlock@0.0.6

0.0.1

Patch Changes