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

Extract builtin validator

Only refactoring here. The builtin validator was extracted into @poppinss/validator-lite

Full Changelog: v0.1.0...v0.1.2

Fix typing error

🩹 Fixes

• Remove hardcoded vite prefix (607b973)

🏡 Chore

• Release v0.1.1 (dffa75c)

Zod Validation

Zod Validation

You can now use Zod as a validation library, in cases where you need a stricter validation or if you just prefer it.

// env.ts
export default defineConfig({
  validator: 'zod',
  schema: {
    VITE_MY_STRING: z.string().min(5, 'This is too short !').startWith('h').endsWith('/'),
    VITE_ENUM: z.enum(['a', 'b', 'c']),
	VITE_AUTH_API_URL: z
      .string()
      .transform((value) => value.endsWith('/') ? value : `${value}/`),
  }
})

Less verbose import.meta.env typing

Just made a little helper for getting the correct IntelliSense on import.meta.env. Can be used as follows:

type ImportMetaEnvAugmented = import('@julr/vite-plugin-validate-env').ImportMetaEnvAugmented<typeof import('../env').default>

interface ImportMetaEnv extends ImportMetaEnvAugmented {}

Initial release

See more details in the README