Agent not working with Yarn Pnp + NextJS

[cmartineauOptimum]

Agent not working with Yarn Pnp + NextJS

[david-luna]

Hi @cmartineauOptimum,

basically what happens is that Yarn + pnpm is adding a custom loader for its cache under the hood. To do soo it sets the environment variable NODE_OPTIONS to a certain value.

The getting started guide assumes this var is not set so the npm scripts

"dev": "NODE_OPTIONS=--require=elastic-apm-node/start-next.js next dev"

overriding its value and making the yarn + pnpm loader unavailable.

You can change the script to append the required value into node options. This is an example

"dev": "NODE_OPTIONS=\"$NODE_OPTIONS --require=elastic-apm-node/start\" node next dev"

This will maintain reference to the required loaders and append the agent start script at the end.

Cheers!

[cmartineauOptimum]

Hello @david-luna,

I have tried your suggestion and it did work in this repository with the nextjs example.

When it came to try it with my project, I had this error :

Error: Qualified path resolution failed: we looked for the following paths, but none could be accessed.

Source path: /workspace/next
Not found: /workspace/next

it seem it wasn't able to start next. I change your suggestion to

"dev": "NODE_OPTIONS=\"$NODE_OPTIONS --require=elastic-apm-node/start-next.js\" next dev "

This seem to be working. do you see any issue with the change I made ?

[david-luna]

do you see any issue with the change I made ?

Maybe we weren't using the same yarn + pnpm version and the resolution differs a little bit. It is okay to use the extension.

[david-luna]

Hi @cmartineauOptimum

As per your last comment in assume the issue is fixed. Should I proceed to close it?

[cmartineauOptimum]

Yes, thank you