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 🙏

© 2026 – Pkg Stats / Ryan Hefner

vite-import-env

v0.0.7

Published

A Vite plugin that enables cross-environment imports using import attributes syntax. This plugin allows you to import modules from different Vite environments (client, server, worker, etc.) within the same codebase using the `with { env: "..." }` syntax.

Readme

vite-import-env

A Vite plugin that enables cross-environment imports using import attributes syntax. This plugin allows you to import modules from different Vite environments (client, server, worker, etc.) within the same codebase using the with { env: "..." } syntax.

Installation

npm install vite-import-env
# or
pnpm add vite-import-env
# or
yarn add vite-import-env

Setup

Add the plugin to your Vite configuration:

import { defineConfig } from "vite";
import { importEnv } from "vite-import-env";

export default defineConfig({
  builder: {
    async buildApp(builder) {
      await builder.build(builder.environments.client);
      await builder.build(builder.environments.server);
    },
    sharedConfigBuild: true,
    sharedPlugins: true,
  },
  environments: {
    client: {
      // Client environment configuration
    },
    server: {
      // Server environment configuration
      build: {
        rollupOptions: {
          // Required for environments that are imported in other environments
          preserveEntrySignatures: "exports-only",
        },
      },
      resolve: {
        conditions: ["react-server"],
      },
    },
    // Add more environments as needed
  },
  plugins: [importEnv()],
});

Usage

Basic Cross-Environment Imports

Use the with { env: "..." } syntax to import modules from different environments:

// Import server-side code from client environment
import { server } from "./entry.server" with { env: "server" };

// Import client-side code from server environment
import { clientOnlyValue } from "./client-only" with { env: "client" };

Example: Client Entry Point

// entry.client.ts
import "client-only";

import { clientOnlyValue } from "./client-only";
import { sharedValue } from "./shared";

// Import server-side function from server environment
import { server } from "./entry.server" with { env: "server" };

export const client = () => ({
  clientOnlyValue,
  server,
  sharedValue,
  value: "client-value",
});

Example: Server Entry Point

// entry.server.ts
import "server-only";

// Import client-side value from client environment
import { clientOnlyValue } from "./client-only" with { env: "client" };
import { serverOnlyValue } from "./server-only";
import { sharedValue } from "./shared";

export const server = {
  clientOnlyValue,
  serverOnlyValue,
  sharedValue,
  value: "server-value",
};

Worker Example

The plugin also works with Web Workers:

// entry.worker.ts
import "client-only";

import { clientOnlyValue } from "./client-only";
import { sharedValue } from "./shared";

// Import server code from worker environment
import { server } from "./entry.server" with { env: "server" };

const client = () => ({
  clientOnlyValue,
  server,
  sharedValue,
  value: "client-value",
});

postMessage(client());

How It Works

The plugin transforms import statements with environment attributes in two phases:

  1. Transform Phase: Converts with { env: "..." } syntax to query parameters

    // Before
    import { server } from "./entry.server" with { env: "server" };
    
    // After
    import { server } from "./entry.server?env=server";
  2. Resolution Phase: Uses the appropriate environment's resolver to handle the import based on the env query parameter

Environment Propagation

When a module is imported with an environment attribute, all of its internal imports automatically inherit that environment context. This ensures that the entire dependency tree is resolved within the correct environment.

License

ISC