https://github.com/Enalmada/env-valibot

validate env variables with valibot
https://github.com/Enalmada/env-valibot

Last synced: 3 months ago
JSON representation

validate env variables with valibot

• Host: GitHub
• URL: https://github.com/Enalmada/env-valibot
• Owner: Enalmada
• License: mit
• Created: 2023-09-22T16:17:31.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-04-18T18:40:37.000Z (7 months ago)
• Last Synced: 2024-04-20T13:03:10.416Z (7 months ago)
• Language: TypeScript
• Homepage: https://env-valibot.vercel.app
• Size: 995 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 11
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# Env validation with valibot

Deploying your app with invalid environment variables is a hassle. This package helps you to avoid that.

Inspired by [t3-env](https://github.com/t3-oss/t3-env) which I highly recommend using if zod is already a production dependency.

Otherwise, valibot may more efficient for just environment variable checking.

## Getting Started

Read the [documentation](https://env-valibot.vercel.app)

## Build Notes

* Using [latest module and target settings](https://stackoverflow.com/questions/72380007/what-typescript-configuration-produces-output-closest-to-node-js-18-capabilities/72380008#72380008) for current LTS

* using tsc for types until [bun support](https://github.com/oven-sh/bun/issues/5141#issuecomment-1727578701) comes around

## Contribute

Using [changesets](https://github.com/changesets/changesets) so please remember to run "changeset" with any PR.  

Give consideration for the summary as it is what will show up in the changelog.