Create custom solution for env #722
Assignees
Labels
enhancement
New feature or request
Comments
|
need this fix! |
3 tasks
3 tasks
|
hej @PatrykKuniczak please tell me what's going on with your idea? Is this topic dead already? Or are you going to push it forward? |
|
@SebastianTroc I have no time now, i hope for the end of this year, but maybe more, also @Jonghakseo are busy and we won't work on entire project till maybe February. I hope @Jonghakseo want to work on this project more next year :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Now it doesn't work well, e.g. there's some problems with
import.meta.envfor some pages.Describe the solution you'd like
I want to create new package where, i can get data from
.envfile and also collect necessary data fromprocess.envand create it accessible in all packages.This can simplify
envusage for entire project and unify it, users don't need to useprocessandimport.meta.envseparetly, but then will have it unified.And it will works for all packages without any other problems.
I also want to implement script which will copy .example.env and paste it as .env on
postinstall, for better first use, because it will work only when.envdoesn't exitsts yet.Ps: I've found it:
https://nodejs.org/dist/latest-v20.x/docs/api/cli.html#--env-fileconfig
From version 20, Node support
.envnative, i can do this that way :)The text was updated successfully, but these errors were encountered: