@elastic/apm-rum breaks SPA behaviour

[pierrechevaliercf]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

 Operating System:        
      Platform: win32        
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:       
      next: 13.4.8-canary.1  
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0      
      typescript: N/A        

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/pierrechevaliercf/NextSPAError

To Reproduce

Tested with next 13.4.6

1 - Install @elastic/apm-rum

npm i @elastic/apm-rum (5.12.0)

2 - Create a client component which will call and use this lib :

'use client';

 import init from "@elastic/apm-rum";

export function InitApm() {
    const a  = init; // just importing this function and calling it cause the error (commenting this line fix the behaviour)

    return null;
}

3 - Call this client component into your layout.tsx

4 - Navigate on your next app

5 - You will see that the SPA behaviour is now broken :

Describe the Bug

When @elastic/apm-rum is imported in a client component, the SPA behaviour no longer works, and navigation clicks fully reload the pages.

Expected Behavior

Next links should not reload the full page at each navigation click and works as an SPA even if @elastic/apm-rum is used.

Which browser are you using? (if relevant)

Chrome (114.0.5735.134) & Firefox (114.0.2 (64 bits))

How are you deploying your application? (if relevant)

No response

[pierrechevaliercf]

I've tested it again with 13.4.8-canary.1 and the issue still occurs

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!