You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set the NITRO_PRESET environment variable to aws-lambda and build the project
Deploy the project to Lambda with the expected values NUXT_CMS_API_KEY, NUXT_CMS_DELIVERY_TOKEN, NUXT_CMS_MANAGEMENT_TOKEN
Run the application several times and we can see process.env returns the expected values.useRuntimeConfig returns expected values on the first couple of loads but becomes the default empty values after
Describe the bug
useRuntimeConfig returns the environment variables as expected on the initial load but returns empty values for privateRuntimeVariables after loading the page several times.
Additional context
Current working version: 3.0.0-27498038.f18e68b
Latest version: NOT WORKING
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v14.21.1
2.16.0
1.0.0
[email protected]
webpack
nitro
,router
,head
,css
,plugins
,dir
,storybook
,buildModules
,modulesDir
,modules
,i18n
,app
,runtimeConfig
,publicRuntimeConfig
,alias
,typescript
,build
,serverHandlers
,devServerHandlers
,devServer
,bridge
@nuxtjs/[email protected]
()
,@nuxt/[email protected]
,@nuxtjs/[email protected]
Reproduction
test.get
asyncData
useRuntimeConfig
:nuxt.config.ts
:NITRO_PRESET
environment variable toaws-lambda
and build the projectNUXT_CMS_API_KEY
,NUXT_CMS_DELIVERY_TOKEN
,NUXT_CMS_MANAGEMENT_TOKEN
process.env
returns the expected values.useRuntimeConfig
returns expected values on the first couple of loads but becomes the default empty values afterDescribe the bug
useRuntimeConfig returns the environment variables as expected on the initial load but returns empty values for privateRuntimeVariables after loading the page several times.
Additional context
Current working version: 3.0.0-27498038.f18e68b
Latest version: NOT WORKING
Logs
No response
The text was updated successfully, but these errors were encountered: