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

   🚀 Features

• Support for custom config file path  -  by @Julien-R44 (6720e)

    View changes on GitHub

v1.0.1

   🐞 Bug Fixes

• Show zod default values  -  by @SimeonC (4a1e9)

    View changes on GitHub

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 debug property 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

• @SimeonC made their first contribution in #14

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)

    View changes on GitHub

v0.2.3

• Fixed issue with optional schemas #9

    View changes on GitHub

v0.2.2

No significant changes

    View changes on GitHub

v0.2.1

   🚀 Features

• Support envDir option  -  by @Julien-R44 (b49bf)

    View changes on GitHub

v0.2.0

Now we are displaying all validations error at once :

Thanks to @reslear for suggesting this idea in #5

Changelog

   🚀 Features

• Display all validation errors at once  -  by @Julien-R44 (d1bd8)

    View changes on GitHub

Support custom prefix

What's Changed

• fix: custom env prefixes by @Julien-R44 in #3

Full Changelog: v0.1.2...v0.1.3