Skip to content

Releases: Julien-R44/vite-plugin-validate-env

v2.2.0

03 Jul 18:28

Choose a tag to compare

Changes

  • Add support for Vite 7
    View changes on GitHub

v2.1.0

25 May 22:39

Choose a tag to compare

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v2.0.0

19 May 23:36

Choose a tag to compare

   🚨 Breaking Changes

    View changes on GitHub

v1.3.0

21 Jan 13:01

Choose a tag to compare

   🚀 Features

    View changes on GitHub

v1.2.0

29 Nov 10:38

Choose a tag to compare

   🐞 Bug Fixes

    View changes on GitHub

v1.1.1

11 Feb 08:49

Choose a tag to compare

Fixes

  • Import dynamically Vite to avoid using the soon to be obsolete CJS version of Vite ( 2b373a4 )
    View changes on GitHub

v1.1.0

11 Feb 08:28

Choose a tag to compare

   🚀 Features

    View changes on GitHub

v1.0.1

28 Nov 18:35

Choose a tag to compare

   🐞 Bug Fixes

    View changes on GitHub

1.0.0

25 Nov 14:42

Choose a tag to compare

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

Full Changelog: v0.2.5...v1.0.0

v0.2.4

28 Jun 08:20

Choose a tag to compare

   🐞 Bug Fixes

    View changes on GitHub