node

Top-scored projects: https://commondatastorage.googleapis.com/ossf-criticality-sc... For JS: node│https://github.com/nodejs/node│JavaScript│73│0│3226│10│64.7│63│1517│2055│4.1│10499… react-native│https://github.com/facebook/react-native│JavaScript│71│0│2866│5│50.5│15│778│1694│3… react│https://github.com/facebook/react│JavaScript│91│0│1609│6│20.9│6│692│973│3.8│333619… gatsby│https://github.com/gatsbyjs/gatsby│JavaScript│67│0│3873│3│83.3│2│2181│2526│1.9│118… three.js│https://github.com/mrdoob/three.js│JavaScript│130│0│1694│8│64.3│12│606│801│3.1│229… bootstrap│https://github.com/twbs/bootstrap│JavaScript│113│0│1360│7│21.7│9│729│912│2.1│14966… material-ui│https://github.com/mui-org/material-ui│JavaScript│76│0│2256│7│53.8│43│1561│1826│2.… odo

Here's a changelog instead of this weird blog post: https://github.com/nodejs/node/blob/master/doc/changelogs/CH...

QUIC support has landed behind an experimental flag https://github.com/nodejs/node/issues/23064 As for HTTP/3 that’s a bit further down the line

If you had clicked the link, you'd see that it is primary a list of libraries. Admittedly I had not considered that Swift can use native C libraries. I'm not sure whether it makes sense to expect a wrapper library or not, whether that would help. But overall, I'm pretty sure no one is doing nor advancing towards HTTP3 in Swift at the moment, which makes me feel like the Swift community is not a serious player for general development. Some trivia, not necessarily a recommendation: Node.js is the only language I know of working towards HTTP3 support in the platform (also in this link, evidence that I may be biased in my priorities): https://github.com/nodejs/node/issues/23064

Wow, that resonates quite a lot with me, though I'm not 55 yet. I started my career as a software engineer with web development in the 90's. Everything seemed simpler. Literally. Then, fast forward to 2020. I'll cite you an example of what happened EXACTLY yesterday. I have a web application which is complete and ready to be deployed. It's a backoffice application for one of our e-commerce sites. It's built using Phoenix, so there is a separate assets folder which contains a webpack config and its own package.json as well. The frontend updates require me to update the assets manifest as well. So, we've setup CI for it to automatically do that for each deploy. So, as usual, it simply runs npm install, but, suddenly, everything broke. Remember, this was fine until our previous deploy. It was some weird error from node about not being able t

The experimental flag was recently removed in v12.17.0 (though the release notes still say ESM is an experimental feature) https://github.com/nodejs/node/releases/tag/v12.17.0

I second this, of course VS Code needed Electron which needs Node all ready for ARM https://github.com/nodejs/node/issues/25998#issuecomment-637... Also to note Edge is available on ARM. Very happy Surface Pro X user here.

There are definitely few things which are done in different way in Deno as part of re-design. But that does not mean NodeJS does not take care of it or at least provide the some API to tackle that issue. In this case, Stream interface API in NodeJS are the solution to the problem. They help you build layer over native EventEmitter interface or rather strictly speaking they help extend it. This links might be helpful for you. Backpressuring in Streams - https://nodejs.org/es/docs/guides/backpressuring-in-streams/ Official Docs on Stream API - https://github.com/nodejs/node/blob/master/doc/api/stream.md Note that HTTP server in NodeJS already implements it.