Environmental Variables not working even though it is defined in .a local/non-public address file?

TL;DR

In Next.JS, when you add environment variables in your .env.* files whose name don't start with NEXTPUBLIC , they are only available to the Node.Js environment. So you can access them in API Routes and data fetching methods like GetServerSideProps etc.

Fix

1. In Next.JS, when you add environment variables in your .env.* files whose name don't start with NEXTPUBLIC , they are only available to the Node.Js environment. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Environmental Variables not working even though it is defined in .a local/non-public address file?.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://stackoverflow.com/questions/72754832/environmental-variables-not-working-even-though-it-is-defined-in-env-local-.

Variant phrasings

Environmental Variables not working even though it is defined in .a local/non-public address file?

Why it happens

I have defined my keys in .a local/non-public address but still while calling it process.env.APIKEY it doesn't work as expected. APIKEY [your value] DATABASEURL=a local/non-public address/db/main Code: export const xata = new BaseClient({ apiKey - process.env.APIKEY, databaseURL: process.env.DATABASE_URL }); Folder Structure: Project - pages - public - .a local/non-public address - helper (file that needs api key)

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://stackoverflow.com/questions/72754832/environmental-variables-not-working-even-though-it-is-defined-in-env-local-file

Source: I have defined my keys in .env.local but still while calling it process.env.APIKEY it doesn't work as expected. APIKEY [your value] DATABASEURL=https://xxxxx/db/main Code: export const xata = new BaseClient({ apiKey - process.env.APIKEY, databaseURL: process.env.DATABASE_URL }); Folder Structure: Project - pages - public - .env.local - helper (file that needs api key)

Verified resolution: In Next.JS, when you add environment variables in your .env.* files whose name don't start with NEXTPUBLIC , they are only available to the Node.Js environment. So you can access them in API Routes and data fetching methods like GetServerSideProps etc. If you want to access variables in client browser you have to append NEXTPUBLIC . Your file becomes : NEXTPUBLICAPIKEY [your value] NEXTPUBLICDATABASEURL=https://xxxxx/db/main

Source URL: https://stackoverflow.com/questions/72754832/environmental-variables-not-working-even-though-it-is-defined-in-env-local-file