 We need a name for the segment. What is it? Is it the two-minute speedrun of the web? Two-minute speedrun? That's pretty good, because I was thinking of HTTP two or three in two. And you. But it's just too many numbers, then, really, isn't it? I mean, I can drive it home. I mean, I can drive it home. So two minutes, you're going to talk about a thing. And what are you going to talk about? I'm going to talk about my recent explorations with Webpack and workers. You have two minutes. Go. Workers. Yes, I'm aware of them still. I think this is a copy of exactly what we said in the previous episode. But now imagine you want to have module loading in workers. You can have that. That's the import function. But it's not available in workers anywhere. Yes. So for now, you can't. But so I said, OK, cool, let's use something like rollup or Webpack, where you basically transform the syntax into just like inlining the things or loading with some other mechanism. Workers have input script. The main thread has script tags so you can emulate the behavior. So I look into Webpack. And I was trying to build a little app that has logic in the worker and UI in the main thread and had some modules that were shared between the main thread and the worker. And this is something you can deal with because you can have, like you say, your main page just including it as a script tag or dynamic import. And your worker can use that horrible import script synchronous function. But it works. So yeah, and my thought was Webpack should figure this out, right, like you should see, oh, this is a shared code. Let's put this in a separate file. Using its commons chunking stuff. So it realizes, oh, here's the common bit. I'll put that into a separate file. Right, problem solved. You would think not quite. So there's a slight difference. So because in Webpack, you have entry points. And these entry points are assumed that you take one of them at a time. But with a worker, you actually take an entry point and the worker entry point at the same time. So there's a different assumption because you can actually, between entry points, usually Webpack doesn't put common modules in a shared thing. So this is when you're using Webpack to do the worker magic for you? Yeah. What if you just do it separately? You've got two entry points. One of them doesn't know that they're shared modules. At least I haven't figured it out. So now I have put in an issue, and I'm going to discuss with the Webpack people how we can support workers. Because I feel like I want to make 2018 about workers. So we need support and tooling for that. That was very good timing because nicely done. Music to my ears. Nicely done. It's not as good as the one we used at Christmas. If I set that off again, do you want to just beatbox? And then we could dub that. I'll give you 10, maybe five seconds. Five, four, three, two, one. That was bad.