Cannot read properties of undefined (reading 'filename') in Node v20.6.0 (yarn2) about nodemon HOT 7 CLOSED

Can you confirm how nodemon was invoked?

from nodemon.

Dear Remy,

I hope this message finds you well. I sought to emulate the behavior demonstrated in Node version 20.5.1, which involved utilizing the "nodemon" command to execute the "app.js" script within the context of my "start" script ("start": "nodemon app.js") as delineated in the "package.json" file. Additionally, I endeavored to incorporate environmental variables from an ".env" file using the command "nodemon --env-file=.env app.js."

Thank you for your attention to this matter.

Sincerely,
Louis

from nodemon.

I can't replicate. It's going to need more information from you - specifically how to replicate:

~/dev/nodemon/issues/2142$ npm run start

> start
> nodemon app.js

[nodemon] 3.0.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,cjs,json
[nodemon] starting `node app.js`
^C%

~/dev/nodemon/issues/2142$ cat package.json app.js
       │ File: package.json
   1   │ {
   2   │   "scripts": { "start": "nodemon app.js" }
   3   │ }
       │ File: app.js
   1   │ require('http').createServer((req, res) => res.end('ok')).listen(8000);
   2   │

~/dev/nodemon/issues/2142$ node -v
v20.5.1

from nodemon.

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

from nodemon.

i replicated this using yarn2 with ts-node, but with npm, nodemon worked with no issues and i don't know why

from nodemon.

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

from nodemon.

Automatically closing this issue due to lack of activity

from nodemon.