Fix build and lint configuration issues

[google-labs-jules]

User description

I have resolved several issues that were causing errors during build and development:

1. Redundant Lockfile: Removed package-lock.json since the project uses Bun, which prevents dependency resolution conflicts.
2. Next.js Config: Removed QCX (the project name) from transpilePackages in next.config.mjs to avoid potential recursion and build issues.
3. Lint Script: Changed the lint script in package.json from next lint to eslint . to fix a directory resolution error.
4. Environment Consistency: Committed the automatic updates made by Next.js to tsconfig.json and next-env.d.ts, aligning with modern Next.js development practices.

These changes ensure that bun run build and bun run dev execute correctly without errors.

---

PR created automatically by Jules for task 2000855008824799080 started by @ngoiyaeric

---

PR Type

Bug fix

---

Description

• Removed 'QCX' from transpilePackages to prevent build recursion issues

• Changed lint script from 'next lint' to 'eslint .' for CLI compatibility

• Updated TypeScript configuration to use 'react-jsx' for Next.js alignment

• Added Next.js auto-generated route types reference to next-env.d.ts

---

Diagram Walkthrough

flowchart LR
  A["Build Configuration"] -->|Remove QCX| B["next.config.mjs"]
  C["Lint Configuration"] -->|Use eslint| D["package.json"]
  E["TypeScript Config"] -->|Update jsx setting| F["tsconfig.json"]
  G["Type Definitions"] -->|Add routes reference| H["next-env.d.ts"]
  B --> I["Fixed Build"]
  D --> I
  F --> I
  H --> I

Loading

File Walkthrough

	Relevant files
Bug fix	next.config.mjs Remove QCX from transpile packages                                              next.config.mjs Removed 'QCX' from transpilePackages array, keeping only 'mapbox_mcp' Prevents potential build recursion and configuration conflicts +1/-1      package.json Update lint script to use eslint directly                                package.json Changed lint script from next lint to eslint . Resolves Next.js CLI directory resolution errors +1/-1
Configuration changes	tsconfig.json Update JSX compiler option for Next.js                                      tsconfig.json Updated jsx compiler option from 'preserve' to 'react-jsx' Aligns with modern Next.js TypeScript configuration best practices +1/-1
Enhancement	next-env.d.ts Add Next.js route types reference                                                next-env.d.ts Added import reference to Next.js auto-generated route types Ensures type definitions for dynamic routes are available +1/-0

---

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
qcx	Ready	Preview, Comment	Jan 19, 2026 10:07am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[charliecreates]

Changing linting from next lint to eslint . can broaden the lint scope and alter ignore behavior; scoping the paths and enabling caching would reduce CI noise and avoid accidentally linting generated artifacts. The jsx switch to react-jsx is generally aligned with modern Next.js defaults and doesn’t raise concerns on its own.

Additional notes (1)

• Maintainability | package.json:8-14
  Switching from next lint to eslint . can change which files get linted (and which are excluded) compared to Next’s defaults (e.g., respecting Next-specific conventions, default directories, and .next-related assumptions). This can inadvertently slow CI or lint generated/build artifacts if your .eslintignore/eslintIgnore isn’t tight.

Given the PR rationale cites a directory resolution error, it’d be safer to keep parity with Next’s intended target set by explicitly scoping the lint paths (and optionally caching).

Summary of changes

What changed

• Updated package.json to run linting via eslint . instead of next lint.
• Updated tsconfig.json JSX transform from "jsx": "preserve" to "jsx": "react-jsx" (Next.js modern default).

Note: The PR description mentions additional changes (e.g., next.config.mjs, next-env.d.ts, lockfile removal), but only the package.json and tsconfig.json diffs were provided here, so this review is limited to those files.

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Use a robust path for types In next-env.d.ts, change the import path for route types from ./.next/dev/types/routes.d.ts to the more robust ./.next/types/routes.d.ts to prevent build failures in production and CI environments. next-env.d.ts [3] -import "./.next/dev/types/routes.d.ts"; +import "./.next/types/routes.d.ts"; Apply / Chat Suggestion importance[1-10]: 8 __ Why: This suggestion correctly identifies that the hardcoded /dev/ path will cause build failures in non-development environments and proposes using the correct, environment-agnostic symlinked path, which is a critical fix for CI/CD pipelines.	Medium
General	Trim origin entries after split In next.config.mjs, add .map(origin => origin.trim()) after splitting the SERVER_ACTIONS_ALLOWED_ORIGINS environment variable to remove leading/trailing whitespace from each origin. next.config.mjs [8-10] allowedOrigins: process.env.SERVER_ACTIONS_ALLOWED_ORIGINS - ? process.env.SERVER_ACTIONS_ALLOWED_ORIGINS.split(',') + ? process.env.SERVER_ACTIONS_ALLOWED_ORIGINS.split(',').map(origin => origin.trim()) : ["http://localhost:3000", "https://planet.queue.cx"], [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: This is a valuable defensive coding practice that makes the parsing of the SERVER_ACTIONS_ALLOWED_ORIGINS environment variable more robust by handling potential whitespace, preventing runtime errors from malformed URLs.	Medium
Possible issue	Prevent linting generated output Update the lint script in package.json to prevent linting generated files and to enforce a stricter policy on warnings. Change the script to eslint . --ext .js,.jsx,.ts,.tsx --max-warnings=0 --ignore-path .gitignore. package.json [7-15] "scripts": { "dev": "next dev --turbo", "build": "next build", "start": "next start", - "lint": "eslint .", + "lint": "eslint . --ext .js,.jsx,.ts,.tsx --max-warnings=0 --ignore-path .gitignore", "db:migrate": "cross-env EXECUTE_MIGRATIONS=true bun lib/db/migrate.ts", "test:e2e": "playwright test", "test:e2e:ui": "playwright test --ui", "test:e2e:headed": "playwright test --headed", ... } [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that changing next lint to eslint . can cause issues by linting generated files. The proposed fix is robust, improving the linting script's correctness and reliability in a CI environment.	Medium
More