Skip to content

Conversation

@chargome
Copy link
Member

  • adds more framework internals to the default ignore list (these will never emit sourcemaps and we just waste time processing these files)
  • updates ignore list to use glob patterns as this is the only way the cli properly picks them up

closes #18872

@chargome chargome self-assigned this Jan 22, 2026
@linear
Copy link

linear bot commented Jan 22, 2026

@chargome chargome marked this pull request as ready for review January 22, 2026 12:29
cursor[bot]

This comment was marked as outdated.

Comment on lines 35 to 46
MAIN_CHUNKS: '**/main-*',
FRAMEWORK_CHUNKS: '**/framework-*',
FRAMEWORK_CHUNKS_DOT: '**/framework.*',
POLYFILLS_CHUNKS: '**/polyfills-*',
WEBPACK_CHUNKS: '**/webpack-*',
PAGE_CLIENT_REFERENCE_MANIFEST: '**/page_client-reference-manifest.js',
SERVER_REFERENCE_MANIFEST: '**/server-reference-manifest.js',
NEXT_FONT_MANIFEST: '**/next-font-manifest.js',
MIDDLEWARE_BUILD_MANIFEST: '**/middleware-build-manifest.js',
INTERCEPTION_ROUTE_REWRITE_MANIFEST: '**/interception-route-rewrite-manifest.js',
ROUTE_CLIENT_REFERENCE_MANIFEST: '**/route_client-reference-manifest.js',
MIDDLEWARE_REACT_LOADABLE_MANIFEST: '**/middleware-react-loadable-manifest.js',
Copy link
Member

Choose a reason for hiding this comment

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

h: We need to ensure these are not too widely applied. The way it is now, these ignore patterns are also passed to the server source maps which might lead to false positives and ignore files we don't want to ignore.

We need a way to distinguish between which patterns we pass to which commands.

Copy link
Member Author

Choose a reason for hiding this comment

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

I reverted the changes for all framework, polyfills etc. and just kept the manifest ones for now. We need to investigate if we can split up the upload calls or be smarter here. Also with turbopack there are likely more files we can ignore

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

'**/route_client-reference-manifest.js',
'**/middleware-react-loadable-manifest.js',
'**/vendor/**',
]);
Copy link

Choose a reason for hiding this comment

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

Missing integration or E2E test for feature PR

Low Severity · Bugbot Rules

This feat PR changes the sourcemap ignore pattern behavior (merging user patterns with defaults instead of replacing) but only includes unit tests. Per the review rules: "When reviewing a feat PR, check if the PR includes at least one integration or E2E test. If neither of the two are present, add a comment, recommending to add one." An integration test verifying the actual sourcemap upload/ignore behavior with the new merged patterns would help ensure the feature works correctly in real build scenarios.

Fix in Cursor Fix in Web

@chargome chargome requested a review from andreiborza January 22, 2026 14:56
@chargome chargome merged commit bb40be1 into develop Jan 23, 2026
69 checks passed
@chargome chargome deleted the cg/JS-1501/nextjs-add-option-to-suppress-could-not-determine-source-map-reference branch January 23, 2026 10:26
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.

[nextjs] Add option to suppress "could not determine source map reference" warnings for specific files

3 participants