4 ms·
We’ll add the uncaught exceptions handler likely before Bun 1.2 and fix the issue with sourcemaps. Sourcemaps do work (with some rough edges) at runtime when ru
by Jarred 3y ago
We’ll add the uncaught exceptions handler likely before Bun 1.2 and fix the issue with sourcemaps. Sourcemaps do work (with some rough edges) at runtime when running TS/JSX/JS files, but are in a worse state with “bun build” right now.
We’ve been so busy with adding Windows support that it’s been hard to prioritize much else
- zackify 3y agoEvery couple weeks I try again to run my app fully on bun. For now I just use it as a packager. The big ones for me are continual prisma issues. Mainly due to poor decisions on their side it seems… Vite crashing. Because I’m using remix. And then the worst one I don’t see a way around: sentry profiling which requires v8. I can’t wait for the day everything can be on bun. Everything else sucks and is so slow or requires really bad configuration to make it work. Can’t believe node itself and TS are so terrible with module compatibility. Bun solves all of this and is 20000x faster when I can use it!
- ibash 3y agoWhat prisma issues are you running into? For us we just installed node alongside bun in our docker container and then ran prisma with node… was there something else?
- zackify 3y agoyou're running your app using the node runtime still. Half the reason I want to use bun is to not use node for the runtime so that it's faster and the docker image is also smaller.
- ibash 3y agoMuch appreciated and definitely rooting for bun! It’s still my goto choice for dev and can’t wait to switch production back to bun :)