NodeJS Evolves

Show Notes

(00:00) Welcome to Syntax!
(02:51) TypeScript
(10:03) SQLite v22.5
(14:35) .env support
(16:24) Test runner
(19:42) Watch Mode
(21:22) Glob support
(22:48) Top-Level Await
(26:40) Experimental require module
(29:39) Experimental WebSocket support
(30:13) Async local storage
(31:43) Single file executables
(32:46) Wishlist
* (32:54) Hot reload
* (34:20) Window shim
* (35:30) Better server
* (35:56) Better terminal integration
(41:36) Twitter responses
(46:54) Sick Picks
(54:56) Shameless Plugs

------------------------------------------------------------------------------
Hit us up on Socials!

#webdevelopment #webdeveloper #javascript

[karlstenator]

I'm a big fan of node SQLite, Environment and Watch. Approaching node is so much easier now for new comers with these features.

[cg]

Scott you're talking about Channels (Go Pipe in the Podcast). Its a concurrency primative. It would be more similar to streams in JS but 100x better.

[robertbaindourov]

Great talk. Exciting to see this thing get patched together into a RAD system for embedded systems, with Typescript support! :)

[erikslorenz]

Vitest has better assertions and such but node test is really quite good and just having no extra dependency is awesome. Plus it’s lightning fast. I don’t use many mocks but spies seem to work fine for me for the occasional use case. Yah no need for anything else except mock service worker for http testing

[thedelanyo]

Sqlite in node, could be used for stuffs like a cache system, probably a direct replacement of redis?

[JTWebMan]

Now we just need sqlite in browsers. I hate that it is not there as a feature. I know there are option to get it their but I never understood why browsers decided to not add it.

[smallmountain]

One annoying thing about the way they have implemented the .env support as a node.js command line option: What if you need to call something else that invokes node.js, but you need your .env to be loaded?
We use sequelize, for which we have to run migrations using the sequelize CLI. Somewhere deep inside of the sequelize CLI, they invoke node.js on our migration configuration .js file. With dotenv middleware, we can load our environment within that config file. But we have no way to tell the sequelize CLI, "Hey, when you launch node.js on our migration config js file, please pass in this command line option to node.js so that our environment file gets loaded!". So this has blocked us from adopting native .env file handling. There needs to be a mechanism *within your JS code* to load your environment, not *just* a command line option.
And, no, NODE_OPTIONS will not work either. That's just another environment variable we have to find a way to guarantee has been set.

[robertbaindourov]

I just save the file as .mjs extension and it allows ESM import statements vs require statements.

[Stoney_Eagle]

Ahhhwww but I like being next to other eagles 😢 hehe