Skip to content

Conversation

@priscilawebdev
Copy link
Member

No description provided.

@priscilawebdev priscilawebdev requested a review from a team as a code owner November 7, 2025 07:15
@priscilawebdev priscilawebdev enabled auto-merge (squash) November 7, 2025 07:15
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 7, 2025
Comment on lines 4 to 11
import {getUploadSourceMapsStep} from 'sentry/components/onboarding/gettingStartedDoc/utils';
import {AwsLambdaArn} from 'sentry/gettingStartedDocs/node/awslambda/awslambdaArnSelector';
import {InstallationMethod} from 'sentry/gettingStartedDocs/node/awslambda/utils';
import {getInstallCodeBlock} from 'sentry/gettingStartedDocs/node/node/utils';
import {t, tct} from 'sentry/locale';
import {getInstallCodeBlock} from 'sentry/utils/gettingStartedDocs/node';

import type {Params, PlatformOptions} from './utils';

Copy link

Choose a reason for hiding this comment

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

Bug: Multiple files import from a deleted module sentry/utils/gettingStartedDocs/node, causing module resolution errors.
Severity: CRITICAL | Confidence: 1.00

🔍 Detailed Analysis

The file static/app/utils/gettingStartedDocs/node.tsx was removed, and its functions were moved to static/app/gettingStartedDocs/node/node/utils.tsx. However, several files, including static/app/gettingStartedDocs/node/awslambda/profiling.tsx, static/app/gettingStartedDocs/bun/bun/index.tsx, and multiple javascript framework files, still import from the old, non-existent path 'sentry/utils/gettingStartedDocs/node'. This will lead to module resolution failures and "Module not found" errors when these documentation pages attempt to load.

💡 Suggested Fix

Update all remaining import statements that reference 'sentry/utils/gettingStartedDocs/node' to the new path 'sentry/gettingStartedDocs/node/node/utils' in affected files.

🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: static/app/gettingStartedDocs/node/awslambda/onboarding.tsx#L4-L11

Potential issue: The file `static/app/utils/gettingStartedDocs/node.tsx` was removed,
and its functions were moved to `static/app/gettingStartedDocs/node/node/utils.tsx`.
However, several files, including
`static/app/gettingStartedDocs/node/awslambda/profiling.tsx`,
`static/app/gettingStartedDocs/bun/bun/index.tsx`, and multiple `javascript` framework
files, still import from the old, non-existent path
`'sentry/utils/gettingStartedDocs/node'`. This will lead to module resolution failures
and "Module not found" errors when these documentation pages attempt to load.

Did we get this right? 👍 / 👎 to inform future reviews.

Copy link
Member

@ArthurKnaus ArthurKnaus left a comment

Choose a reason for hiding this comment

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

🚀

Copy link
Member

@andreiborza andreiborza left a comment

Choose a reason for hiding this comment

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

LGTM

@priscilawebdev priscilawebdev merged commit 772cca1 into master Nov 7, 2025
47 checks passed
@priscilawebdev priscilawebdev deleted the priscila/ref/onboarding/remove-unused-node-utils branch November 7, 2025 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants