989: State of JS 2025  🔗 **Source:** [989: State of JS 2025](https://share.snipd.com/episode/6ff2b591-05c8-4bb9-b95f-cfbd3989d94f) ## Highlights - **Common Backward C Usage Pattern In Libraries** - Many libraries show a backward-C usage pattern: initial rise in use followed by growing negative sentiment over time. - Wes and Scott note this appears across tools like React, Express, and Webpack, signaling cyclical hype then backlash. Transcript: Scott Tolinski Where do you want to kick this off? Do we want to start on the libraries? There's the whole section on here for JavaScript features. As you mentioned, when we were talking about this pre-show, it's gotten kind of less interesting. Like, oh, okay, we're still talking about knowledge coalescing. Like, okay, we've been talking about that for years. It's been in JavaScript forever, you know. Wes Bos JavaScript had, like, I don't know, probably six or seven years of like major API improvements. And the actual like the language itself is starting to get pretty good. And like we certainly have had lots, lots of new things, you know, lots of new methods added to it. There's all these like immutable methods added to arrays. But simply just like looking at the stats of these features, it seems like people are not as as like dialed in on them as I think people are a bit more distracted by all the AI stuff going On right now. But that said, the libraries, the tooling, the bundlers, resources, all of those things that people are using, those have quite a bit. They're not as stagnant as the actual language features. And I think there's a lot more interesting stuff in that. ([Time 0:01:06](https://share.snipd.com/snip/a576d948-a53f-469d-8bee-f47c9842d29c)) - **Solid Rising With Enthusiast Users** - Solid shows an S-shaped trajectory with growing positive sentiment despite lower overall usage. - Scott and Wes think Solid attracts advanced developers seeking React-like ergonomics without major paradigm shifts. Transcript: Scott Tolinski Now, solid is still pretty low in terms of the have used, but solids makes like kind of like an S, whereas people are using it. I think the sentiment I've reached is that people are coming back to it and generally like we we had that episode about svelte recently and one of the comments was like so it's getting Close to being like solid it's like trying to catch up to solid now and i think solid does have a general sentiment of being a solid choice right like a a yeah and i i I don't mean to be a dad Joke about that, but I do think that it is an interesting use case for where like, I think people are seeing that it is definitely a good choice and solve some of their react issues without Being a completely different beast. Wes Bos Like something like Svelte, right? Yeah, you can move to it pretty quickly. Um, I feel like the people that use Solid are generally a little bit more advanced. Yes. And care about the nitty gritty, you know, right? They have taste. Most people will just kind of like default to writing React. And then once you either get really good at React or you kind of look for something else, and that's kind of where you start dipping into Vue and Svelte and whatnot. ([Time 0:03:36](https://share.snipd.com/snip/eaef67f7-9597-4172-9105-4a2418131f29)) - **Vite Became Ubiquitous After Course Correction** - Vite and Vite-related tools form a large S-shape: initial concerns corrected to strong adoption and satisfaction. - Both hosts find Vite ubiquitous; it's now among the most used and loved build tools. Transcript: Scott Tolinski Yeah. Other ones that share a similar kind of S shape, but more higher use territories. VTest, for one. I think VTest is still on the way up. People are realizing it's so fast and wonderful. And if you're using VTest, VTest just makes sense. Playwright is one of these things that I think people were paying attention to and then maybe over swung on a little bit. And then now with AI, people are back to using and enjoying Playwright because it's doing a lot of nice automation for them. Another one I noticed in here is Vite in general has a much larger version of this massive S shape. So what's so interesting about this is that this does typically follow a number of standard shapes. It's like the backward C where something gets popular and then everybody hates it. But then what I don't understand is why so many of them have the same S shape, where they really have positive opinions slightly negative the previous year and then positive the the year Before that and then like the long tail of what would be the boomerang it's almost like the boomerang is starting to happen and then it corrected itself back to an s this like backward C is happening and it pulls it back but veet oh my gosh, Vite is the most popular, most used tool on the planet. ([Time 0:04:56](https://share.snipd.com/snip/f0d344c4-f289-4b2c-8e73-65eeff2026b0)) - **Cache Components Not Whole Pages** - Reduce meta-framework complexity by caching and streaming at component granularity instead of whole-page caching. - Wes points to React Server Components and Suspense as ways to cache specific pieces like a live footer separately from a blog post. Transcript: Scott Tolinski A little bit of that let's talk i just want to hit real quick the meta framework pain point and the highest pain point for people is excessive complexity which like yeah excessive complexity You know the things that we're doing i I think there's too many times where we're having to do the same exact thing over and over again. Things feel boilerplate-y when like, man, I think that simplicity is a thing we'll continue to see with new frameworks, either frameworks doing more for you or because what like right Now these meta frameworks they you still need to bring so much stuff to have them be like fully usable and then you have to wire that up together it all feels like complex so using them all Wes Bos Together yeah we'll see something there i i think a lot of the complaints over excessive complexity have to do with individual component caching and updating individual things. Because in my opinion, one of the best things about React server components in Next.js is the ability to fetch data in the component, be able to use React Suspense. Now you can use the same thing in Svelte Land as well as Synchronous Svelte. I think that those are fantastic because if you have one thing on your site where it might take a little bit longer or you want to like not cache the entire page, but you want to just cache Like one piece of it. For example, like I have a footer on my website where the data in the footer is live. And I want that to continually be updated maybe every so often. But like the blog post itself doesn't need to be re-rendered every single time. And there's other parts, right? It doesn't make sense to cache at a page level. All of the stuff around React, suspense and caching and being able to stream from the server to the client, that stuff is both fantastic, but also really hard to wrap your head around And figure out how to do it right. ([Time 0:19:33](https://share.snipd.com/snip/414a4be2-2cb2-467b-ae84-f8f0a633172f)) - **Express Dominance Driven By Inertia** - Express remains dominant on backends largely due to inertia and middleware ecosystems despite newer servers like Hono. - Wes notes migration costs and compatibility (request/response models) keep many apps on Express. Transcript: Scott Tolinski Back end frameworks are interesting because, well, a lot of us are using full stack or meta frameworks now. So the folks who are running just straight up back end frameworks, it does seem like, well, it does seem like it seems like by this chart, Express is still the top dog. Wes Bos By far, like by far, 80 percent, Nest 32 percent. Yeah, Express is such a weird one where and like i have i have this myself as well where it like it's just not worth you have such a huge app not necessarily worth but it's such a big job to Move off of the like connect handlers and especially when you have your your off and everything just wound into the that as middlewares it's such a big job to move that into the next generation Which is like like web request web response which everything else uses now right um thankfully i i just moved mine off of express and it's it's it's not like oh that's so much better you Know that's the other thing as well it's like oh it's that's nice that it's all on like a standard web web request web response um yeah and i think that's why express is just so big you know Scott Tolinski Like there's it's not worth people's time to to move off of it but i do have i have noticed personally um some ai defaulting to express oh yeah and it like drives me nuts i i was doing something And then i see it's like setting up an express endpoint and where i'm i'm in the middle of a svelte kit site i have my agents tuned it knows it's a svelte kit site and so i'm like why the f are You doing an express route it's like well we needed a route for the API. It's like, brother, you have the whole API system baked into the app. Like, why are you setting up a separate Express server? I would never ask you to do that. Hano showing up for the first time in 15%. I would love to see next year Hano shooting up and Express shooting down. Wes Bos Personally, that's what I'd like to see. Yeah, so I linked up this Express versus Hano and you can kind of see every single NPM package right now is seeing like double numbers going up right now. Everything is just increasing an insane amount. And that's simply just because there's a lot more people coding right now and there's a lot more agents just spinning stuff up and people are just making projects left and right. So like the fact that both numbers are going up, I think is kind of a moot point because, but you can see that, I don't know, Hano is biting the heels of that. And also Hano is used in a lot of the meta frameworks. Even if you don't know that you're using Hano, it's often, it's either Nitro or Hano. Those are the two like little web servers that are sitting behind a lot of these frameworks that are being built. Scott Tolinski Yeah, yeah, it's interesting. ([Time 0:22:01](https://share.snipd.com/snip/f3465827-f8ed-4533-b577-5c85c954846f)) - **AI Models Shift Tooling Recommendations Rapidly** - AI code assistants heavily influence tooling recommendations and can shift preferred stacks across model versions. - They cited Amplifying.ai tests showing models moved recommendations from Prisma to Drizzle and changed many stack picks. Transcript: Wes Bos You see the amplifying.ai they had this yeah they had this like stats on what cloud code picks so what they did is they took a whole bunch of different code examples right they had like A react spa they had a back-end app they had i think they had a Python app and they had an XJS app. And then they asked it several questions of like, what should I use for styling? What should I use for components? Where should I host this? What should I use for error monitoring? And they tracked what Cloud Code gave them from the different models. And it's significantly different between the latest Opus update and the ones that were what Sonnet 4.5 versus Opus 4.5. Like Express just wiped off the map in the latest one. Prisma to Drizzle was nuts like it was recommending prisma let's see if you scroll down to where it says where models disagree hold on one second sorry for the interruption folks i had A salad delivery homemade non-brand i got some i got all kinds of stuff in here my life is the best shout out to Courtney yeah so cool look at this they asked like what ORM should I be using Sonnet 4.5 was Prisma 79% of the time Opus 4.5 was Drizzle 60% of the time and then Opus 4.6 Drizzle 100% of the time so like it's clear that they are training these things. Either they're taking the feedback as to when they suggested something and then they train the model on it, being like, oh, people didn't want this. Or they're simply just like, I often wonder if they're just writing these things in. I know, yeah. Straight into it. Because they certainly did that for getting rid of the purple. In these models, they had to beat the purple out of these models. And the purple is almost entirely gone. It's been replaced with like model space fonts and putting circles around it or borders around everything. But that was unreal that this is like, there's like a cloud code stack now where it just chooses all of the entire stack for you. Scott Tolinski This is fascinating. We'll link this up so people can check this thing out. Like authentication, custom DIY. Like where's BetterAuth on this? Because I always do. I use BetterAuth for everything. I do wonder, yeah, how much of this is just from the training verse. Like how are they steering this, if at all? Yeah. Really fascinating stuff. ([Time 0:25:15](https://share.snipd.com/snip/f8ad7fb1-920c-47dc-873c-5439bbbc8a92)) - **Migrate Tests To VTest And Playwright** - Try swapping Jest/Mocha for Vite Test and Playwright to improve test speed and realism. - Scott and Wes highlight VTest's performance and Playwright's browser-based integration testing as major reasons for recent migrations. Transcript: Wes Bos Let's talk about testing frameworks and kind of what's being used right now. So if we go down to we go to testing tools over time and then filter for the rank just to see what's being popped up. Just again, still number one. These tools that are so big, sometimes you think, oh, everybody's using VTest or whatever, but these big tools take a long time to dethrone. But VTest coming in at number three. Storybook still coming in at number two as well, which is impressive. And Playwright coming up. So the whole story of the state of js is vtest and playwright are just absolutely climbing everybody's using that lately yeah yeah wow those are some big climbs for playwright big climbs Scott Tolinski For vtest i think vtest is still going to keep climbing because you still have a lot of folks who aren't even on Vite, which like, I'm sorry, because it's just so wonderful. Yeah, I find this to be really interesting. Bunn tests showing up in here as well. Yeah, really interesting stuff. Wes Bos I don't even think you don't even need to be on Vite to make Vite test work. Scott Tolinski Is that true? Wes Bos Yeah, because like, like most people have like some expect or like Mocha, like you have some sort of unit tests. And you in many cases, you can simply just swap these things over, right? You're using Jest or whatever, you can just swap over the packages. And they will simply just work. I think a lot of the pain people have with Jest and whatever is that it still needs CommonJS and you're compiling your code so that it will run and now you're testing it against like this Weird compiled stage, which is not the code that's running in production. And that's a bit of a pain. So seeing people move to VTES, which is it's testing it as your code is running, not as it's running but it's testing it as if it were bundled for production. And then also Playwright, where you're literally just testing it in the browser, your integration testing. I think people's tests are getting in a much better shape. And honestly, I feel that as well. ([Time 0:30:39](https://share.snipd.com/snip/4b546495-2239-49d1-8c60-8c4cd88bfd42)) - **Zod Growth Shows Demand For Runtime Validation** - Zod saw a large usage spike as teams adopt runtime schema validation even in TypeScript projects. - Hosts tie this to developers wanting validation beyond static types, driving a 12% increase in Zod usage. Transcript: Scott Tolinski 4 000 people lodash lodash i'm surprised underscore isn't on here if the lodash is high still. Hold on. Wes Bos It is. It's number 12. Still 7% of people using underscore. And I wonder if this is just like, yeah, I've heard of that. I used that at one point. And then I'm going to put a check on there. But what's more interesting is which ones have gone up or down, right? Like Zod, massive 12% spike in the last year. Everybody is realizing, man, I need validation and schema for absolutely everything. I think like once everybody sort of got in, like was TypeScript pilled for a couple years, they're realizing, okay, I understand that everything is fully typed and validated. What else can be fully typed and validated? And that's when you get Zod pilled. Lodash, mindless. ([Time 0:33:25](https://share.snipd.com/snip/e769d047-961a-495f-95a5-681df6acf3c7)) - **Oxc And Biome Threaten ESLint Prettier** - New tooling like Biome and Oxc are disrupting ESLint/Prettier by offering faster, integrated parsing and TypeScript-compatible linting. - Oxc uses Go port of TypeScript; hosts expect OxLint adoption to rise quickly. Transcript: Wes Bos If we scroll down and look at utilities, like what people are using, you know, ESLint prettier looks like 90% people still using ESLint, 86% as prettier. We've seen a lot of like disruption in this space in the last little bit, namely Biome and OxLint, OxFormat sort of coming out and providing compatible APIs or simple just like better APIs that are way faster. But most people still on old faithful ESLint and prettier. But Biome, 16%. And then OxLint, 1%. If you were to tell me which one is way more popular right now, based on just my ears on talking to people, I would say OxLint. But Biome is 16 times bigger. Scott Tolinski Yeah. Biome, I think for being first to market in that regard is being the nice alternative there. I like biome. Yeah, biome is fine for me. I occasionally see the biome process on my computer going absolutely apeshit. So I don't know what's going on there. So I've personally been looking forward to Oxlant because I do feel like their approach is possibly a bit more, a bit more possible for consistency amongst moving into different frameworks Or HTML or CSS. I see it as being a better long term option. I would have to imagine by the time that this says JS 2026 here, Oxlant will be way higher than it is in this one because I think people are going to I think it's going to be a thing that people Are going to discover this year. Wes Bos If you're if you've never heard of it, like OXC is like it's from the folks at Vite or I think the like creator of it has joined void zero. And that OXC tool is like it parses and transforms. I was going to say JavaScript, but it parses and transforms languages, you know, like JavaScript, JSX, JSON, HTML, CSS, view templates, all of that stuff. Right. And then when you have a parser and transformer then you can build things like a linter like es lint or a formatter like prettier and those are the two things and i i'm kind of glad to see This as well because like i feel like now that most of the industry has standardized on using veet and now everybody's moving to using veet. And then the next thing is that people are going to be using the linter and formatter from that ecosystem. And then what's next, a JavaScript framework? Scott Tolinski Yeah. Yeah. And I think the reason why I prefer the OXC is like what they exactly say here is Oxlant leverages the native Go port of the TypeScript compiler providing full TypeScript compatibility As by contrast Biome is to implement its own type inference instead of relying on the TypeScript compiler. To me, using the Go port of TypeScript and actually using TypeScript instead of writing your own is like, that to me seems a more scalable approach. Also, you can have plugins that are compatible with ESLint with OxLint. So therefore, you know, your ecosystem is going to be larger. ([Time 0:37:20](https://share.snipd.com/snip/ac618a41-949b-48ee-8b53-ad03702e397f)) - **Node Stable While Edge Runtimes Rise** - Node.js remains top runtime because it solved many prior pain points; Bun and Deno grow but haven't dethroned Node. - Cloudflare Workers and WorkerD saw large adoption increases as edge-first hosting gains traction. Transcript: Scott Tolinski Number one is obviously Node.js for people out there. Yeah, I think there's like a weird kind of like Twitter subset of like people who think that like bun is it for everything. But Node, clearly top dog, top banana still, browser, obviously, but then no button being number three with a huge increase i have noticed like a lot of ai bros a lot of like non-developer Wes Bos Types like to talk about bun as being the thing i i feel the same way as well and i love bun i've got many videos on bun i use it on a lot of my projects and how obnoxious the bun guys on twitter Are when you post anything about node it's all it's always just use bun just use bun and it seems really big in the like um um like student area you know vibe code student area and it's being Obviously bun was purchased by anthropic will bun become like a like a like a runtime that like obviously it is right now. But like it seems like the place for Bun is people are sticking it in obviously Cloud Code, right? That's what power powers Cloud Code. I know OpenCode used to use Bun and they swapped it out for no just because they were having issues with with windows but like maybe that's the the move is that people are bun is just going Scott Tolinski To be this like nucleus engine that they can stick into products that get shipped yeah i in my experience i found bun to be buggy or have issues and like that's just my personal experience. But like, using the bun adapter for Svelte kit, like occasionally, there's issues there. But using bun for open claw won't work. So you have to use PNPM or NPM and node like there, I have hit a number of like, times when bun just doesn't work. And I don't know if that's, like, I'm just hitting weird edges, because I'm on, you know, weird stacks or different things here and there. But I don't know if that's, that's common. But me personally, I that's one, I don't have any problems with node node to me just works like that. Wes Bos That was the other thing. And I think that if you if you take a look at Dino, Dino's at 11% went down 1%. And I don't, I think that Dino didn't go down because Bun got more popular. I think Dino went down simply because people were fine with Node. Node added a lot of the stuff that we wanted, right? You can, you can run TypeScript in Node without a plugin. Now you can, you can load your environmental variables in without a plugin. Now, you know, like a lot of the just like little paper cuts of Node are solved. And a lot of people were saying, it's fine, it's fast enough, it works great for me, and I'm happy with it. But what else? Cloudflare workers went up 12%. Cloudflare has had a hell of a year just seeing how many people, like almost nobody was using Cloudflare workers a year ago. According to the survey, when was my first Cloudflare workers video? Because I feel like I was early. Six years ago, I posted a video. Here's what Cloudflare workers do. But obviously, as Cloudflare has pushed their workers platform more into like, oh, this can be used much more than just like a little middleware. Now, like you could build entire apps on it. You got databases and images and they've emailed now like they're almost like the full stack now. So a lot more people are opting to just build straight on that. And they sorted out their like it locally. ([Time 0:40:55](https://share.snipd.com/snip/ba57e442-23d3-4ce6-a339-71767fb135d1)) - **Wes Early Cloudflare Workers Experience** - Wes notes Cloudflare Workers adoption jumped as Cloudflare expanded to databases and images, making full apps feasible. - He recalled early WorkerD tooling pain but says local emulation and features improved the developer experience. Transcript: Scott Tolinski Yeah. Yeah. Interesting stuff. Hosting, I think, is interesting. AWS is top dog for cell number two. GitHub Pages is number three. Okay. Netlify, number four cloudflare at number five but a massive increase i could imagine cloudflare becoming an easy uh uh number three on this by next year with the i don't know i'm surprised Wes Bos That cloudflare is number five if we're being honest um but i man i think like the the people that are using github pages are doing it because they want somewhere to host their stuff for Free right and they're maybe they're sticking it they're building it every single pull request you can do that on cloudflare now for either free or they're like five dollar plan will Cover a lot of if you're like i want to put this somewhere but i don't feel like paying for it. Yeah. That's a good spot to throw all of your like little one-off projects. Totally. Netlify is still a huge one. Firebase. This is odd to me. Firebase was 1%. Now is 21%. Scott Tolinski Okay. That seems like something weird in the data. Wes Bos Not like i don't even yeah i don't know i do know that like the ai does pick firebase quite often for building apps right and and especially if you want to build like some quick little real-time App firebase is huge for that but and then also you can host it on Firebase. ([Time 0:45:03](https://share.snipd.com/snip/80c0ce1a-5871-4538-8fb0-95f4dd730e02)) - **Editor Switching Happens With Toolchain Shifts** - VS Code remains the dominant editor despite newer entrants like Cursor and Zed; switching editors often ties to broader toolchain changes. - Wes suggests moving editors becomes easier when switching linters/formatters and AI tools. Transcript: Wes Bos Text editors, 84% on VS Code, 26% on Cursor. Man, that's another one that surprises me. If you were to ask me i you you'd ask anybody and they say i was on cursor until january and now i'm don't even use an editor at all i just cloud code prompt in my brains and ship it who cares But that does not seem to be the case here seems like vs code still massive massive lead over cursor and that's my experience i don't i've never really found cursor to be that much beyond Scott Tolinski Vs code i know you like it and i know you have good arguments for that uh but vs code has always done done the trick for me the the editor i use most these days is zed though and zed being number Five on the list is that is not without its issues you know there's there's uh it's still very fresh but if we're talking like performant text editors that are like a GUI based text editor Wes Bos It's nice very nice I was thinking about you using Zed the other day and I thought like now now's the time to switch your editor because so much is changing, right? Like a lot of people don't want to switch their editor because their ESLint and Prettier finally works when they hit save in formats and they don't want to fuss with it anymore. They're not going to switch, right? But now, oh, you're going to, you're switching to Oxlint or Biome. Oh, and you're, you're using Cloud Code instead of like GitHub Copilot. There's a lot of change happening right now in the tools that you use. And when that happens, when you're using a new framework, you're using new formatters, new linters, all that type of stuff, it's not that big of a jump to also switch the editor, right? You got to get your keyboard shortcuts in place, but it's a good use case. ([Time 0:46:45](https://share.snipd.com/snip/57dbb4ba-2b58-439b-9510-13bb4917de6a)) - **AI Assists Many But Doesn't Replace Developers** - AI tool usage is widespread but not total: ChatGPT, Copilot, and Claude lead while full-code generation remains rare. - Survey shows average 29% of code is AI-assisted and 0% claim 100% AI generation. Transcript: Scott Tolinski We also have AI tools in here where a large amount of people, 6,000 people, put ChatGPT as number one. And those people just plug it into ChatGPT, I guess. I would recommend that. Like I get that's, you know, something that I'll pick up every now and again. But yeah, interesting that it's like the number one thing. Wes Bos That one is probably number one because, like, if you're asking what AI tools you use, people are going to be like ChatGPT. And then they insert their, like, Copilot 51%, Claude at 44%. And then it's interesting. This is a huge amount for Claude versus Cursor. It's almost double what Cursor usage is. Yeah. And this was before the January clodification of everybody. Scott Tolinski The clodification, yes. You know? The clodification. The clodification. The clod, yes. Wes Bos But I would have thought cursor. Cursor, 26%. Again, you asked me, what is the entire world using? Three months ago, I would have said cursor. Yeah. Scott Tolinski No, I wouldn't have. No, I wouldn't have said cursor. I would have said co-pilot. Yeah. Wes Bos Yeah, yeah, you're right. Everybody's bagging on co-pilot, but they don't realize how much of a, like the fact that everybody was already using VS Code and GitHub, how much of an advantage they have there. Scott Tolinski Yeah. Meanwhile, open code at only 58 respondents at number 14 doesn't even get a point as a point or 0,5, 0,5 percentage points here. Okay. I got to know. Uh, nearly 1% of the people here put grok. You're coding with grok. Wes Bos We did. Scott Tolinski I did our vibe video and I used grok. What are you doing? Wes Bos It was free for like three or four months. That's probably why. Scott Tolinski Oh my God, dude. Oh my God. That's crazy. That's shocking to me. Wes Bos Give me the Grok coding model. They have it, I guess. But like, where's a Grok CLI? Scott Tolinski But if there's all these other things out there that are so much better, what's possessing you to pick that? Wes Bos It's free. It's because it was free. That a guarantee that's why if you if you download install open code it like for the longest time it defaulted to grok because it was free yeah and then people were just using that for everything And it's it's no longer free so we'll see what it is next year i we almost need this like what ai tools are using we need this like every three weeks every three weeks yes for sure yeah um also In like ai code generation real quick zero percent of people said they are generating a hundred percent of their code with ai which is and just the spread in general was much more comforting Scott Tolinski Than i would have thought yes yeah yeah the average is 26 percent or no the average is 29 percent 29 percent yeah ([Time 0:51:39](https://share.snipd.com/snip/e09e3edb-4c7e-4643-a109-2b59ef52453e)) - **Wes Uses A Battery Heat Gun For Small Tasks** - Wes shares a practical personal tool: a battery-powered heat gun he uses to remove stickers and for electronics rework. - He values its portability despite lower max heat compared to corded guns for occasional tasks. Transcript: Wes Bos Got this for Christmas and it's something that I've been wanting forever. And this is a battery powered heat gun. So heat gun, I use quite a bit. You know, you got shrink wrap or if you need to heat something up to take a component off of a board. Or surprisingly, one thing I use a lot for is my wife comes home shopping and there's stickers on it, absolutely everything. And those stickers always come off brutally, right? You got to peel it and you got to get the goo gone. If you just heat them up a little bit, they come off way easier. And I always get annoyed with my heat gun because it's the same thing with the glue gun. I got a battery power glue gun as well. I was like, I'm not near an outlet and I'm doing something where I need to put heat on something. And I was like, you know what? It's not as like powerful as like a plug in one and it doesn't run as as as long, but I often don't need it to be super hot. I just need to be like good enough and I need to be wireless. So I got this one. It takes the wall batteries. I'll link up the one I actually ended up getting and it works awesome. ([Time 1:00:23](https://share.snipd.com/snip/4bc30097-e5e6-470a-bdc3-f736987905c6)) - **Scott Recommends Anker Cube Charger For Travel** - Scott recommends the Anker cube three-device MagSafe charger as a travel-friendly gift he buys repeatedly. - He praises its compact cube form, MagSafe, Apple Watch charging, and fast USB-C charging for travel use. Transcript: Scott Tolinski Is very hot uh i'm going to sick pick something that i amazon says i've purchased a lot of times and uh i've sick picked this before but it's been a long enough here that i feel like i should I should mention this thing uh Anker maker of really nice stuff in general um the Anker cube is this little cube it's currently on sale right now you can get for 83 bucks but it charges your Airpods on the side here or the airpods go on the right top here, it charges your Apple Watch. And then it does MagSafe right here. And it just plugs in with the USB-C. So it's the three-way charger here. And man, this is something I just like, this is a gift I buy for people like I got my dad one for his desk. But the best part about these things is that, like, for travel, it just shows up in this little cube. Now you got a three-way charger that's not some, like, obnoxious crazy shape to fit in your luggage. It packs so nicely because it's this little cube. And since it's just USB-C, you can throw your normal any USB-C charger on this bad boy. ([Time 1:01:40](https://share.snipd.com/snip/5da1f362-2616-499a-9826-bc545a74782e))