I'm running a nextJS app in a NX workspace and I need to get access to env variables on client side.
/apps/myproject/.local.env
NEXT_PUBLIC_PROJECT=my-super-project
/apps/myproject/next.config.tsx
module.exports = {
publicRuntimeConfig: {
PROJECT: process.env.NEXT_PUBLIC_PROJECT
}
}
In my nextJS app I'm trying several things:
/apps/myproject/pages/_app.tsx
import nextConfig from 'next/config'
const { publicRuntimeConfig } = nextConfig()
// ...
console.log(process, publicRuntimeConfig)
Running the app via nx serve myproject
does not give me any output on client, but on server side I do see the NEXT_PUBLIC_PROJECT
value. I'm not quite sure if my next.config.js file is read by nx at all...
For anyone who is still having this issue.
For loading the env variables in react project, followings are required:
.env
file at application level.apps/myReactApp/.env
If you want to load different env files for different configuration, then you can do it like this:
For QA: `npx env-cmd -f apps/web-client/.env.qa nx run web-client:build:qa`,
For staging: `npx env-cmd -f apps/web-client/.env.staging nx run web-client:build:staging`,
NOTE: you need to install env-cmd package
More about loading environment variable in their doc.