We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows_NT
v16.17.0
2.16.0-27720022.54e852f
1.0.0
[email protected]
webpack
typescript
alias
bridge
nitro
ssr
render
target
imports
loading
head
css
srcDir
plugins
components
buildModules
i18n
modules
publicRuntimeConfig
axios
router
vuetify
build
ignore
serverHandlers
devServerHandlers
devServer
@nuxtjs/[email protected]
()
@pinia/[email protected]
@nuxt/[email protected]
Not needed ( i dont think )
nuxi commands always use the default .env file even if the --dotenv arg is specified
.env
I think the right spot for the fix is @nuxt/config-edge src/load.js loadNuxtConfig
@nuxt/config-edge src/load.js loadNuxtConfig
With nuxi the incoming env config has the following pattern:
{ cwd: 'C:/code/Tempest/flexdeploy', fileName: 'production.env' }
which is the spread here:
envConfig = { dotenv: ".env", env: process.env, expand: true, ...envConfig };
Just changing to dotenv: envConfig.fileName ?? ".env" does the trick
dotenv: envConfig.fileName ?? ".env"
No response
The text was updated successfully, but these errors were encountered:
I can submit a PR for this as long as this seems like the right spot
Sorry, something went wrong.
The --dotenv flag is working in the latest version, so this issue is closed.
--dotenv
No branches or pull requests
Environment
Windows_NT
v16.17.0
2.16.0-27720022.54e852f
1.0.0
[email protected]
webpack
typescript
,alias
,bridge
,nitro
,ssr
,render
,target
,imports
,loading
,head
,css
,srcDir
,plugins
,components
,buildModules
,i18n
,modules
,publicRuntimeConfig
,axios
,router
,vuetify
,build
,ignore
,serverHandlers
,devServerHandlers
,devServer
@nuxtjs/[email protected]
,@nuxtjs/[email protected]
()
,@pinia/[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,@nuxt/[email protected]
------------------------------Reproduction
Not needed ( i dont think )
Describe the bug
nuxi commands always use the default
.env
file even if the --dotenv arg is specifiedAdditional context
I think the right spot for the fix is
@nuxt/config-edge src/load.js loadNuxtConfig
With nuxi the incoming env config has the following pattern:
which is the spread here:
Just changing to
dotenv: envConfig.fileName ?? ".env"
does the trickLogs
No response
The text was updated successfully, but these errors were encountered: