François Jacques

I have the same issue on an older version of rails where bootsnap was integrated. It uses the same configuration as recommended above and it still breaks in a different...

If I remove `Bootsnap.setup`, to be precise. The gem can be `require`d, as long as `Bootsnap.setup` isn't called. That's my workaround for now - skip Bootsnap.setup if a environment variable...

Oh, we're loading an old version of debase as well for interactive debugging from IDEs. I'll see if bumping its version helps.

Actually, looking at the change in debase, it's perhaps due to the fact that ruby is used is still at 2.3? In mean, the custom bootsnap configuration might be working...

I'll have to put this on the backburner for now, at least I've isolated that removing Bootsnap.setup fixes it, which will do for now. Might get back to this in...

This is due to bootsnap being integrated in Rails 5.2. See https://github.com/deivid-rodriguez/byebug/issues/452

Try the bootsnap settings. It wasn't enought for me but apparently was good enough for others. Please report back if you still have issues with the bootsnap settings, this way...

Since this library is to log nestjs log errors through pino, it seems reasonable that pino be exposed as a peerDependency instead of a devDependency like currently. The workaround works...

I've hit that too. Exactly same symptoms, within a nextjs 13 (.4 and .5) application. Stack uses typescript as well (bundler module resolution). Switching to npm fixed it, but led...