Edouard Bozon

Multi-version support compliance is coming to @NxDevTools v23, which means we will be able to plan atomic migrations of dependencies without a big-bang refactor when upgrading Nx. It's a major improvement as these upgrades can be tedious on some large workspaces.

@benjilegnard ça existe encore HATEOAS?

Je suis dans un arc HATEOAS + client angular / SPA en ce moment, ça intéresserait du monde ce délire ?

@brandontroberts @angular @Cypress_io @vite_js I'm actually moving our Storybook tests and CCT tests from Webpack to Vite using Analog. I'm expecting a massive speed-up. Thanks for the nice work @brandontroberts!

⚡️ Want to move your @angular and @Cypress_io component tests from Webpack to @vite_js? My latest post shows you how to do this in a few steps 👇

Here's my conversation all about @FFmpeg, the legendary open-source software powering most video on the Internet. In the episode, I talk with Jean-Baptiste Kempf and Kieran Kunhya. JB is lead developer of VLC and Kieran is FFmpeg contributor, codec engineer, and the person behind the now-infamous @FFmpeg account on X. VLC (@videolan), by the way, is also a legendary piece of open-source software: it's a video player that can open basically anything & has been downloaded over 6 billion times. I think both FFmpeg and VLC are two of the most important and impactful software systems ever created, both open source, and both created & maintained by volunteers: brilliant engineers from all walks of life. Thank you to everyone who contributed to FFmpeg and VLC, and in general to all engineers giving their heart & soul to building systems used by millions (or billions) of people, and often doing so not for money, status, or fame, but purely for the love of building great software and doing good for the world. Thank you to the builders! 🙏❤️ Shoutouts in this chat to @ID_AA_Carmack @karpathy @elonmusk @TimSweeneyEpic and everyone who is a contributor & fan of open source! It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 2:17 - Introduction 5:35 - Weirdest things VLC opens 9:59 - How video playback works 19:20 - Video codecs and containers 30:07 - FFmpeg explained 51:07 - Linus Torvalds 55:46 - Turning down millions to keep VLC ad-free 1:10:04 - FFmpeg & Google drama 1:29:18 - FFmpeg developers 1:35:55 - VLC and FFmpeg 1:40:29 - History of FFmpeg 1:43:46 - Reverse engineering codecs 1:57:01 - FFmpeg testing 2:01:08 - Assembly code (handwritten) 2:25:26 - Rust programming language 2:34:42 - FFmpeg and Libav fork 2:43:04 - Open source burnout 2:50:51 - x264 and internet video 3:04:07 - Video compression basics 3:11:04 - CIA and fake VLC 3:21:39 - Ultra low latency streaming 3:39:07 - AV2 codec and video patents 3:48:59 - VLC backdoors 3:59:14 - Video archiving 4:05:51 - Future of FFmpeg and VLC

@VojtechMasek Merge trains look similar to GitHub merge queues. I think they're missing a couple of features to be truly beneficial: Nx project graph awareness, which enables parallel queues and flakiness detection/quarantine.

@edbzn Client uses merge trains on GitLab and I have to say it was weird at first plus it involves scrange cases that are not good DX but I can see the benefit and it sure saves some seriouse CI time. I would like to see if it acually makes PR cycle faster (which I doubt atm)

We're considering integrating a merge queue, as our merge throughput has increased significantly with AI. I'd love to hear feedback from people with real-world experience. What tools have you used, and what are the pros and cons? We're managing a monorepo with trunk-based dev.

@SantoshYadavDev Thank you, @SantoshYadavDev. What kind of issues have you encountered? We're considering Trunk.io for its ability to catch transient errors between CI runs and classify them as flakiness.

@edbzn GitHub merge queue is what I have used so far, it has some issues but works. Other options are mergify and trunk .io

@StefanvHaas Interesting anyway, thanks

@edbzn I think it is just based on memory - but don't know it that deeply

Increasing Nx parallelism doesn't always bring the performance benefits you think. With tools that already parallelize internally (Vitest, Jest, esbuild...). You end up w/ threads competing for your CPUs, and runs become slower. edbzn.dev/blog/nx-parall…

@StefanvHaas I mean, if the inner tool tries to take all threads, then BuildXL will react and take fewer. But, if they do not share this information, how does it behave? Which one wins?

@edbzn it stores the resource usage of each target in a cache and uses that historic metadata to plan for resource usage

@StefanvHaas Nice, I wonder how dynamic parallelism would behave when different tools compete with each other.

@edbzn BuildXL has a solution for this. It has a dynamic parallelism based on memory usage. some targets are resource intensive while others aren't. VitePlus will eventually also support this

@sidferreiraz Hey! Awesome, thanks for letting me know, I missed the GitHub notification. I'll answer in the PR directly. Thank you!

Hey @edbzn ! I created a PR in nx autocomplete, trying to add some improvements if you agree.

Ideally, defining boundaries with glob patterns would solve this. Here’s a hypothetical example. This would also help in multi-platform monorepos, where you don’t want backend-only dependencies ending up in frontend bundles just because you imported a shared interface.

It’s almost impossible to maintain proper boundaries without more granular constraints. Today, we define boundaries at the project level, but files like *.spec.ts, *.story.ts, *.cy.ts, etc. shouldn’t be treated the same as src files.

Even experienced Nx users get confused between the concepts of affected graph and cache computation. They both save computation time in a monorepo, but in different ways. edbzn.dev/understanding-…

TypeScript excitement 😉 TS 6.0 is planning breaking changes to tsconfig options to deprecate some & change the defaults for others. This will simplify configuration & ease the transition to the Go-based TS 7.0 👍 The latest pitch is to enable strict type-checking by default 🎉

🚨 Nx experienced a supply-chain attack: - Attackers released compromised versions of Nx packages. - These weren't from our CI (lacked npm provenance signatures). - Nx Cloud is not affected We are actively investigating. All details 👇 github.com/nrwl/nx/securi…

I'm offering free 30 minute @NxDevTools configuration assessments! DM me with details about your repo and I'll send you a scheduling link. Last week, I was laid off by Nx, so I get to do what I enjoy doing for now. I'll keep going until I don't want to any more.

TypeScript excitement 😉 TS 5.9 RC is out 🎉 🔶 `import defer` by @NicoloRibaudo 🔶 module: "node20" for require(ESM) 🔷 --init has modern defaults (no downlevel) 🔷 Docs: Inline summaries for DOM APIs 🔷 IDE: Expandable hovers for Quick Infos 🔷 Perf: Faster type instantiation

@MaxKless @juristr my bad🤌

@edbzn @juristr uh oh 🇮🇹

You want to see my evening office view? 🤔Sure 🤷‍♂️ 🤪