Node's amazing new feature is not compatible with Bun

Follow me on other platforms to stay connected:

[aravindhrajendran]

Dude You are just awesome, i can hear you teach something and keep hearing for hours.

[karlstenator]

Any example with "FOO BAR" shits me to f**king tears. Why is it so hard to write good documentation with relative examples?

[dealloc]

Drop-in replacement for Bun means that Bun supports base Node features, but it doesn't mean that it can't further expand on features. For .env Bun supports the same format as Node plus the ability to expand variables. It doesn't claim that you can replace Bun with Node; for example if you were to use Bun's own API.

[developerpranav]

Wow what a minute thing but makes a huge difference. Good that I always like to have quotes around my env values

[thehungrybird]

Why does it really matter, Bun already supports .env files in a much better manner than Node and most of the applications developed using Nodejs will still be using dotenv package for years, I doubt if it really breaks Bun?

[neji-hyuga-]

Bun or burger, the support and resources node has, they can't compare let alone compete. Node will still reign.

[adityagaur]

I dont know if this is a problem, whenever I am trying to create a project using bun i will usually find a lot of stuff which the bun either doesnot support or you have to do annoying things like playing with the commands to make it work. My favourite example is that of shadcn with bun.

[sahilaggarwal]

Tbh, I didn't like the logic behind Bun's env expansion. And even if they want to support expansion, they should introduce a more robust system as $ is pretty common to include inside the values of an .env file

[CodeWithSaidur]

Sir I am I am getting confused how can we connect web mobile and desktop on single Backend and Database HELP ME

[VeaceslavBARBARII]

Why not node-22?
Or do you always stick to LTS?