Skip to content

fix(analytics): use more unique chunk name for middleware (#1339)#1357

Merged
chenxzhang merged 1 commit intomasterfrom
fix/middleware-chunk-name
Apr 15, 2026
Merged

fix(analytics): use more unique chunk name for middleware (#1339)#1357
chenxzhang merged 1 commit intomasterfrom
fix/middleware-chunk-name

Conversation

@chenxzhang
Copy link
Copy Markdown
Collaborator

@chenxzhang chenxzhang commented Apr 15, 2026

Fixes issue with Next.js where the "middleware" webpack chunk name collides with Next.js's middleware.js entrypoint when using the Node.js runtime.

Based on #1355 by @blurrah.

  • I've included a changeset (psst. run yarn changeset. Read about changesets here).

Fixes issue with Next.js where the "middleware" webpack chunk name
collides with Next.js's middleware.js entrypoint when using the
Node.js runtime.

Based on #1355 by @blurrah.
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 15, 2026

🦋 Changeset detected

Latest commit: 0356183

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@segment/analytics-next Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@chenxzhang chenxzhang merged commit a70d9e6 into master Apr 15, 2026
11 checks passed
@chenxzhang chenxzhang deleted the fix/middleware-chunk-name branch April 15, 2026 16:40
@github-actions github-actions bot mentioned this pull request Apr 15, 2026
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