Skip to content

fix(ci): use webpack build to fix E2E TypeError in production mode - #276

Merged
alfredo1996 merged 1 commit into
release/1.0from
fix/e2e-neo4j-externalize
Mar 30, 2026
Merged

fix(ci): use webpack build to fix E2E TypeError in production mode#276
alfredo1996 merged 1 commit into
release/1.0from
fix/e2e-neo4j-externalize

Conversation

@alfredo1996

Copy link
Copy Markdown
Owner

Summary

  • CI was running npx next build which defaults to Turbopack in Next.js 16 (because turbopack: key exists in config)
  • Turbopack bundles the connection module differently, causing TypeError: a is not a function in all parameter-related E2E tests
  • Fix: use npm run build which explicitly passes --webpack

This fixes the pre-existing E2E failures on release/1.0 that were blocking PRs #273, #274, #275.

Test plan

  • CI E2E tests pass (the whole point of this PR)
  • Local build passes with npm run build

🤖 Generated with Claude Code

…pack)

Next.js 16 auto-enables Turbopack when a `turbopack:` key exists in
next.config.ts. The CI workflow was running `npx next build` which
used Turbopack, causing `TypeError: a is not a function` in E2E tests
because Turbopack bundles the connection module differently than webpack.

The app's build script already specifies `--webpack` explicitly.
CI should use `npm run build` to match.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Mar 30, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@alfredo1996 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 13 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 3 minutes and 13 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f76eb652-bfc4-4bd2-994b-b846bd39a322

📥 Commits

Reviewing files that changed from the base of the PR and between 6f01cf8 and a384912.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/e2e-neo4j-externalize

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@sonarqubecloud

Copy link
Copy Markdown

@alfredo1996
alfredo1996 merged commit 0ed0468 into release/1.0 Mar 30, 2026
12 checks passed
@alfredo1996
alfredo1996 deleted the fix/e2e-neo4j-externalize branch March 30, 2026 20:19
alfredo1996 added a commit that referenced this pull request May 10, 2026
…pack) (#276)

Next.js 16 auto-enables Turbopack when a `turbopack:` key exists in
next.config.ts. The CI workflow was running `npx next build` which
used Turbopack, causing `TypeError: a is not a function` in E2E tests
because Turbopack bundles the connection module differently than webpack.

The app's build script already specifies `--webpack` explicitly.
CI should use `npm run build` to match.

Co-authored-by: alfredorubin96 <alfredo.rubin@neotechnology.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants