feat: add env:*

[lxsmnsyc]

This PR adds the env:server and env:client modules

// Loads SERVER_* from .env
// Throws and omits all detected variables on client runtime
import { SERVER_EXAMPLE } from 'env:server';

console.log(SERVER_EXAMPLE);

// Loads CLIENT_* from .env
import { CLIENT_EXAMPLE } from 'env:client';

console.log(CLIENT_EXAMPLE);

// Dynamically loads environment variables (only on server)
import env from 'env:server/runtime';

console.log(env.NODE_ENV);

closes #2113

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7415042

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

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

[netlify]

✅ Deploy Preview for solid-start-landing-page ready!

Name	Link
🔨 Latest commit	7415042
🔍 Latest deploy log	https://app.netlify.com/projects/solid-start-landing-page/deploys/69b8f3497a76380008255d22
😎 Deploy Preview	https://deploy-preview-2110--solid-start-landing-page.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/solidjs/solid-start/@solidjs/start@2110

npm i https://pkg.pr.new/solidjs/solid-start/@solidjs/vite-plugin-nitro-2@2110

commit: 7415042

[yinonburgansky]

Can we error on build-time, instead of run-time?
Maybe if it is done after the server-function & tree-shake

[lxsmnsyc]

@yinonburgansky This actually yields error on build, but not dev.

fun fact: despite the "throw" side-effect, the missing module exports error yields first on runtime.