Fábio Luiz Nery de Miranda
Fábio Luiz Nery de Miranda
Thank you! May I contribute with testing/documentation?
> Solved this problem in next js 14.1.0, solution: I was able to solve this problem by removing browserslist:[...] of the package.json and I admit that this version is much...
Indeed it's a must-have feature! Any plans to be updated and merged?
Struggling to fix this error when trying to instrument a Next.js 14 application, app router based. ## Versions ``` "@appsignal/nodejs": "3.4.2" "next": "14.2.3", ``` ## Error ``` ○ Compiling /instrumentation...
It seems to be related to https://github.com/appsignal/appsignal-nodejs/issues/928
Same error with: ``` module.exports = { reactStrictMode: true, experimental: { instrumentationHook: true, serverComponentsExternalPackages: ['@appsignal/nodejs'], }, } ``` ### trace ``` ○ Compiling /instrumentation ... ⨯ ./node_modules/@appsignal/nodejs/build/Release/extension.node Module parse failed:...
## TLDR Loader changes the nature of the error to other never-ending `Can't resolve 'package_name'` errors. ## next.config.js ``` module.exports = { reactStrictMode: true, experimental: { instrumentationHook: true, serverComponentsExternalPackages: ['@appsignal/nodejs'],...
Any updates?
The RC version worked for me. Thanks!