@next/env

What is @next/env?

The @next/env package is designed to load environment variables for Next.js projects. It allows developers to define environment variables in .env files and access them in their Next.js applications, ensuring that sensitive information is not hard-coded into the source code. This package is particularly useful for managing different configurations across various deployment environments, such as development, testing, and production.

What are @next/env's main functionalities?

Loading environment variables

This code snippet demonstrates how to load environment variables from the .env file in a Next.js project. It uses the `loadEnvConfig` method from the @next/env package, which reads the environment variables defined in the .env file and makes them available through `process.env`.

require('@next/env').loadEnvConfig(process.env.PWD || process.cwd())

Other packages similar to @next/env

dotenv

Dotenv is a popular npm package that loads environment variables from a .env file into `process.env`. Similar to @next/env, it helps in managing application configurations across different environments. However, dotenv is not specifically tailored for Next.js applications and can be used in any Node.js project.

cross-env

Cross-env allows you to set and use environment variables across different operating systems in a Node.js project. Unlike @next/env, which is focused on loading environment variables from files, cross-env is useful for setting environment variables directly in npm scripts in a cross-platform compatible way.

env-cmd

Env-cmd is another npm package that supports loading environment variables from a file into Node.js applications. It is similar to @next/env in its purpose but offers more flexibility in specifying different environment files for different environments (e.g., .env.production, .env.development) directly from the command line or scripts.

README

@next/env

Next.js' util for loading dotenv files in with the proper priorities