Load your `.env` file and replace `process.env.MY_VARIABLE` with the value you set.
npm install babel-plugin-inline-dotenv!Test
Load your .env file and replace process.env.MY_VARIABLE with the value you set.
tl;dr
It actually replaces process.env.MY_VARIABLE with:
process && process.env && process.env.MY_VARIABLE || 'value assigned to variable in dotenv'
This way, if the value is available at runtime it will be used instead.
``sh`
$ npm install babel-plugin-inline-dotenv
Without options:
.babelrc
`js`
{
"plugins": ["inline-dotenv"]
}
With options:
`js`
{
"plugins": [["inline-dotenv",{
path: 'path/to/.env' // See motdotla/dotenv for more options
}]]
}
To replace with env value without process && process.env && process.env.MY_VARIABLE || safety:
`js`
{
"plugins": [["inline-dotenv",{
unsafe: true
}]]
}
The plugin support 3 mode to read the env var from the system :
`js`
{
"plugins": [["inline-dotenv",{
systemVar: 'all' | 'overwrite' | 'disable'
}]]
}
- all _default_, every env var found in process.env will be used
> ⚠️ This could leak super secret stuffs !
- overwrite, the value in process.env will overwrite the one present in .env only. Your .env file act as a whitelist
- disable, the process.env will not be used at all
`sh`
$ babel --plugins inline-dotenv script.js
`javascript``
require("babel-core").transform("code", {
plugins: ["inline-dotenv"]
});