[Feature Request] Preset support

[mmikhan]

Description

I am a long time user of T3 Env. It's not perfect but it's what I have got until I found Varlock. Varlock is what I have wanted an env management would be. It's also not 100% perfect but the best one I could find so far. So, thanks for making this.

Motivation

One of the feature of T3 Env is Preset. A preset is a collection of env vars. For example, there's a preset for Vercel and another one is for Vite. Vite offers a few built-in constants that every project has access to.

So, instead of recreating the same vars everyone using Varlock on their projects, we could simply use the Vite preset as the built-in constants are there for us to use.

Proposed Solution

Varlock offers @import() root decorator out of the box. We could use the @import(Vite) to import the Vite preset and use the ENV.mode in a normal way.

Alternatively, there could be a new root decorator called @preset() and we pass the preset name to it as arg, @preset(Vite).

Or a better way that I can't think of 😉

Alternatives

No response

Additional Information

No response

[theoephraim]

Yes this is something we’ve thought about for a while. Check out this discussion - #151

Importing from installed npm packages will also help, but remote imports would be even more lightweight.

[theoephraim]

Ok the plan is to create a new public-schemas folder within the monorepo. Then allow these remote imports using a special protocol - for example # @import(public-schemas:platforms/vercel) which will fetch (likely from github) and cache.

[mmikhan]

That works as well. Thanks for looking into this so fast 🚀