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

@svitejs/vite-plugin-env-import

v1.0.0-next.1

Published

Import env vars

Downloads

1

Readme

@svitejs/vite-plugin-env-import

Import env vars

Installation

pnpm i -D @svitejs/vite-plugin-env-import

Usage

add plugin to vite config

// vite config
import { defineConfig } from 'vite';
import { envImport } from '@svitejs/vite-plugin-env-import';

export default defineConfig({
	plugins: [envImport()]
});

import from virtual modules

virtual:env

Contains all env variables that do not start with a public prefix with their value as static strings.

import { SUPER_SECRET } from 'virtual:env';

imports from 'virtual:env' only work in ssr code, if you do this in client code, an error is thrown

virtual:env:runtime

Same as virtual:env but instead of static value replacement at buildtime, it uses process.env.XXX so the actual runtime value at time of ssr is used

virtual:env:public

Contains all env variables that start with a public prefix with their value as static strings.

import { VITE_TITLE } from 'virtual:env:public';

imports from 'virtual:env:public' work in client and ssr code

virtual:env:public:runtime

Same as virtual:env:public but instead of static value replacement at buildtime, it uses process.env.XXX so the actual runtime value at time of ssr is used

imports from 'virtual:env:public:runtime' only work in ssr code, if you do thing in client code, an error is thrown

This is due to the fact that clientside code cannot access the ssr runtime env

License

MIT