npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@techmely/valibot-env

v1.1.2

Published

Access your environment with easy and secure way

Downloads

8

Readme

nuxt-modules

Env Valibot

Framework agnostic validation for type-safe environment variables

Never build your apps with invalid environment variables again. Validate and transform your environment with the full power of Valibot.

Install dependencies

npm install @techmely/env-valibot valibot

Create your schema

File example src/env.ts We need separate two function for client and server side - Because the security issues(when you define schema client here --> Will expose to client, hacker can reverse engine those code and do something with that)


import { string, url } from 'valibot';
import { accessEnvs } from "@techmely/env-valibot";
 
export const serverEnvs = accessEnvs({
  /*
   * Specify what prefix the client-side variables must have.
   * This is enforced both on type-level and at runtime.
   */
  clientPrefix: "PUBLIC_",
  server: {
    DATABASE_URL: z.string().url(),
    OPEN_AI_API_KEY: z.string().min(1),
  },
  /**
   * What object holds the environment variables at runtime.
   * Often `process.env` or `import.meta.env`
   */
  runtimeEnv: process.env,
});

export const clientEnvs = accessEnvs({
  /*
   * Specify what prefix the client-side variables must have.
   * This is enforced both on type-level and at runtime.
   */
  clientPrefix: "PUBLIC_",
  client: {
    PUBLIC_DOMAIN_URL: string([url()]),
    PUBLIC_SENTRY_DNS: string([url()]),
  },
  /**
   * What object holds the environment variables at runtime.
   * Often `process.env` or `import.meta.env`
   */
  runtimeEnv: process.env,
});

Nextjs, NuxtJs

Do the same things like above


import { string, url } from 'valibot';
import { accessEnvs } from "@techmely/env-valibot";
 
export const serverEnvs = accessEnvs({
  /*
   * Specify what prefix the client-side variables must have.
   * This is enforced both on type-level and at runtime.
   */
  clientPrefix: "PUBLIC_",
  server: {
    DATABASE_URL: z.string().url(),
    OPEN_AI_API_KEY: z.string().min(1),
  },
  /**
   * What object holds the environment variables at runtime.
   * Often `process.env` or `import.meta.env`
   */
  runtimeEnv: process.env,
});

export const clientEnvs = accessEnvs({
  /*
   * Specify what prefix the client-side variables must have.
   * This is enforced both on type-level and at runtime.
   */
  clientPrefix: "PUBLIC_",
  client: {
    PUBLIC_DOMAIN_URL: string([url()]),
    PUBLIC_SENTRY_DNS: string([url()]),
  },
  /**
   * What object holds the environment variables at runtime.
   * Often `process.env` or `import.meta.env`
   */
  runtimeEnv: process.env,
});

With Nextjs

In next.config.mjs


import "./src/env.mjs";
 
/** @type {import("next").NextConfig} */
const config = {
  /** ... */
};
 
export default config;

With Nuxtjs

In nuxt.config.ts


import "./src/env.ts";
 
export default defineNuxtConfig();

With AstroJs

In astro.config.mjs


import "./src/env.mjs";

import { defineConfig } from 'astro/config'

export default defineConfig();

With ViteJs App

In vite.config.(ts/js/mjs)


import "./src/env.(ts/js/mjs)";

import { defineConfig } from 'vite'

export default defineConfig();

With Qwik City

Do like ViteJs app do!