@winglibs/vite use native environment variables vs global wing object

Use Case

I'm building an application and trying to share the API URL.

bring cloud;
bring vite;


let freinds: Array<Json> = [
  {name: "John", email: "test@test.com"},
  {name: "John", email: "random@test.com"},
];

let api = new cloud.Api();

api.get("/friends", inflight () => {
  return cloud.ApiResponse {
    body: Json.stringify(freinds)
  };
});

// Create the website

let website = new vite.Vite(
  root: "../ui",
  publicEnv: {
    API_URL: api.url,
  },
);

In the vite code I have to access this using window.wing.env but vite has it's own eco system and ways to share public ENV variables, it would be nice to support this. So Front end developers don't have to care about a wing global object, they continue to write applications as they were.

Proposed Solution

Let me just use Vite import syntax to get what I want https://vitejs.dev/guide/env-and-mode

For example import.meta.env gives me all the environment variables, I would expected to see it on there import.meta.env.API_URL in this example.

Implementation Notes

No response

Component

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Discord.

Start with the winglibs/vite Vite component and compare its current publicEnv/window.wing.env behavior with the linked Vite env-and-mode documentation. Determine how API_URL should appear through import.meta.env, then verify that a Vite frontend can consume it without relying on the Wing global object.