Error accessing params and queryparams when browser script injected into NextJs v15 app

[a88zach]

Description

When using Nextjs v15, errors are thrown with accessing params and query params

Steps to Reproduce

Add newrelic to a NextJs v15 app
Follow this article to inject the browser script https://newrelic.com/blog/how-to-relic/how-to-monitor-app-based-router-nextjs-application
Start the application and click anywhere on the page once loaded

reproduction: https://github.com/a88zach/issue-1358

Expected Behavior

Relevant Logs / Console output

• Screenshots showing errors

[workato-integration]

https://new-relic.atlassian.net/browse/NR-364240

[a88zach]

Relevant changes in Next v15: https://nextjs.org/docs/messages/sync-dynamic-apis

[metal-messiah]

Thanks for sharing this @a88zach . Any chance you have a live replication case we can play with? Is this live on a publicly-accessible site? Otherwise, are you on a version of Next@15 greater than this rc?

[a88zach]

I'm on version 15.1.6. I don't have a public reproduction, but I'll put together an example repo and post it here

[jwage]

This issue may be related symfony/ux#2537

If you have an html element with a property containing an object that has dynamic methods, when you click the element, the element gets passed to newrelic stringify and calls toJSON on the element.__component. In the case of symfony live components, element.__component.toJSON() makes an ajax request and you get an error that the toJSON live action does not exist.

[a88zach]

@metal-messiah reproduction here: https://github.com/a88zach/issue-1358

[ptang-nr]

Hey @a88zach, I work with Jordan (metal-messiah). I gave the repro repo a go but was unable to reproduce the issue - I rigged up a fresh NodeJS app + Browser app, added a newrelic.js config w/ needed vals, and was able to bring up the test app. I tried clicking on the page, but didn't see any console errors.

I did notice it grabbed nr-spa-1.281.0.min.js. Not sure if that's the difference. Could you check if the issue is still happening and/or if there're other differences or console.log not accounted for in the repro app?

[a88zach]

@metal-messiah @ptang-nr I'm going to close this one out. I can no longer reproduce now that v1.281.0 of the client script is used. I couldn't tell in the commit history where this may have been addressed, but regardless, it's no longer throwing the error reported.