import.meta.env respects morphed envs

[yamcodes]

• Updated unit tests to mock environment variable creation and validate transformed values.
• Added tests for handling various data types, including null, undefined, and special characters.
• Improved the plugin's configuration hook to expose transformed environment variables through Vite's define option.

These changes enhance the robustness of the Vite plugin and ensure accurate handling of environment variables.

Closes #226

Summary by CodeRabbit

• Bug Fixes

  • import.meta.env now correctly exposes transformed environment variables at build time, preserving schema defaults and type transformations.
  • Ensures consistent handling of strings, numbers, booleans, null, undefined, empty values, and exact key names.

• Tests

  • Added comprehensive unit tests covering environment transformation, define mapping, empty environments, key preservation, and error propagation.

• Chores

  • Updated changelog for a patch release.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1635a99

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@arkenv/vite-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
arkenv	Ready	Preview	Comment	Oct 13, 2025 3:06pm

[coderabbitai]

Walkthrough

The Vite plugin’s config hook now collects transformed env values from createEnv and returns a Vite define mapping to expose them under import.meta.env.KEY. Added unit tests verify define serialization, key preservation, empty/env edge cases, and error propagation. A changeset entry documents the patch release.

Changes

Cohort / File(s)	Summary
Changelog entry \.changeset/tidy-worlds-fetch.md	Adds a patch changelog describing that morphed env values are now exposed via Vite’s define option.
Vite plugin implementation packages/vite-plugin/src/index.ts	Updates config hook to call createEnv(...), build a define object mapping import.meta.env.KEY to JSON-stringified values, and return { define }.
Vite plugin tests packages/vite-plugin/src/index.test.ts	Adds tests covering invocation of createEnv, define mapping of various types, key preservation, empty env behavior, and error propagation through the config hook.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as vite.config.ts
  participant Vite as Vite Build
  participant Plugin as @arkenv/vite-plugin
  participant Ark as createEnv()

  Dev->>Vite: start build / dev
  Vite->>Plugin: config(config, env)
  Plugin->>Ark: createEnv(mode, schema, loaders)
  Ark-->>Plugin: transformedEnv
  Plugin->>Vite: return { define: { "import.meta.env.KEY": JSON.stringify(value), ... } }
  Note right of Vite: Vite inlines define mappings
  Vite-->>Dev: import.meta.env.KEY available with morphed values

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• refactor: use vi.stubEnv instead of process.env #205 — Refactors vite-plugin tests to use vi.stubEnv/unstubEnvs; overlaps with current plugin test surface.
• Integration tests #108 — Modifies @arkenv/vite-plugin tests and setup; related to expanded test coverage here.

Suggested labels

@arkenv/vite-plugin, tests

Poem

A rabbit tweaks the Vitey breeze,
Morphs and maps with hopping ease.
Env keys shine, their types aligned,
In define’s warren, neatly signed.
Now burrows build without a fret—
import.meta knows what it should get. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly summarizes the main change by indicating that import.meta.env now respects morphed environment variables, which aligns precisely with the core objective of integrating createEnv transformations into Vite’s environment interface.
Linked Issues Check	✅ Passed	The updated plugin config hook now returns a define object populated with JSON-stringified transformed values from createEnv, and the new unit tests validate type conversions, default values, custom logic, key preservation, empty environment handling, and error propagation, satisfying all coding objectives outlined in issue #226.
Out of Scope Changes Check	✅ Passed	All modifications, including the added changelog entry, plugin code updates, and new unit tests, directly support the goal of exposing morphed environment variables through import.meta.env and do not introduce any unrelated or out-of-scope changes.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 226-importmetaenv-does-not-respect-morphed-environment-variables

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/arkenv@227

npm i https://pkg.pr.new/@arkenv/vite-plugin@227

commit: 1635a99

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/vite-plugin/src/index.ts (1)

20-22: Filter out undefined values in Vite define entries
Vite’s define option passes values to esbuild and requires valid expressions or JSON-serializable values; JSON.stringify(undefined) yields undefined (not a string), producing invalid replacements. Exclude undefined entries:

