Yes I'm actually not too fond of the DX of Deno. I don't know why. It's a perfectly fine runtime and the permissions are obviously great but the texture is off if that makes sense.
I always gravitate to Bun when I can, it feels light and fresh.
Also I'm definitely going to try out your project this weekend, I've been looking for something like this to put together a free college info aggregation site from the college's public sites themselves, like financial aid dates, on campus programs, etc..
Like the the other commenter said, just for the permissions.
If Bun had a sandbox I'd use it.
Deno isn't my cup of tea (although I appreciate it more after building with it the past two days). My impression is that it is lightweight, you can deploy it easily to edge workers and it's built on rust so you can actually use it to build your own runtime with only the parts you want. (I was working on this for a game when I ran into the CF blog article).
Node/npm is the grandpa, can't go wrong but it doesn't run typescript by default and you'll lose cool points.
pnpm is cool don't really know what makes it different these days except it has a nice cache by default so you get faster installs, and you can do monorepos semi-easily. It's my default if I can't use Bun.
Bun is newer and my current favorite. You can compile to single executable, have access to most of the npm ecosystem (some packages still have minor issues), you have a built in sqlite db so it's great for prototyping, and some other niceties.
There's a lot more to it but that's the important differences I run into in my day to day.
Yeah since it's using Deno it'd be cool just use Deno throughout. Definitely gotta clean up the code quite a bit.