Skip to content

neat (nextjs) troubleshoot docs update #15430

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −2
Open

neat (nextjs) troubleshoot docs update #15430

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/platforms/javascript/common/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ keywords:
- blocked
- tunnel
- non-Error exception
- '404'
- "404"
notSupported:
- javascript.capacitor
sidebar_order: 9000
Expand Down Expand Up @@ -524,7 +524,7 @@ When using pnpm, you might encounter errors related to packages that can't be ex
While adding these packages as direct dependencies might remove the warning messages, it often doesn't resolve the underlying functionality issues:

```bash
pnpm add import-in-the-middle require-in-the-middle
pnpm add import-in-the-middle@1 require-in-the-middle@7
Copy link
Member

@BYK BYK Nov 8, 2025

Choose a reason for hiding this comment

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

I think mentioning the version pinning with some rationale or future plans would provide good context

```

As a workaround, create or modify `.npmrc` in your project root. First, try to specifically hoist the dependencies in question:
Expand Down Expand Up @@ -686,6 +686,7 @@ shamefully-hoist=true
In case you are using Session Replay and experience performance issues with the client instrumentation hook, you can try lazy-loading session replay as described [here](/platforms/javascript/guides/nextjs/session-replay/#lazy-loading-replay).

If you want to init the SDK itself at a later point, this will result in tracing data losing accuracy and errors could happen before the SDK is initialized. This should be a tradeoff you make based on your use case, although we recommend initializing the SDK as early as possible.

</Expandable>
</PlatformSection>

Expand Down
Loading