const define = Object.fromEntries(
-  Object.entries(<Record<string, unknown>>env).map(([key, value]) => [
-    `import.meta.env.${key}`,
-    JSON.stringify(value),
-  ]),
+  Object.entries(<Record<string, unknown>>env)
+    .filter(([, value]) => value !== undefined)
+    .map(([key, value]) => [
+      `import.meta.env.${key}`,
+      JSON.stringify(value),
+    ]),
);

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 469729a and 1635a99.

📒 Files selected for processing (3)

• .changeset/tidy-worlds-fetch.md (1 hunks)
• packages/vite-plugin/src/index.test.ts (3 hunks)
• packages/vite-plugin/src/index.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.test.ts

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.test.ts: Place tests alongside source files and use the .test.ts suffix (e.g., create-env.test.ts, types.test.ts, errors.test.ts, utils.test.ts)
Use Vitest's describe/it structure in tests
Test both success and failure cases for environment validation and utilities
Mock process.env to cover different environment scenarios in tests
In tests, save and restore process.env in setup/teardown (beforeEach/afterEach) to avoid leakage between cases
Verify both runtime behavior and TypeScript types in tests

Files:

• packages/vite-plugin/src/index.test.ts

🧠 Learnings (2)

📚 Learning: 2025-09-12T06:23:45.463Z

Learnt from: CR
PR: yamcodes/arkenv#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-09-12T06:23:45.463Z
Learning: Applies to **/*.test.ts : Mock process.env to cover different environment scenarios in tests

Applied to files:

• packages/vite-plugin/src/index.test.ts

📚 Learning: 2025-09-12T06:23:45.463Z

Learnt from: CR
PR: yamcodes/arkenv#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-09-12T06:23:45.463Z
Learning: Applies to **/*.test.ts : Test both success and failure cases for environment validation and utilities

Applied to files:

• packages/vite-plugin/src/index.test.ts

🧬 Code graph analysis (2)

packages/vite-plugin/src/index.ts (2)

packages/arkenv/src/create-env.ts (1)

• createEnv (21-34)

packages/arkenv/src/index.ts (1)

• createEnv (13-13)

packages/vite-plugin/src/index.test.ts (1)

packages/vite-plugin/src/index.ts (1)

• config (15-27)

🔇 Additional comments (9)

packages/vite-plugin/src/index.ts (1)

16-26: LGTM! The implementation correctly exposes morphed environment variables.

The config hook now properly integrates createEnv results with Vite's define option, ensuring schema transformations are respected in import.meta.env.

packages/vite-plugin/src/index.test.ts (7)

42-43: LGTM! Proper mock setup for fixture test.

The mock correctly returns the environment variables from the fixture configuration.

---

102-133: LGTM! Thorough test of createEnv invocation during config hook.

The test properly verifies that createEnv is called with the expected schema and environment object, using a complete mock context.

---

135-182: LGTM! Comprehensive test of define object generation.

The test thoroughly verifies that transformed values are correctly serialized and exposed through the define object with proper import.meta.env keys.

---

184-230: LGTM! Excellent coverage of edge cases.

The test thoroughly covers various data types including edge cases like null, undefined, empty string, zero, and false. The explicit expectation at line 225 that JSON.stringify(undefined) returns undefined documents the current behavior.

Note: This test confirms the undefined behavior I flagged in the implementation. Consider adding a comment or integration test to verify that Vite handles undefined values in the define object correctly.

---

232-259: LGTM! Good edge case coverage.

The test correctly verifies that an empty environment object produces an empty define object.

---

261-304: LGTM! Thorough test of key name preservation.

The test ensures that various key formats (uppercase, lowercase, numeric prefixes, special characters) are preserved exactly in the define output.

---

306-338: LGTM! Proper error propagation test.

The test correctly verifies that errors thrown by createEnv are propagated through the config hook, ensuring failures are not silently swallowed.

Based on learnings: The test follows the coding guideline to "Test both success and failure cases for environment validation and utilities."

.changeset/tidy-worlds-fetch.md (1)

1-11: LGTM! Clear and accurate changelog entry.

The changeset properly documents the fix, explaining both the previous problematic behavior and the new solution using Vite's define option to expose morphed environment variables.