Blog
We had a great time live streaming with Nick Taylor adding varlock to his Astro project. You can watch the full stream here.
August was a month of stability improvements, bug fixes, and new integrations. We’ve been listening to your feedback and working hard to make varlock more reliable and easier to use.
New Features and Content
- Updated framework integrations: Building on the foundation of our Vite integration, we’ve added support for Qwik, React Router, and Cloudflare Workers
- Docker Image: We’ve created a Docker image for varlock, making it easier to use in containerized environments.
- GitHub Action: Use varlock in your GitHub Actions workflows. Automatically emits resolved env vars so they can be reused and optionally shows a summary of the resolved env vars.
- @required: We’ve added a new
forEnv()helper to the@requiredand@optionaldecorators to allow you to make items conditionally required based on the value of yourenvFlag. - MCP guide: We’ve added a new guide to help you secure your MCP servers.
Thanks to reneleonhardt for suggesting both Docker and GitHub Action features.
Core Bug Fixes & Enhancements
- Env Handling: Improved logic around setting
process.envand handling empty or undefined values. - Astro & Vite: Fixed an issue with the Astro+Vite plugin.
- Cloudflare: Addressed a bug with global
Responsepatching for Cloudflare environments. - Error Handling: Fixed an error that occurred when Git is not installed.
- Vite SSR: The Vite plugin now works better in SSR scenarios, with improved code injection and resolved env handling.
- .envrc: Varlock now ignores
.envrcfiles to avoid conflicts with tools likedirenv. - envFlag normalization: We’ve removed the normalization that previously meant
dev,stage, andprodvalues inenvFlagwould be normalized todevelopment,staging, andproduction.
What’s Next
- First-party plugin for 1Password
- GitHub App including things like PR schema validation and reporting
@importdecorator for importing env vars from other files