Skip to content

Add ImportMetaENV interface to next.config.js #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aUsABuisnessman wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add ImportMetaENV interface to next.config.js #248

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions next.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,4 @@ const nextConfig = {
};

export default nextConfig;
interface ImportMetaENV

@greptile-apps greptile-apps Bot May 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 TypeScript syntax in a .js file breaks the build

interface ImportMetaENV is TypeScript syntax and is also incomplete (no body {}). next.config.js is parsed directly by Node.js as a JavaScript module, so this line will cause a SyntaxError at startup and prevent Next.js from reading the config at all. Even if the goal is to type import.meta.env, the correct location is a TypeScript declaration file (.d.ts), not the Next.js config. This line should be removed.