Linus Unnebäck
Linus Unnebäck
Did it work with 0.5.18? 🤔
I believe that this is the problem: https://github.com/expo/expo/commit/6a750d0620da88294f9f1c7bada2cb5b6d7df3ff#r121599931 Adding `mjs` and `cjs` to `watcher.additionalExts` seems to resolve the issue
@brentvatne would you be able to review/merge this? 🙏
@EvanBacon would you be able to look at this? 🙏
Ran into this today as well, would be great to have `dist` ignored by default...
I'm not entirely sure on what the problem is, `console.log` doesn't do anything with the line number as far as I'm aware?
Great writeup! While I don't have time to look at this myself, I would love to accept a PR that fixes this 👍
This looks very good, the only thing that concerns me is that this will actually terminate the program, whereas the default behaviour is to just print a one line warning,...
I believe that the default behaviour for uncaught exceptions is to exit the process, they are not handled equally by Node.js
Hmm, just a thought. Do you think it would be possible to just modify the `.stack` property and then call the original implementation? Something like: ```js const originalEmit = process.emit...