@next/env 16.3.0-canary.1

Next.js dotenv file loading

@next/env@16.3.0-canary.1 was published on 2026-04-17. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @next/env versions · Permanent reference to 16.3.0-canary.1 · Latest release

Package specifications

Version16.3.0-canary.1
License declarationMIT
Published2026-04-17T23:44:54.571Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.60 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars143129
Repository forks34873

Install @next/env 16.3.0-canary.1

npm install @next/env@16.3.0-canary.1
pnpm add @next/env@16.3.0-canary.1
yarn add @next/env@16.3.0-canary.1

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review9/10 — Found 27/29 approved changesets -- score normalized to 9
Maintained10/10 — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Packaging10/10 — packaging workflow detected
Binary-Artifacts0/10 — binaries present in source code
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Fuzzing10/10 — project is fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness