[PR #34] [CLOSED] Consolidate duplicate Next.js config files #36

New Issue

2026-02-16T03:16:44-05:00

yindo commented

2026-02-16 03:16:44 -05:00

📋 Pull Request Information

Original PR: https://github.com/run-llama/auto_rfp/pull/34
Author: @roland-at-ailtir
Created: 12/10/2025
Status: ❌ Closed

Base: main ← Head: roland/bug-fix/next-config

📝 Commits (2)

04c28fe consolidate duplicate Next.js config files into TypeScript version
6685050 Fix merge conflicts

📊 Changes

2 files changed (+12 additions, -18 deletions)

View changed files

➖ next.config.js (+0 -17)
📝 next.config.ts (+12 -1)

📄 Description

Problem

The repository had two Next.js configuration files:

next.config.ts (TypeScript, mostly empty)
next.config.js (JavaScript, containing actual configuration)

Having both files creates confusion about which configuration is actually being used by Next.js. The .js file contained important environment variable configurations for LlamaCloud API keys and React strict mode settings.

Solution

Consolidated the configuration into a single next.config.ts file:

Migrated all configuration from next.config.js to next.config.ts
Removed the redundant next.config.js file
Verified the build works correctly with the consolidated configuration

Benefits

Eliminates ambiguity about which config file is active
Aligns with TypeScript best practices for the project
Maintains all existing functionality (environment variables, React strict mode)

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/auto_rfp/pull/34 **Author:** [@roland-at-ailtir](https://github.com/roland-at-ailtir) **Created:** 12/10/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `roland/bug-fix/next-config` --- ### 📝 Commits (2) - [`04c28fe`](https://github.com/run-llama/auto_rfp/commit/04c28feb576653f2233739a8f95d4569a56f7997) consolidate duplicate Next.js config files into TypeScript version - [`6685050`](https://github.com/run-llama/auto_rfp/commit/6685050384d9c23b3577da7e671e721e4b9803f0) Fix merge conflicts ### 📊 Changes **2 files changed** (+12 additions, -18 deletions) <details> <summary>View changed files</summary> ➖ `next.config.js` (+0 -17) 📝 `next.config.ts` (+12 -1) </details> ### 📄 Description ## Problem The repository had two Next.js configuration files: - `next.config.ts` (TypeScript, mostly empty) - `next.config.js` (JavaScript, containing actual configuration) Having both files creates confusion about which configuration is actually being used by Next.js. The `.js` file contained important environment variable configurations for LlamaCloud API keys and React strict mode settings. ## Solution Consolidated the configuration into a single `next.config.ts` file: - Migrated all configuration from `next.config.js` to `next.config.ts` - Removed the redundant `next.config.js` file - Verified the build works correctly with the consolidated configuration ## Benefits - Eliminates ambiguity about which config file is active - Aligns with TypeScript best practices for the project - Maintains all existing functionality (environment variables, React strict mode) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-16 03:16:44 -05:00

yindo closed this issue

2026-02-16 03:16:44 -05:00

yindo referenced this issue

2026-02-16 03:16:45 -05:00

[PR #36] [MERGED] Update README to use .env instead of .env.local #38

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: run-llama/auto_rfp#36