Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@nuxtjs/dotenv
Advanced tools
A nuxt.js module that loads your .env file into your context options
The module loads variables from your .env file directly into your nuxt.js application context
and process.env
.
@nuxtjs/dotenv
dependency to your projectyarn add @nuxtjs/dotenv # or npm install @nuxtjs/dotenv
@nuxtjs/dotenv
to the modules
section of nuxt.config.js
{
modules: [
// Simple usage
'@nuxtjs/dotenv',
// With options
['@nuxtjs/dotenv', { /* module options */ }]
]
}
{
modules: [
'@nuxtjs/dotenv'
],
dotenv: {
/* module options */
}
}
only
null
If you want to restrict what's accessible into the context, you can can pass to the module options an only
array with the keys you want to allow.
{
modules: [
['@nuxtjs/dotenv', { only: ['some_key'] }]
]
}
path
srcDir
By default, the we'll be loading the .env
file from the root of your project. If you want to change the path of the folder where we can find the .env
file, then use the path
option.
{
modules: [
['@nuxtjs/dotenv', { path: '/path/to/my/global/env/' }]
]
}
Note: that this is the path to the folder where the
.env
file live, not to the.env
file itself.
The path can be absolute or relative.
false
By default this is false and variables from your system will be ignored. Setting this to true will allow your system set variables to work.
{
modules: [
['@nuxtjs/dotenv', { systemvars: true }]
]
}
.env
We can override the filename when we need to use different config files for different environments.
{
modules: [
['@nuxtjs/dotenv', { filename: '.env.prod' }]
]
}
After creating your .env file in the project root, simply run your usual yarn dev
or npm run dev
.
The variable inside the .env file will be added to the context (context.env
) and process (process.env
)
This module won't overload the environment variables of the process running your build.
If you need to use variables from your .env file at this moment,
just append require('dotenv').config()
to your nuxt.config.js
:
require('dotenv').config()
module.exports = {
// your usual nuxt config.
}
This will works thanks to the dotenv
library provided by this module as a dependency.
If you decided to ignore some values from your .env
file in the module configuration, this won't apply here.
yarn install
or npm install
npm run dev
Copyright (c) Nuxt Community
FAQs
A Nuxt.js module that loads your .env file into your context options
The npm package @nuxtjs/dotenv receives a total of 45,070 weekly downloads. As such, @nuxtjs/dotenv popularity was classified as popular.
We found that @nuxtjs/dotenv demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.