Skip to content

Commit feb7a91

Browse files
authored
neat (nextjs) troubleshoot docs update (#15430)
1 parent 8af7017 commit feb7a91

File tree

1 file changed

+3
-2
lines changed
  • docs/platforms/javascript/common/troubleshooting

1 file changed

+3
-2
lines changed

docs/platforms/javascript/common/troubleshooting/index.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
- blocked
99
- tunnel
1010
- non-Error exception
11-
- '404'
11+
- "404"
1212
notSupported:
1313
- javascript.capacitor
1414
sidebar_order: 9000
@@ -524,7 +524,7 @@ When using pnpm, you might encounter errors related to packages that can't be ex
524524
While adding these packages as direct dependencies might remove the warning messages, it often doesn't resolve the underlying functionality issues:
525525
526526
```bash
527-
pnpm add import-in-the-middle require-in-the-middle
527+
pnpm add import-in-the-middle@1 require-in-the-middle@7
528528
```
529529
530530
As a workaround, create or modify `.npmrc` in your project root. First, try to specifically hoist the dependencies in question:
@@ -686,6 +686,7 @@ shamefully-hoist=true
686686
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).
687687
688688
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.
689+
689690
</Expandable>
690691
</PlatformSection>
691692

0 commit comments

Comments
 (0)