babel-plugin-inline-dotenv
babel-plugin-inline-dotenv copied to clipboard
Load your .env file and replace 'process.env.MY_VARIABLE' with the value you set.
## Updating Dependencies | Name | Updating | devDependencies | | :---- | :--------: | :-: | | [mocha](https://mochajs.org/) | 9.2.0...9.2.2 | * | Powered by [actions-package-update](https://github.com/taichi/actions-package-update)
there're two env files. .env > AAA=aaa > BBB=bbb > .env.prod > AAA=prod and I want get > AAA=prod > BBB=bbb I tried to config in babe.config.js, but no luck...
Once installed the plugin works as expected (loading my `.env` vars in `process.env` being used in webpack and all), but after a node reload or any changes, it suddenly stops...
## Updating Dependencies | Name | Updating | | :---- | :--------: | Powered by [actions-package-update](https://github.com/taichi/actions-package-update)
Hi. I've integrated this plugin on my Expo (React Native) project [following these steps](https://github.com/luggit/react-native-config/issues/249#issuecomment-386090809). Can you please tell me if it is possible to configure the plugin to use the...
## The devDependency [mocha](https://github.com/mochajs/mocha) was updated from `6.0.2` to `6.1.0`. 🚨 [View failing branch](https://github.com/brysgo/babel-plugin-inline-dotenv/compare/master...brysgo:greenkeeper%2Fmocha-6.1.0). This version is **covered** by your **current version range** and after updating it in your project...
This seems to be a common issue with babel plugins, we're doing relative reads (or dotenv ends up doing relative read), so a path with something like '../../.env' (lerna setup,...
The plugin doesn't recognize code like below ... ``` const {PORT, NODE_ENV} = process.env; ```
How can I pass a specific path to the CLI command? For instance like this: `$ babel --plugins [ inline-dotenv --path .env-prod ] script.js`
Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3. Release notes Sourced from json5's releases. v2.2.3 Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299) v2.2.2 Fix: Properties...