3 ms·
Or you can use Bun and have it handle all the nonsense. Or esbuild, but then you get a big blob, which isn’t really usable for a lot of things. The extensions
by Aeolun 2y ago
Or you can use Bun and have it handle all the nonsense. Or esbuild, but then you get a big blob, which isn’t really usable for a lot of things.
The extensions were always silly to me. Who changes only a few files to esmodules? You either change your whole project or not at all.
- lefrenchy 2y agoDoes it actually handle it though? I use bun to run my remix app at work and I have run into ESM/CJS issues.
- dimgl 2y agoBun handles all of the nonsense but the catch is that it blows up both in dev and in production. Wake me up when Bun doesn't segfault/fail to work at all.
- jasfi 2y agoI look forward to the day when Bun can run Next.js. Apparently the main showstopper is in the Next.js router.
- evilduck 2y agoI'm not steeped in the history of this issue but I periodically run a maintained and up to date NextJS app via Bun in a dev env just to monitor performance and compatibility. It uses the app router and the edge runtime middleware, hosted from a Docker container. I haven't seen massive benefits using Bun since Next doesn't use the Bun-specific libraries that make their performance numbers great, but I haven't seen any game breaking issues either, it runs and all the app's E2Es pass.
- afavour 2y ago> Who changes only a few files to esmodules? You either change your whole project or not at all. Transition. It’s a much lighter lift to transform a project piece by piece than do the whole thing.