Don't default export `from(process.env)` for environments that don't have `process` about env-var HOT 6 CLOSED

This is available in the beta release of version 8. You can install and test it using npm install env-var@beta. Feel free to reopen this issue if necessary.

EDIT: See my latest comment in this thread for a fix with v7.x

from env-var.

@kenberkeley I have released v7.4.0 with this fix. You can now do the following for Vite environments:

const env = from(import.meta.env);

Or in React with create-react-app, you need to explicitly reference each variable like:

const env = from({
  SOME_VARIABLE: process.env.REACT_APP_SOME_VARIABLE
});

from env-var.

Thanks for raising this issue @smblee. I think it's a good point, and the module probably shouldn't assume that it's operating in a Node.js environment.

One problem is that I think this will break backwards compatibility, unless the code is changed to use some sort of conditional check.

If you change the line causing the issue to this, does it fix the issue?

module.exports = from(typeof process === 'undefined' ? {} : process.env) 

from env-var.

@smblee any luck with that fix? If so I can merge it into this module and push a patch release.

from env-var.

hi @evanshortiss , thanks for your work on this! Wanted to let you know that the beta worked just fine in my Vite React app -- head's up to anyone reading this, I had to place import.meta.env in an object like so:

const env = from({ variables: import.meta.env });

from env-var.

@evanshortiss May I ask when you will release the beta version?

from env-var.