You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
$ npx appmap-agent-js -- node node_modules/.bin/next dev -p 3001
(node:95565) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:95565) DeprecationWarning: Obsolete loader hook(s) supplied and will be ignored: transformSource
ready - started server on 0.0.0.0:3001, url: http://localhost:3001
/Users/dustin/dev/tmp/next-test/nextjs-blog/node_modules/next/dist/bin/next:158
commands[command]().then((exec)=>exec(forwardedArgs)).then(()=>{
^
TypeError: exec is not a function
at /Users/dustin/dev/tmp/next-test/nextjs-blog/node_modules/next/dist/bin/next:158:34
$ npx appmap-agent-js -- node node_modules/.bin/next dev -p 3001
/Users/dustin/dev/tmp/next-test/nextjs-blog/node_modules/@appland/appmap-agent-js/lib/node/abomination.js:38
throw new Error(
^
Error: Unable to solve the file extension issue of ESM loader -- see: https://github.com/nodejs/node/issues/41465
at Function.executeUserEntryPoint [as runMain] (/Users/dustin/dev/tmp/next-test/nextjs-blog/node_modules/@appland/appmap-agent-js/lib/node/abomination.js:38:13)
at node:internal/main/run_main_module:17:47
The text was updated successfully, but these errors were encountered:
Hi @dustinbyrne thanks for the bug report. The second issue is probably due to you tempering with a bin file in the next npm module. Extension-less files cause problems -- cf: nodejs/node#41465. So I rename them with an explicit .cjs extension. If the extension-less file and the .cjs file are not identical, I crash the agent instead of continuing with something inconsistent. We could discuss whether a simple warning would suffice. I'm looking at the root failure now.
One of two errors may appear. This issue is easily recreated using a sample project and created along with the following commands:
The errors are as follows:
The text was updated successfully, but these errors were encountered: