Releases: Julien-R44/vite-plugin-validate-env
Releases · Julien-R44/vite-plugin-validate-env
v2.2.0
v2.1.0
🚀 Features
- Expose function for validation without running Vite - by @aweebit and @Julien-R44 in #36 (47026)
🐞 Bug Fixes
- Include
@standard-schema/specas a dependency - by @matt-tingen in #38 (15d43)
View changes on GitHub
v2.0.0
🚨 Breaking Changes
- Remove zod adapter - by @Julien-R44 (5cd45)
- Remove CJS build - by @Julien-R44 (31e3a)
- Minimum node version >= 22 - by @Julien-R44 (a6e63)
View changes on GitHub
v1.3.0
🚀 Features
- Implement standard schema - by @Julien-R44 (78418)
- Infer type produced by standard schema - by @Julien-R44 (1535b)
View changes on GitHub
v1.2.0
🐞 Bug Fixes
- Add vite 6+ to supported list of vite versions - by @theZieger (21203)
View changes on GitHub
v1.1.1
Fixes
- Import dynamically Vite to avoid using the soon to be obsolete CJS version of Vite ( 2b373a4 )
View changes on GitHub
v1.1.0
v1.0.1
1.0.0
Breaking Changes
Before, the plugin didn't really work at 100%, or at least, it wasn't totally type safe. Only strings were stored in import.meta.env. Even when using z.number() or Schema.number(). Same for all other types other than string. It's all fixed now, everything works as expected. We've changed our strategy and now use define from vite rather than process.env.
This is the main reason for this major version change.
Features
- Added a
debugproperty in the plugin configuration that allows process.env to be logged before the vite-plugin-validate-env processing
Fixes
- Previously, when .env file was modified and the vite dev server was running, the changes were not taken into account. This is now fixed
New Contributors
Full Changelog: v0.2.5...v1.0.0
v0.2.4
🐞 Bug Fixes
- Don't stop validation when value is undefined - by @Julien-R44 (8ddf0)