JavaScript Jabber

A weekly discussion by top-end JavaScript developers on the technology and skills needed to level up on your JavaScript journey.

Follow

JSJ 434: Understanding and Using ES Modules in Node with Gil Tayar

Guests :

Gil Tayar

Hosts :

Published : May 19, 2020

Duration : 1 Hours, 21 Minutes

Show Notes

Gil Tayar gave a presentation recently on ES modules in Node. He joins the panel to discuss how to use and think about ES modules. With considerable pushback from AJ, Gil explains how to start using modules and what the tradeoffs are between modules, script tags, and build tools.

Panel

AJ O’Neal
Aimee Knight
Charles Max Wood
Steve Edwards
Dan Shappir

Guest

Gil Tayar

Sponsors

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

Links

JSJ 341: Testing in JavaScript with Gil Tayar

Picks

AJ O’Neal:

Aimee Knight:

AJ ONeal - YouTube

Charles Max Wood:

Steve Edwards:

Dan Shappir:

webinstall.dev
Visit Israel

Gil Tayar:

Follow Gil on Twitter > @giltayar
Sunset Blvd
Node v14.0.0

Follow JavaScript Jabber on Twitter > @JSJabber

Special Guest: Gil Tayar.

Transcript

CHARLES MAX_WOOD: Hey everybody and welcome to another episode of JavaScript Jabber. This week on our panel, we have AJ O'Neill.

AJ_O’NEAL: Yo, yo, yo. Coming at you live from sunny, pleasant, pleasant Grove.

CHARLES MAX_WOOD: Amy Knight.

AIMEE_KNIGHT: Hey, hey from a gloomy Nashville.

CHARLES MAX_WOOD: Steve Edwards.

STEVE_EDWARDS: Hello from sunny Portland.

CHARLES MAX_WOOD: Dan Shapir.

DAN_SHAPPIR: Hey, coming at you from Tel Aviv with was sunny. Now it's night still under lockdown. Hopefully not for too long though.

CHARLES MAX_WOOD: I'm Charles Maxwood from devchat.tv. And this week we have a special guest, it's Gil Tayar.

GIL_TAYAR: Hi everybody, also from Tel Aviv, starting our set Independence Day celebrations here.

CHARLES MAX_WOOD: Oh, congrats.

If you're a front-end developer looking for remote work, then I recommend G2i, a React and React Native focused hiring platform that will connect you directly with their clients that need your skillset. What makes G2i a unique hiring experience is that they spend the time marketing you to their clients of your choice. G2i is a team of engineers that technically vets you upfront. If you pass their vetting, their clients have agreed to skip their initial interview process, saving you time and energy getting your next gig. They take care of all the hard work for you so you can get focused on development. To join G2i, go to g2i.co and apply.

CHARLES MAX_WOOD: So Dan set this up and I'm gonna let him introduce what's going on. Gil, we've had you on before though, I'm pretty sure. Do you wanna just remind people who you are?

GIL_TAYAR: Yep, I'm senior architect, whatever that means, at Applitools. I designed and architected and built a visual grid. I'm also a developer advocate, go to conferences, blog posts, Twitter, whatever, like part-time-ish thing and basically 30, 35 years in the industry. So, did a lot.

CHARLES MAX_WOOD: Cool. All right, so Dan, you were giving us kind of an intro before the intro, and all I really heard was the AJ's are contrarian. So do you want to tell us what the deal is here?

DAN_SHAPPIR: So yeah, for sure. So I think right before we went into lockdown, there was this conference in Tel Aviv called No TLV. I actually missed that conference because I already put myself in lockdown. That being said, I did watch all the videos and one of the great videos from that conference was Gil speaking about ESM modules and how great they are in general and how great they are in was an excellent topic on conversation. So I wanted to have Gil here on the show.

AJ_O’NEAL: Blessing.

CHARLES MAX_WOOD: you know, what the ESM modules are and how they work in general. I think, I think some people are going to be familiar and some people kind of take for granted how they work, may have used them and not realized it. So yeah, just give us a rundown and then we can talk about what it means in Node.

GIL_TAYAR: Sure. ES modules are like first things first, they are a feature of JavaScript since ES6 is 2015. So they're with us for five or six years already. Basically, they haven't been implemented. They're the last ES6 feature that's been implemented. They've started to become implemented on the browser, like natively, and now in Node.js natively. But people have been using them for five years, not natively, but rather by transpiling them. And we'll talk a bit later about, I mean, what does transpiling ES modules do in Node.js and in the browsers? There's a whole history there and a lot of stuff that's really, really confusing because of that history and because everything is so late in the game. Hopefully this episode will remove a lot of that confusion.

DAN_SHAPPIR: Just to add to that, just to maybe to clarify, when we say ES modules, what we practically mean is the import keyword and the export keyword and the export default keyword combination and so forth, right?

GIL_TAYAR: Exactly. Let's think pre-ES modules days. Back in the days, I mean, really back in the days, JavaScript didn't even have a module system. It never did. There was one big script source and people worked with that and that was fine back in the MySpace days and GeoCity days. But then things started to become bigger and bigger, the source code became bigger and bigger, and people wanted to separate them into separate files, which makes sense. What people did in the JavaScript, well, in JavaScript was because there was no module system, they invented one. And then we had things like, people don't remember that today, but Dan probably does, AMD and RequiredJS were the two more popular ones. They were these weird stuff where you wrote the files and then there was this thing that combined them all into one and like hooked them with various means. I think Google Closure also did sort of a module thing. But in the end, the browser, and we're talking browser days, pre-Node.js, the browser had to have just one script source. So basically all the files were combined into one. That was pre-ESM. Now, even pre-ESM, Node.js comes to the scene. Node.js had to have a module system because writing server-side code with one big file doesn't make sense. So they borrowed one, something that wasn't really used back then, but Node.js made very popular, it was Common.js. Common.js is what is now used in Node.js for a module system. It's that require load dash or require foo or whatever, where you write a file, what is called a module. You do a module.exports and export whatever you want on that exports object. And when you require that file, Node.js basically runs the file, takes the module.exports object and returns it as a return value of the require. So it's a really, really cool and simple module system. Love it. I mean, when I saw it, it was like, oh, this is so simple. Makes total sense. And that was Node.js. That was pre-ES6. And then in the ES6, people came and said, no, we need a real module system something that is part of the language.

AJ_O’NEAL: Something that breaks the language, you mean?

GIL_TAYAR: Well, that's, I mean, conditional, a lot of things break the language. Object.assign breaks the language, for, out breaks the language, async, away breaks the language, promise breaks the language.

AJ_O’NEAL: Wait, how does object.assign break the language?

GIL_TAYAR: I mean, it's not backward compatible.

AJ_O’NEAL: How is it not backwards compatible?

GIL_TAYAR: No, not object.assign, okay, but it's for, away.

DAN_SHAPPIR: No, actually object.assign as well. If you happen to have, if somebody happened to have, to put and assign method on object on the global object instance. And then you get object to sign as part of the language. Then all of a sudden you have a problem and there's that famous smoosh gate because what was it? Muthools or somebody put a flat or flatten on arrays and suddenly you couldn't do array.flat because that broke existing code.

GIL_TAYAR: Right, but sorry, but that's an edge case. That's definitely an edge case, but I mean, any feature, any syntactic feature in ES6, 7, 8, whatever, breaks previous languages. I mean, that's why we transpiled to ES5, because all those language features don't work in previous JavaScript syntax. A lot of new JavaScript breaks old JavaScript. That's what new JavaScript features are. They're basically additions too. So yeah, any addition breaks previous language. That's fine. That's how languages evolve. All languages evolve that way. Good or bad, I try not to. Not having a module system, but rather, cludging something from require and everything is fine and it works really well for Node.js, but it's not part of the language and a lot of tooling has problems with that and everything. I think making modules a part of I mean, is there any language other than JavaScript that doesn't have a module system? Well, C++ in some ways doesn't have a module system, C and C++, because they have this weird combination of just include, hash include and whatever. But other than that, all languages have a module system and like JavaScript wanted one. So they designed one. It's ESM, ES modules, which is as Dan Sappir said import something from whatever and export default and export const x equals whatever. It's a land and it actually, I mean, definitely broke the language, but it's become immensely popular in the frontend world. I mean, most code today, whether it's Angular, React or Vue, uses ES modules in the language. They're transpiling it and we can talk a lot about. They're definitely using ES modules.

AJ_O’NEAL: I would say ES modules are definitely a native feature of React script. I've definitely seen that. I find it to be confusing because it's, it came from Ruby and C sharp. Those were the people on the committee that wanted to break the language rather than continue with the existing standard common JS, which is a module system and does work pretty darn well, both in the browser and in node, which the import stuff has not without.

GIL_TAYAR: What, I, I, I didn't. Common test doesn't work in the browser. What, what, what happens is that bundlers like webpack, browserify, rollup, et cetera, what they do is they transpile it into one big file back again. They have no choice.

AJ_O’NEAL: No, require can work in the browser just fine.

GIL_TAYAR: Not really because require is in a synchronous, it's a synchronous feature and browser can't do HTTP in a synchronous manner.

AJ_O’NEAL: They can actually can. XML HTTP request is synchronous.

GIL_TAYAR: And it's deprecated. If you think of stretch, stretch is async only. And as far as I know, all uses of require whether webpack rollup, et cetera, I mean like a hundred percent are by bundling and not by HTTP using XML HTTP. So basically. Require and import are being transpiled. Now, I think Require is amazing. I mean, CommonJS is amazing, but it's not part of the syntax. And I think the fact that...

AJ_O’NEAL: It is part of the syntax. But I grant you the point that like predominantly in the browser, no, people are not using Require synchronously. They're using some sort of tool that gives it the ability to load asynchronously by wrapping it or perhaps converting it over to the very oddly named require.js syntax, which is actually defined, not require.

GIL_TAYAR: Yes.

AJ_O’NEAL: Yeah.

GIL_TAYAR: It was confusing back in the days.

DAN_SHAPPIR: The AMD syntax.

GIL_TAYAR: The AMD syntax, yes.

DAN_SHAPPIR: Yeah, which is a total different thing from common.js, though.

GIL_TAYAR: Not necessarily, by the way. Rollup and Parcel don't do the Webpack.

DAN_SHAPPIR: No, they do UMD, which works both ways does introduce some issues. But the way that you then import that stuff is you either, you import it either using a CommonJS Require or using RequireJS. And one of them is synchronous by definition, and the other one is asynchronous by definition. And using them both within the same project is an invitation for problems.

GIL_TAYAR: So the ESPREC people, rightly or wrongly define the import-export syntax, what is now called ES modules. And by the way, I think what the nice thing is, they took the best module system of the day, which is CommonJS, and they basically turned it into syntax. If you look at CommonJS and you look at ESM, they're basically the same, but different syntax. The idea of default export wasn't in ESM originally, wasn't in ESM modules but they took it from CommonJS, now we have export default. And named exports obviously comes from CommonJS because in CommonJS, the exports object can be like an object with like properties in it. So that's basically like named exports. So when you do import a call it a B from whatever, you're basically doing a named exports, which is similar to const a be equals require whatever. So the syntax is like amazingly similar and I think that's a good thing. I think, you know, there are quibbles on syntax and yak shaving on that bike shedding, but basically it's taking require, taking common JS and turning it into a language feature, which is great.

AJ_O’NEAL: So I...Of course, disagree on this. The primary thing that comes to mind, and a lot of people are not concerned with performance anymore. A lot of people don't care about how weighty something is, you know, bundle up six megabytes of JavaScript in a file, you know, they're cool with it. But with require, you have the option, both in node and in the browser, depending on implementation, though I grant very few implementations worked in such a way. But you have the option of lazy loading. For example, you know, it's very common to have a gigabyte of dependencies in your node modules folder. And if you try to load all of those at once, it's very common that a server might take 30 seconds, 45 seconds to fully boot up. Now granted, if somebody's writing that kind of server, they're not, you know, caring much for conservation in the first place. So kind of a bad example, but I've run into that type of issue on the Raspberry Pi. That's where even normal apps can start to become under performant or take long load times. And you could do tricks with require to, you know, put a require on the first line for something you need right away, have some sort of a knit method, let things get started, let the server get going, and then start requiring other things that are needed for background tasks and et cetera, et cetera. And the import syntax does require that you have to have everything load all at once. Now granted, you can still use require with import. There's nothing stopping you from having a require in code that has an import in it because require is well defined, it's easy to understand, it can easily be implemented and transpiled and all that. But I think, although people make the argument of tree shaking and all that with import, I don't understand why you can't do that with require, but import does have some disadvantages over require and the syntax breaking and also in that it functions, everything has to be eager loaded to work.

GIL_TAYAR: I totally agree in ES2015. In ES2018 or 2019, I don't remember, we have a way import. So you can dynamically import lazily or dynamically import whichever module you want. And you were talking about cold starting a server. If you think about it, require is totally, I mean, Node.js is a totally async environment and yet the module loading system is synchronous. That's basically crazy.

AJ_O’NEAL: Well, it's not as crazy as you think because the time... So I did performance tests on this because like I said, I had this as a real-world problem. The where you lose the time is actually when you hit VM.compile. You do not lose the time on the FS read. The FS read time is sub-millisecond. The VM compile time is where you get into multiple milliseconds.

GIL_TAYAR: Yes. And so, okay, we're going deep into the rabbit hole. Maybe we can, you know, come back to that later. Because I have answers to all that.

AJ_O’NEAL: But hey, I'm super excited to hear about this. I did not know what you said about the 2018.

GIL_TAYAR: Okay, so a weight is crazily important. Not only that, in 2020, yes, 2020, we have top level of weight, which means we can a weight import or a weight of file read on the top level and not only in an async function. But this works only if the module is an ESM module, an ES module. It cannot work in a CJS module because CJS is basically synchronous. We're getting a little bit forward here. Let's go back to the history. I really want to go back to the history. So, you know, we're in ES6 world and we have the two, you know, we have common JS and we have all those AMDs and everything and then up comes ES6 with import export, right? Now what happened are two amazingly interesting things in parallel. One is browse and they basically have nothing to do with one another ESM, natively. Okay. So today in all browsers, except IE, I don't care about IE, you can do an import from to a file that is on your server. So you can do import from dot slash my module dot JS. Okay. And what the browser will do is will HTTP get to and bring that file and use it as an ESM module. No bundling, no nothing.

DAN_SHAPPIR: Just a quick comment before you continue, because people might be running out to try it if they're not familiar with it. You do need to put scripts type="module", for that to work.

GIL_TAYAR: Yes, yes. The entry point in the HTML has to have type="module", on it. Otherwise, the script itself will be like non-module, so it can't import. Yes. Thank you, Dan.

AJ_O’NEAL: Like a red-black thing where...Red modules can import other red modules and black modules, but black modules cannot import red modules.

GIL_TAYAR: Exactly. And it's basically, and they define names for those red and black. So in ES6, you have script and module, okay? Script cannot import a module and it goes, once you're in module land, you're in module land forever. And once you're in script land, you're in script land basically forever, unless you do an awaken.

AJ_O’NEAL: But from module land you can still go to script land. You can import script from a module.

GIL_TAYAR: Not that I know. Not in the browser. In Node.js, yes. Not in the browser.

AJ_O’NEAL: Okay, so in the browser, red modules only support red modules, black modules only support black modules, and there is no intermingle.

GIL_TAYAR: Yes. And in Node.js, common.js is script and es-modules are modules.

DAN_SHAPPIR: Okay, again, to interject a quick point about no mingle. Yes, they cannot mingle, but they can obviously access each other because they both see the global browser namespace. So obviously if, if both of them put a function on window, for example, they can definitely call each other. They cannot import each other. That's the, that's the important point.

AJ_O’NEAL: So I couldn't from a Java module. No, wait, that's not right. But if we're replacing JavaScript with Java module, no? Okay, anyway. So if I were to do one of those documents, like window.document.body.addEvent or no, addElement script, blah, blah, blah, you know, that little trick you do sometimes to load a script in the background the same way that JSONP used to work, that type of trick, no worky in a JavaScript module? Sure.

DAN_SHAPPIR: That would work because both of them see both of them see the DOM. It's not that they each have any restriction with regard to access to the DOM or DOM functionality. Like I said, they even can call each other's functions because you can just put the function on the window object or whatever. What you cannot do is you cannot use ES6 import or ESM import from within a regular JavaScript code that doesn't have type equals module or was originally imported from something recursively from something that had a type of module. Likewise, from within type of module, you don't do a common JS sort of a thing.

AIMEE_KNIGHT: I'll give like a practical example maybe because we were talking about this before the call. So I'm trying to get a really old app over to at least using some modules so that I can test it more, so I can use it to test more easily. And right now, everything is just in script tags and the HTML. So what I've done is just to try to do this piecemeal is I created a couple just regular JavaScript modules like we're used to, but then what I had to do so that I could do this iteratively and not just do it all in one big fell swoop is I'm having to import some of those modules in a script tag in the HTML. And of course I had to, so that script tag, that's actually like, there's JavaScript within that script tag, and that JavaScript within the script tag, hopefully this is making some sense for people if they can like imagine this in their heads. There's actually JavaScript in that script tag inside the HTML, and that JavaScript is, it was previously just using a script tag to import the file, but I've changed that file to export whatever, I'm doing a terrible job of explaining this. I had to update the script tag from the type JavaScript to type module. But then once I did that, I'm able to import the helper module that JavaScript in my HTML is relying on the functions for. God, that was a horrible... I feel like I did a terrible job explaining that.

GIL_TAYAR: That's beautiful because you're basically using ESM the way it was meant to be as like a replacement for script. So instead of having a lot of script sources, you have one script which imports a lot of modules. This is perfect.

STEVE_EDWARDS: It made sense to me, Amy. I got it.

AIMEE_KNIGHT: Okay, and I'm trying to like, I mean, what I'm trying to do is to try to minimize, because this application really doesn't need a lot of JavaScript, but because I like testing so much, I wanna be able to test it. I don't wanna like overcomplicate things by introducing like a Bundler and all that stuff. I just wanna use like whatever I can get that comes native in browsers, which we don't have to support IE, so I was able to do this.

GIL_TAYAR: Perfect. The nice thing is that, well, if the code uses DOM, then it won't work obviously, but you can run that code today in Node.js and the import-export will work. And if you use a library like JS DOM to simulate the DOM, then the same code will work both in Node.js and in the browser. That's, for me, that's beautiful.

AIMEE_KNIGHT: One other thing I want to throw in super quickly. So, I mean, one of the issues that, you know, there's not a lot of, there's really nobody else on the team who knows JavaScript, but, you know, they were having to like fight issues of like the order of their script tags and by doing this, that's no longer a problem. So there's some benefits there as well.

GIL_TAYAR: Yep. Okay. So, uh, we were in browser land, right? And browsers got what Amy was using, which is basic module support for ES6, including a way to import and everything. But the interesting thing is, if we go back to Node.js and require, when you do a require like.slash.poo,.slash.amodule, it doesn't look for a module. It looks for a module.js and a module.json. And when you do a require loadash, then it doesn't look for the file load-. It looks for node module slash load- slash package.json and slash index.js. It has this whole algorithm where it looks for files based on your import string, on the string you pass to require. So if it's a relative file, it will look relatively. And if it's not a relative file, if it's a bare specifier, like load-dash, that's called a bare specifier, then it looks upwards in the tree for node modules, for a node modules folder with a load-dash directory.

DAN_SHAPPIR: So basically what you're saying is that even though they look like paths. What they actually are, are let's call them some sort of indices into some sort of, they're used by some sort of an algorithm that translates them into a path, but they aren't really paths in and of themselves.

GIL_TAYAR: Exactly. And whenever you do or require something, you're basically doing about five to ten file operations just to get at that file. Now, it works! in a Node.js environment because files are cheap. But in browser land, you can't do that. You can't look for a file and then look for another file because each one of those is HTTP and HTTP is not cheap. Definitely not back in the days of HTTP one, but even in HTTP two, those things are not cheap. So browsers said, okay, we're not gonna do any lookup. We're not gonna support bare specifiers at all. So you can't import from low dash. And when you're specifying a relative path, you can't do. slash foo. You have to say. slash foo.js because we're going to do an HTTP GET and get that foo.js. And we're not going to look for foo and foo.js and foo.json, whatever. Just give us the path. So browser land, and this is important for... We'll see a node. For browser land, you have to specify the whole path, including the extension. That is incredibly important. And this is why because browsers can't do HTTP like they do fast.

AJ_O’NEAL: And I'd also argue that it is best to do it that way in Node as well, because if you haven't hit an ambiguous case where it works wrong, you will eventually. And I mean, I know a lot of people are like, well, I'd rather save 10,000 keystrokes over the next five years. I'd rather write the extra 10,000 keystrokes on the.js and the.json and always be completely clear what happened with the module loading.

GIL_TAYAR: Totally agree. And if you remember back then, and when we talked about Cold Start, a lot of the time in Cold Start is wasted on looking for all those files in the node modules and in whatever.

AJ_O’NEAL: Well, not really, because you're usually gonna get it on the first hit and even on a block device, even if it's not SSD. What do you mean? No, you're not going to get it.

GIL_TAYAR: When I was at Wix, but by the way, Dan Shappir knows me at Wix. We worked on this project called Wix code and then now it's called wait for it. Wix Corvid. Yes, I know that's, uh,

DAN_SHAPPIR: Corvid, not COVID.

GIL_TAYAR: Yeah.

DAN_SHAPPIR: Important to make that distinction. Marketing is going to kill me.

CHARLES MAX_WOOD: Unfortunate at all.

DAN_SHAPPIR: Marketing is going to kill me when they hear me say that, but please go on.

GIL_TAYAR: Cold start was. Cold start was a big issue because we're basic Wix Corvid or Wix code back in the days what is the serverless solution basically. And cold start was a big thing. And what one of our developers would did was whenever we do a require, our whole thing doesn't require, what they do is they cash all the decisions by Node.js. And the next time that module runs, the next time the application runs we just patch the require to just know where the files are. That saved about 30% of the cold start time, which is a lot. Definitely not like it's not 50%, but a big part of the cold start time in a Node.js application is spent on all those little searches. But definitely, you and the Node.js modules team are on the same page in terms of let's be more specific instead of what the file path is. Okay, so that's what happened in browser. On the node land, something interesting happened. Node started getting more and more NPM modules, NPM started to grow. And the browser, the front end people remember that's before bundling. They looked at the NPM registry and said, oh, there's a really nice things we can use there. But they couldn't use it because they were using AMD and require JS, which are like these old module systems and not common JS. So then this guy came along and wrote Browzerify. That was the first bundler. What Browzerify did is it took an npm package with all those requires transpiled all those requires and bundled them into one big file just like Webpack does. That was before Webpack. So now you can use those npm packages that were meant for NodeJS you can use them in browser land. You can use CommonJS in browser land. And Browserify basically did a revolution in front-end land. We don't remember that today because everybody's using bundlers.

DAN_SHAPPIR: Yeah, that's when we went from having kilobytes of JavaScript download to megabytes of JavaScript download. Thank you Browserify and Webpack.

AJ_O’NEAL: Well, a lot of that is because the way that it bundled it was not very smart. So say for example, you did something that used buffer, which is everything in Node. Rather than using an implementation that would take, you know, like four or five lines of code, which you can do using A to B and B to A and escape and URI and code and...Like you can, you can get this to happen using things that are natively available in the browser, but that's not the way that it got packed and transpiled. I don't know why they made the choices that they did, but they kind of, instead of using browser functions, they kind of use like pure JavaScript to do some of these implementations. So they, they re-implemented the wheel and then some on a lot of stuff and buffer is one of those modules where it was a little overzealous, I believe, and that it kind of like even copied the bugs of buffer, which are not, I mean, from my perspective, if you're trying to get something to run in the browser, it would be acceptable that it fail if you're using like an obscure feature that is deprecated or whatever. But like everything about buffer. Every little nuance detail about buffer was replicated in like this pure JavaScript without using any of the native browser things that had been there since like, you know 1998 and

DAN_SHAPPIR: I but I think you're going down down I You're right, but I think you're going down the wrong rabbit hole here I think that the main issue is the developers tend to just use the path of least resistance whenever they're developing anything. And if I know that Moment.js happens to do what I need to do in terms of working with date and time, and it's so easy now thanks to first Browserify and now Webpack to bundle in Moment.js, then I will bundle in Moment.js. And because I'm not a specialist about how to configure NPM, I end up bundling five different versions of Moment.js into my application and before I know it my download size is 600 kilobytes. Even though my own code...

AJ_O’NEAL: That's a pretty lean sight by today's standards.

DAN_SHAPPIR: Yeah, even though my own code is only, I don't know, 20 kilobytes of minified code because, you know, I've never actually wrote more than that. But again, I think we're kind of straying away from the main topic here.

GIL_TAYAR: Right, because browser-ified tried to do two things emulate node and bundle. Webpack came and basically killed Browserify because it tried to do only one thing, bundle. It didn't care about node. Which makes sense historically because back in the days when Browserify started, all the NPM packages were node. Now in the Webpack days and roll up in parcel, like I'm guessing that 90% are front end in NPM. So I think what you're saying is totally true, but the reason that happened was historic. Browserify is basically not really used anymore, so it's a more point. But the interesting thing is that the front-end people started using CommonJS. And not only that, they used the CommonJS node resolution module. So they didn't write foo.js like the browsers. They just wrote foo and load- and use bare specifiers, because that is how NodeJS works. This is how CommonJS works. And then came the webpacks of the world and the babels of the world, and they didn't want to use require they wanted to use ES module syntax. So the web packs of the world and the webels of the world just said, hey, why not ditch require and just use the import-export syntax and still bundle. And this is what we have in the browser land, in front end land today, not in browser land. Front-end land uses the import syntax, but uses the resolution module of common JS. So when you're doing import load dash, the bundler goes and looks at node modules and all that package JSON and looks at everything to find it just like Node.js would. And when you're writing import from foo,.slash foo, it goes and looks for.slash foo.js. So we have frontend land using his modules, but with node resolution, with finding modules the way node. And we have the browser land not doing that. So Frontend land is using bundlers but cannot migrate to browser land and they can only bundle because their module resolution is different. So this is like ironical in that basically the frontend people implemented ES modules a bit too quickly in some ways. They did it before browsers did and when browsers did it like the right way. There's no going back. Well, not yet. We'll talk about how this will happen. But we basically now have three module systems, Common.js and Node.js, transpiled ES6 modules that work a bit like Common.js, and browser-landed ES modules, which just use relative paths.

Right now, many of you are stuck at home, but eventually everything will open up. All right, listeners, let me ask you a question. Wouldn't you rather work from home instead of a cubicle or a noisy open office? Need to negotiate with your team and convince them to let you do it? Well, I have the perfect book for you. It's by my friend, Will Gantt. It's called Remote Work, Get a Job or Make a Career Working from Home. He's a proven author, software developer and professional consultant with over 20 years of experience in a variety of roles. And now he wants to share his trade secrets with you. In remote work, you'll discover how to save more time, money, and mental energy each year. How working remotely can give you and your company a competitive edge in the market managing your physical health, mental health, career goals and relationships. You'll also get the ultimate list of tools and resources to help you transition into working remotely and much more. This is the perfect time to test out if working remotely is for you. And if you enjoy the freedom of working anywhere you want, then you can pick up your copy of remote work on Amazon today, or click the link below in the show description.

GIL_TAYAR: Now comes Node.js native modules and introduces a fourth option. Remember we have browser language that uses relative paths, but you have to specify the whole path. We have require, we have common.js which uses require and where you don't have to specify the whole path and we have transpiled ES6 which is used front end lines in bundlers which uses the syntax of ES6 but not the module resolution so you don't have to specify the whole path. Now come node-esm. One of the prime directives of the designers of node-es modules, when I'm talking node-es modules. They wanted to be as browser compatible as they could. And that is an important thing. What did that mean? They mean that just like CJ said, AJ, sorry, they did not accept Foo. They had to have Foo.js,.slash Foo.js. So in ESM land, in Node, you have to, when you're importing, you have to import.slash Foo.js. and not. slash full. So that's one big difference. And a prime directive, that is one of the main reasons Node.SM is so different from CommonJS in Node.js. So that's like a bit of a history of the order of things and why things happen. I have a lot more to talk about on the Node.SM side, but if you have any questions up to now.

DAN_SHAPPIR: Aside from your describing some things that I also discovered for myself, some of them the hard way, other than that, it's pretty clear to me.

GIL_TAYAR: Great. So basically, that was Node's prime directive. Let us be as browser compatible as possible. But they had a problem. They had a big problem because browsers, remember we have script and module, browsers have that distinction between script and module. So we talked about the fact that a script can't do an import, but there are other differences between script and module. For example, a module is always strict mode. It can't be sloppy. If you know the distinction between strict mode and sloppy mode in JavaScript.

DAN_SHAPPIR: You're referring to use strict, right?

GIL_TAYAR: Yes, use strict, exactly. So a module is always use strict, and I think you can't go back. So you can't do use sloppy.

DAN_SHAPPIR: You cannot, there is no way to to undo a use strict within a block.

GIL_TAYAR: Moreover, this means that for example, global this, if you use this in a global scope, it's undefined in a module. Whereas if you use this in a global scope in a script, it points to something in the window object and in browsers and in Node.js, I don't even remember what.

AJ_O’NEAL: So do modules actually define the global object or is that still something where you have to do like, window.function, eval, whatever, whatever.

GIL_TAYAR: ES2020, which is implemented in, I think, all the browsers and in Node.js, defined this horribly named thing called global this. Global this is the new global window. It works both in Node and in all the browsers.

DAN_SHAPPIR: It's not a global window, it's the global object or the global context.

GIL_TAYAR: Yeah, but it's basically just like window in the browser and global in the node.

DAN_SHAPPIR: In the browser it's window, exactly.

AJ_O’NEAL: So now we've got three globals in node. We've got global, uppercase global, and global this. And I bet they all have different properties on them.

GIL_TAYAR: No, I think they're the same. I didn't know about uppercase global. Wow, that's new, interesting. But yeah, just like in browser land, you have window and you have global this. But they wanted to use global. They really wanted to use nodes global, but it didn't work for other reasons.

AJ_O’NEAL: So they invented this horribly named global this because like one out of every thousand websites had a variable called global, but only one out of 10 million websites had a variable called global this

GIL_TAYAR: exactly something like that. Probably. So the browser's know understand the description between script and module and the ESM designers and no just wanted the same thing because they wanted to be as browser compatible as possible in node land. So they defined CJ as a script, which it is. So it's sloppy by default. And they decided that ES modules will be, well, modules. But that's a problem because now when node has to parse a file, it needs to know whether it's parsing a module or a script because the parse is different between the two. Now comes the controversial part, the node-y assembly.

DAN_SHAPPIR: Just to give an example of where the parse is different for people who don't remember, the width keyword is supported in script and is not supported in modules. So that's just an additional example. So yes, parsing needs to be different between the two.

GIL_TAYAR: Wow, I didn't know that about width, but yes.

AJ_O’NEAL: And there's certain errors that in sloppy mode. It'll do it PHP style where it just encounters the error, says nothing and keeps going to the next line. And in strict mode, those errors become hard errors that actually get thrown. And I think that may originate from like ES1 or so back before try catch was defined. I'm not sure about that, don't quote me on it.

GIL_TAYAR: We'll send Brendan and Ike along your way. So they needed a way to figure out when importing or requiring a file, whether it's like module or script. And they decided on a weird way. I think it's the right way, but it is very controversial. They decided that it's defined by extension. So JS is script, it's CJS, and MJS, what I call Michael Jackson script, or module JavaScript is ESM. That is the birth of the MJS extension. And people got crazy about this on the internet. I mean, it was a very controversial decision. People...

JavaScript Jabber JSJ 434: Understanding and Using ES Modules in Node with Gil Tayar
JavaScript Jabber 007 JSJ Online Resources for Javascript Developers
JavaScript Jabber 005 JSJ Javascript Objects
JavaScript Jabber JSJ 329: Promises, Promise.finally(), and Async/await with Valeri Karpov
JavaScript Jabber 004 JSJ Backbone.js with Jeremy Ashkenas
JavaScript Jabber 003 JSJ Build Tools
JavaScript Jabber 021 JSJ Weapons of Choice
JavaScript Jabber JSJ 280: Stackblitz with Eric Simons and Albert Pai
JavaScript Jabber JSJ 328: Functional Programming with Ramda with Christine Legge
JavaScript Jabber 025 JSJ Require.js with James Burke
JavaScript Jabber JSJ 358: Pickle.js, Tooling, and Developer Happiness with Anatoliy Zaslavskiy
JavaScript Jabber JSJ 326: Conversation with Ember co-creator Tom Dale on Ember 3.0 and the future of Ember
JavaScript Jabber JSJ 413: JavaScript Jabber at RxJs Live
JavaScript Jabber 064 JSJ Ember Tools with Ryan Florence
JavaScript Jabber JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank
JavaScript Jabber 041 JSJ Single Page Applications
JavaScript Jabber Simplifying Full-Stack Dev with the "Boring JavaScript Stack" and Sails Framework - JSJ 621
JavaScript Jabber Mastering Back-End Functionalities and Development with AWS Amplify - JSJ 619
JavaScript Jabber JSJ 324: with Kent Beck
JavaScript Jabber Exploring AI Impact on Code Generation and Quality Metrics - JSJ 618
JavaScript Jabber Unlocking Vue and Nuxt Potential: New Tools, Best Practices, and more - JSJ 652
JavaScript Jabber Inside the World of React: Server Components, Unidirectional Data Flow, and Frameworks - JSJ 617
JavaScript Jabber JSJ 321: Babel and Open Source Software with Henry Zhu
JavaScript Jabber 073 JSJ React with Pete Hunt and Jordan Walke
JavaScript Jabber Iterating on Open Source - JSJ 615
JavaScript Jabber JSJ 320: Error Tracking and Troubleshooting Workflows with David Cramer LIVE at Microsoft Build
JavaScript Jabber Dev Dilemmas: TypeScript Triumphs and Quirks of JavaScript Arrays - JSJ 614
JavaScript Jabber Optimizing SQL and ORM Practices for High-Performance Applications - JSJ 650
JavaScript Jabber JSJ 339: Node.js In Motion Live Video Course from Manning with PJ Evans
JavaScript Jabber The Future of Authentication in JavaScript: An Inside Look into Passport JS with Jared Hanson - JSJ 613
JavaScript Jabber The Rise of No Code: A Deep Dive into Toddle's Revolutionary Web App Platform - JSJ 612
JavaScript Jabber Bit: Paving the Way for Component Management - JSJ 610
JavaScript Jabber JSJ 318: Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari LIVE at Microsoft Build
JavaScript Jabber Next-Level Web Performance with Patrick Meenan - JSJ 608
JavaScript Jabber Partytown with Adam Bradley - JSJ 550
JavaScript Jabber Mastering ORM with TypeScript - JSJ 606
JavaScript Jabber JSJ 314: Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver LIVE at Microsoft Build
JavaScript Jabber What has Changed with htmx 2.0 with Carson Gross - JSJ 604
JavaScript Jabber Discovering ElysiaJS and The Duality of TypeScript and JavaScript - JSJ 609
JavaScript Jabber View Transitions API with Noam Rosenthal - JSJ 602
JavaScript Jabber From Learning New Languages to Learning New Technologies - JSJ 629
JavaScript Jabber Accessibility in Component Libraries with Maya Shavin - JSJ 601
JavaScript Jabber 131 JSJ Conferences & Meetups with Dave Nugent
JavaScript Jabber JSJ 270 The Complete Software Developers Career Guide with John Sonmez
JavaScript Jabber Unraveling the CSS Revolution, Podcast Growth Tactics, and More - JSJ 600
JavaScript Jabber Redwood JS in Action with Tom Preston-Werner - JSJ 599
JavaScript Jabber Exploring the True Measure of User Experience: Core Web Vitals & Beyond - JSJ 598
JavaScript Jabber JSJ 308: D3.js with Ben Clinkinbeard
JavaScript Jabber 217 JSJ The Now Project with Guillermo Rauch
JavaScript Jabber 226 JSJ Test Doubles with Justin Searls
JavaScript Jabber 208 JSJ MS Office with Jeremy Thake
JavaScript Jabber What if your JavaScript Validations Looked like Tests? - JSJ 597
JavaScript Jabber Embracing Web Standards with Owen Buckley - JSJ 626
JavaScript Jabber Is JavaScript on the Backend a Mistake? - JSJ 596
JavaScript Jabber JSJ 374: CosmosDB with Steve Faulkner LIVE at Microsoft BUILD
JavaScript Jabber Why Should You Get Into The Web3 World - JSJ 595
JavaScript Jabber JSJ 307: Apollo with Peggy Rayzis
JavaScript Jabber Svelte 5: Compiler, Signals, and Web App Performance - JSJ 627
JavaScript Jabber JSJ 305: Continuous Integration, Processes, and DangerJS with Orta Therox
JavaScript Jabber The Evolution of Qwik - JSJ 594
JavaScript Jabber 092 JSJ The MEAN Stack with Ward Bell and Valeri Karpov
JavaScript Jabber JSJ 402: SEO for Developers with Vitali Zaidman
JavaScript Jabber Introducing The B2B SaaS Starter Kit - JSJ 593
JavaScript Jabber The CSS Universe with Austin Gil - JSJ 592
JavaScript Jabber 189 JSJ PureScript with John A. De Goes and Phil Freeman
JavaScript Jabber Progressive Enhancement with Elliott Johnson - JSJ 591
JavaScript Jabber Things Coming Down the Pipe From TC39 - JSJ 590
JavaScript Jabber JSJ 303: Test Coverage Tools with Ben Coe, Aaron Abramov, and Issac Schleuter
JavaScript Jabber Million.js with Aiden Bai and Tobiloba Adedeji - JSJ 589
JavaScript Jabber 121 JSJ Broccoli.js with Jo Liss
JavaScript Jabber How to Build Peer-to-Peer Mobile and Desktop Apps with Socket Supply - JSJ 588
JavaScript Jabber What It Takes To Be A Web Developer: Part 2 - JSJ 587
JavaScript Jabber Streamlining AI Integration - JSJ 616
JavaScript Jabber What It Takes To Be A Web Developer: Part 1 - JSJ 586
JavaScript Jabber Defining and Learning Web Fundamentals - JSJ 585
JavaScript Jabber Find Out More About Barry Pollard - BONUS
JavaScript Jabber React Server Components: Part 2- JSJ 583
JavaScript Jabber React Server Components: Part 1 - JSJ 582
JavaScript Jabber 151 JSJ Getting Started with a Career in Web Development with Tyler McGinnis
JavaScript Jabber Making AI Accessible for Developers - JSJ 641
JavaScript Jabber Overcoming JavaScript Load Issues: Import Maps and Performance Enhancements - JSJ 643
JavaScript Jabber JSJ 435: Form.io with Travis Tidwell
JavaScript Jabber JSJ 298: Angular, Vue and TypeScript with John Papa
JavaScript Jabber Find Out More About Brad Westfall - BONUS
JavaScript Jabber JSJ 248 Reactive Programming and RxJS with Ben Lesh
JavaScript Jabber 169 JSJ Property-based Testing (QuickCheck) with Zach Kessin
JavaScript Jabber SolidStart with Ryan Carniato - JSJ 581
JavaScript Jabber JSJ 438: You Don't Know JS Yet with Kyle Simpson (SPECIAL ANNOUNCEMENT at the End)
JavaScript Jabber Cross Platform App Development with Simon Grimm - JSJ 580
JavaScript Jabber JSJ 297: Scrollytelling with Russell Goldenberg and Adam Pearce
JavaScript Jabber 216 JSJ Angular with Rob Wormald Live from Microsoft Build 2016
JavaScript Jabber JSJ 296: Changes in React and the license with Azat Mardan
JavaScript Jabber 134 JSJ Quilljs with Jason Chen
JavaScript Jabber 074 JSJ Grunt with Ben Alman
JavaScript Jabber JSJ 311: Securing Express Apps with Helmet.js with Evan Hahn
JavaScript Jabber JSJ 288: TypeScript with Amanda Silver
JavaScript Jabber 173 JSJ Online Learning with Gregg Pollack
JavaScript Jabber Simplifying Development with Deno - JSJ 625
JavaScript Jabber 194 JSJ JavaScript Tools Fatigue
JavaScript Jabber 196 JSJ Tabris.js with Jochen Krause and Ian Bull
JavaScript Jabber 205 JSJ Shasta with Eric Schoffstall
JavaScript Jabber 006 JSJ Chrome Dev Tools with Paul Irish
JavaScript Jabber 211 JSJ Ember and EmberConf with Michael North
JavaScript Jabber 223 JSJ WebStorm with Dennis Ushakov
JavaScript Jabber 197 JSJ Auth0 with Kassandra Perch
JavaScript Jabber JSJ 466: Infrastructure as Code with Christian Nunciato
JavaScript Jabber JSJ 467: The Joy of JavaScript with Luis Atencio
JavaScript Jabber JSJ 286: Creating a CSS-in-JS Library from Scratch and Emotion with Kye Hohenberger
JavaScript Jabber Being a New Developer with Diego Moura - JSJ 553
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber JSJ 432: Internet of Things (IoT) with Joe Karlsson
JavaScript Jabber JSJ BONUS: Cloud Services and Manifold with Matthew Creager and Peter Cho
JavaScript Jabber Understanding, Confidence, and Humility in Web development - JSJ 655
JavaScript Jabber JSJ 283: A/B Testing with Nick Disabato
JavaScript Jabber JSJ 348: EnactJS with Ryan Duffy
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber Stimulus and Turbo in Web Development - JSJ 656
JavaScript Jabber Supply Chain Security with Stephen Chin - BONUS
JavaScript Jabber Simplifying Slinkity with Anthony Campolo
JavaScript Jabber JSJ 437: Inside the Brave Browser with Jonathan Sampson
JavaScript Jabber JSJ 443: All About InertiaJS with Jonathan Reinink
JavaScript Jabber JSJ 289: Visual Studio Code and Live Sharing with Chris Dias and PJ Meyer LIVE at Microsoft Connect 2017
JavaScript Jabber JSJ 245 Styled Components and react-boilerplate with Max Stoiber
JavaScript Jabber JSJ 451: Are Software Bugs Inevitable with Ran Levi
JavaScript Jabber Qwik with Misko Hevery - JSJ 549
JavaScript Jabber JSJ 442: Breaking Into Tech with Danny Thompson
JavaScript Jabber JSJ 279: ES Modules in Node Today! with John-David Dalton
JavaScript Jabber Dan Shappir's Failed Predictions - JSJ 552
JavaScript Jabber 102 JSJ Angular and Open Source Projects with Brad Green
JavaScript Jabber 100 JSJ Centennial Episode Celebration
JavaScript Jabber JSJ 275: Zones in Node with Austin McDaniel
JavaScript Jabber 209 JSJ TypeScript with Anders Hejlsberg
JavaScript Jabber JSJ 274: Amazon Voice Services and Echo Skills with Terrance Smith
JavaScript Jabber How To Recession Proof Your Job - BONUS
JavaScript Jabber All Things TypeScript with Maina Wycliffe - JSJ 559
JavaScript Jabber 018 JSJ Agile Development
JavaScript Jabber JSJ 273: Live to Code, Don't Code to Live with 2 Frugal Dudes Sean Merron and Kevin Griffin
JavaScript Jabber Vue Courses, Top End Devs, and More... Oh, My! - JSJ 546
JavaScript Jabber JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman
JavaScript Jabber JSJ 272: Functional Programming and ClojureScript with Eric Normand
JavaScript Jabber 043 JSJ Sinon.JS
JavaScript Jabber JSJ 271: SharePoint Extensions in JavaScript with Mike Ammerlaan and Vesa Juvonen
JavaScript Jabber 065 JSJ Build Tools with Adam Hawkins
JavaScript Jabber 046 JSJ Staying Current
JavaScript Jabber JSJ 430: Learning JavaScript in 2020 with Matt Crook
JavaScript Jabber 026 JSJ Code Organization and Reuse
JavaScript Jabber 084 JSJ Node with Mikeal Rogers
JavaScript Jabber 012 JSJ Design Patterns in JavaScript with Addy Osmani
JavaScript Jabber Women on Stage and in Tech with Moran Weber - JSJ 483
JavaScript Jabber JSJ 301: CSS Grids: The Future of Frontend Layout with Dave Geddes
JavaScript Jabber JavaScript and IoT with Nick Hehr and Peter Hoddie - JSJ 545
JavaScript Jabber Even More JavaScript Features You Should Avoid - JSJ 547
JavaScript Jabber 161 JSJ Rust with David Herman
JavaScript Jabber JSJ 266 NPM 5.0 with Rebecca Turner
JavaScript Jabber JSJ 343: The Power of Progressive Enhancement with Andy Bell
JavaScript Jabber 165 JSJ ShopTalk with Chris Coyier and Dave Rupert
JavaScript Jabber 080 JSJ - Impact.js with Dominic Szablewski
JavaScript Jabber JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code
JavaScript Jabber BONUS: Start Building Video Games with Jason Weimann
JavaScript Jabber JSJ 263 Moving from Node.js to .NET and Raygun.io with John-Daniel Trask
JavaScript Jabber JSJ 429: Learning about Postman with Joyce Lin
JavaScript Jabber 079 Lo-Dash with John-David Dalton
JavaScript Jabber 070 JSJ Book Club: JavaScript Allongé with Reginald Braithwaite
JavaScript Jabber 094 JSJ BonsaiJS with Tobi Reiss
JavaScript Jabber JSJ 261 HTTP 2 with Surma
JavaScript Jabber Mentorship in Tech: Balancing Professionalism and Friendship for Maximum Growth and Accountability - JSJ 649
JavaScript Jabber 101 JSJ js-git with Tim Caswell
JavaScript Jabber JSJ 260 Practical JavaScript with Gordon Zhu
JavaScript Jabber 108 JSJ AngularJS with Igor Minar
JavaScript Jabber 105 JSJ JSConf and Organizing Conferences with Chris Williams
JavaScript Jabber JSJ 349: Agile Development - The Technical Side with James Shore
JavaScript Jabber 109 JSJ Dependency Injection in JavaScript with Vojta Jína & Misko Hevery
JavaScript Jabber JSJ 397: Design Systems with Kaelig Deloumeau-Prigent
JavaScript Jabber JSJ 259 Clean Code JavaScript with Ryan McDermott
JavaScript Jabber JSJ 258 Development in a Public Institution with Shawn Clabough
JavaScript Jabber 119 JSJ Chrome Apps with Joe Marini
JavaScript Jabber The State of WASM - JSJ 560
JavaScript Jabber Sorting through the Script (AJ vs. Dan Shappir) - JSJ 519
JavaScript Jabber 122 JSJ Socket.IO with Guillermo Rauch
JavaScript Jabber Don't Let These Things Keep You From Podcasting - BONUS
JavaScript Jabber JSJ 388: Functional Programming with Brian Lonsdorf
JavaScript Jabber 107 JSJ ClojureScript & Om with David Nolen
JavaScript Jabber JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler
JavaScript Jabber JSJ 257 Graphcool with Johannes Schickling
JavaScript Jabber 129 JSJ BaaS with Ryan Done
JavaScript Jabber JSJ 425: The Evolution of JavaScript
JavaScript Jabber 132 JSJ MV Frameworks with Craig McKeachie
JavaScript Jabber Sentry's Impact on Web Vitals Understanding - JSJ 632
JavaScript Jabber 137 JSJ &yet with Henrik Joreteg and Phil Roberts
JavaScript Jabber 086 JSJ Ember.js & Discourse with Robin Ward
JavaScript Jabber Beyond JavaScript: Master TypeScript at Scale at SquiggleConf - JSJ 646
JavaScript Jabber Web3 with Nik Kalyani - JSJ 630
JavaScript Jabber Mastering Browser Caching with Vitali Zaidman - JSJ 490
JavaScript Jabber JSJ 256 Wordpress and Wordpress API for JavaScript Developers with Roy Sivan
JavaScript Jabber JSJ 428: The Alphabet Soup of Performance Measurements
JavaScript Jabber 164 JSJ Rendr with Spike Brehm
JavaScript Jabber 155 JSJ Webtorrent with Feross Aboukhadijeh
JavaScript Jabber 024 JSJ Strata.js with Michael Jackson
JavaScript Jabber 160 JSJ Stormpath with Robert Damphousse
JavaScript Jabber 158 JSJ Roots with Jeff Escalante
JavaScript Jabber 159 JSJ Why JavaScript Is Hard
JavaScript Jabber Preventing Fraud on Your Payment Website - JSJ 534
JavaScript Jabber Data Wrangling in JavaScript with Ashley Davis - JSJ 484
JavaScript Jabber 171 JSJ Babel with Sebastian McKenzie
JavaScript Jabber JSJ 431: Personal Branding for Developers with Morad Stern
JavaScript Jabber JSJ 255 Docker for Developers with Derick Bailey
JavaScript Jabber JSJ 389: What Makes a 10x Engineer?
JavaScript Jabber JSJ 254 Contributor Days with Tracy Lee
JavaScript Jabber 207 JSJ Growing Happy Developers with Marcus Blankenship
JavaScript Jabber JSJ Special Episode: Azure with Jonathan Carter
JavaScript Jabber Splatty-doo and Other JavaScript Features You Should Avoid - JSJ 543
JavaScript Jabber JSJ 252 The 20th Anniversary of Visual Studio with Bowden Kelly
JavaScript Jabber 142 JSJ Share.js with Joseph Gentle
JavaScript Jabber Becoming the Go-To Person in Your Technology Area - BONUS
JavaScript Jabber 190 JSJ Web Performance Part 2 with Nik Molnar
JavaScript Jabber 045 JSJ jQuery
JavaScript Jabber JSJ 251 InfoSec for Web Developers with Kim Carter
JavaScript Jabber JSJ 384: FaunaDB: Support for GraphQL and Serverless Development with Evan Weaver
JavaScript Jabber 222 JSJ Nodal with Keith Horwood
JavaScript Jabber JSJ 449: The Things Every JavaScript Developer Must Know
JavaScript Jabber 200 JSJ EPISODE 200!!!
JavaScript Jabber JSJ 249 Loading and Optimizing Web Applications with Sam Saccone and Jeff Cross
JavaScript Jabber JSJ 246 GraphQL and Apollo with Uri Goldshtein
JavaScript Jabber 128 JSJ Famo.us with Steve Newcomb
JavaScript Jabber JSJ 327: "Greenlock and LetsEncrypt" with AJ O'Neal
JavaScript Jabber Typing Without Transpilation - The Beauty of JSDoc - JSJ 489
JavaScript Jabber 244 JSJ Visual Studio with Sam Guckenheimer
JavaScript Jabber Can JAMstack do REAL Web Apps? with James Q Quick - JSJ 517
JavaScript Jabber 036 JSJ DOM Rendering and Manipulating
JavaScript Jabber 112 JSJ Refactoring JavaScript Apps Into a Framework with Brandon Hays
JavaScript Jabber 227 JSJ Fostering Community Through React with Benjamin Dunphy, Berkeley Martinez, and Ian Sinnott
JavaScript Jabber JSJ 304: React: The Big Picture
JavaScript Jabber 243 JSJ Immutable.js with Lee Byron
JavaScript Jabber JSJ 401: Hasura with Tanmai Gopal
JavaScript Jabber JSJ 345: Azure Devops with Donovan Brown LIVE at Microsoft Ignite
JavaScript Jabber 242 JSJ Visual Studio and .NET with Maria Naggaga
JavaScript Jabber 066 JSJ Transitioning to JavaScript
JavaScript Jabber 235 JSJ JavaScript Devops and Tools with Donovan Brown and Jordan Matthiesen
JavaScript Jabber RPC Resurgence: From Client-Server Applications to Next.js and Meta Frameworks - JSJ 607
JavaScript Jabber 241 JSJ Microsoft Docs with Dan Fernandez
JavaScript Jabber The MaxCoders Guide To Finding Your Dream Developer Job
JavaScript Jabber 240 JSJ Visual Studio Code with Chris Dias
JavaScript Jabber TC39 and Upcoming Proposals for ECMAScript (PART 2) - JSJ 533
JavaScript Jabber A Deep Dive Into Some Nooks and Crannies of JavaScript - JSJ 535
JavaScript Jabber 239 JSJ Vets Who Code with Jerome Hardaway
JavaScript Jabber JSJ BONUS: Web Apps on Linux with Jeremy Likness and Michael Crump
JavaScript Jabber 230 JSJ Node at Capital One with Azat Mardan
JavaScript Jabber 236 JSJ Interview with Mads Kristensen from Microsoft Ignite
JavaScript Jabber Data Oriented Programming with Yehonathan Sharvit - JSJ 481
JavaScript Jabber JSJ 478: Browser Standards Rampage: Can We Have Nice Things?
JavaScript Jabber JSJ 269 Reusable React and JavaScript Components with Cory House
JavaScript Jabber Building a Custom Front-end Framework - JSJ 633
JavaScript Jabber 229 JSJ Elm with Richard Feldman
JavaScript Jabber Creating Your Community with Brett Haralson - JAVASCRIPT 515
JavaScript Jabber 206 JSJ PostCSS with Ben Briggs
JavaScript Jabber 224 JSJ Cypress.js with Brian Mann
JavaScript Jabber JSJ 459: Codota Tabnine and the Rise of Ai-powered Developer Tooling with Kyle Simpson PT 2
JavaScript Jabber Power Tips for Browser Dev-Tools with Craig Buckler - JSJ 492
JavaScript Jabber JSJ 334: “Web Performance API” with Dan Shappir
JavaScript Jabber Things JavaScript Developers Should Know, Part 2 - JSJ 485
JavaScript Jabber JSJ 476: Understanding Search Engines and SEO (for devs) - Part 1
JavaScript Jabber 215 JSJ ChakraCode with Guarav Seth Live from Microsoft Build 2016
JavaScript Jabber 214 JSJ Pebble with Heiko Behrens and François Baldassari
JavaScript Jabber Front End Architecture - JSJ 522
JavaScript Jabber 089 JSJ The Node Security Project with Adam Baldwin
JavaScript Jabber BONUS: How to Crush Your Biggest Goals in 2021
JavaScript Jabber 210 JSJ The 80/20 Guide to ES2015 Generators with Valeri Karpov
JavaScript Jabber 192 JSJ IoT with Peter Hoddie
JavaScript Jabber 199 JSJ Visual Studio Code with Chris Dias and Erich Gamma
JavaScript Jabber 204 JSJ Free Code Camp with Quincy Larson
JavaScript Jabber JSJ 312: Hygen with Dotan Nahum
JavaScript Jabber 203 JSJ Aurelia with Rob Eisenberg
JavaScript Jabber 202 JSJ DoneJS + CanJS with Justin Meyer
JavaScript Jabber 111 JSJ The Ember.js Project with Erik Bryn
JavaScript Jabber 201 JSJ Security with Troy Hunt
JavaScript Jabber Unveiling Chrome DevTools: Network Monitoring, Cache Debugging, and Beyond - JSJ 623
JavaScript Jabber JSJ 356: Build Websites Like It's 2005 with Keith Cirkel
JavaScript Jabber 198 JSJ 2015 Recap and 2016 Predictions
JavaScript Jabber Embracing Angular's Evolution with Santosh Yadav - JSJ 631
JavaScript Jabber JSJ BONUS EPISODE: Observables and RxJS Live with Aaron Frost
JavaScript Jabber JSJ 319: Winamp2-js with Jordan Eldredge
JavaScript Jabber Bun.js with Jarred Sumner - JSJ 584
JavaScript Jabber Practical Strategies for Web Optimization: Using Chrome DevTools - JSJ 635
JavaScript Jabber 195 JSJ Rollup.js with Rich Harris and Oskar Segersvärd
JavaScript Jabber Stories From The Trenches - JSJ 556
JavaScript Jabber 225 JSJ Functional Programming with John A. De Goes
JavaScript Jabber An Unconventional Journey into Coding ft. Sam Sycamore - JSJ 496
JavaScript Jabber 193 JSJ Electron with Jessica Lord and Amy Palamountain
JavaScript Jabber 191 JSJ Stripe with Craig McKeachie
JavaScript Jabber 179 JSJ redux and React with Dan Abramov
JavaScript Jabber OAuth Explained - JSJ 523
JavaScript Jabber JSJ 290: Open Source Software with Dirk Hohndel - VMWare Chief Open Source Officer
JavaScript Jabber 186 JSJ NativeScript with TJ VanToll and Burke Holland
JavaScript Jabber Hydrogen and Oxygen - JSJ 539
JavaScript Jabber 183 JSJ Should I go to college?
JavaScript Jabber Building and Distributing PWAs: Tools, Techniques, and Insights - JSJ 638
JavaScript Jabber 182 JSJ RxJS with Matthew Podwysocki
JavaScript Jabber 181 JSJ The Evolution of Flux Libraries with Andrew Clark and Dan Abramov
JavaScript Jabber Do You Have Dev FOMO? ft. Yoav Ganbar - JSJ 510
JavaScript Jabber 178 JSJ Tech Education and The Business of Running Front End Masters with Marc Grabanski
JavaScript Jabber 177 JSJ UI Validation with Oren Rubin
JavaScript Jabber 175 JSJ Elm with Evan Czaplicki and Richard Feldman
JavaScript Jabber JSJ 469: The Case for JavaScript Iterators and Generators, part 2
JavaScript Jabber 174 JSJ npm 3 with Rebecca Turner and Forrest Norvell
JavaScript Jabber 232 JSJ GunDB and Databases with Mark Nadal
JavaScript Jabber 172 JSJ NodeSchool with Jason Rhodes
JavaScript Jabber High-Performance Networking: Key Resources and Tools for Web Developers - JSJ 637
JavaScript Jabber 168 JSJ The Future of JavaScript with Jafar Husain
JavaScript Jabber JSJ 268 Building Microsoft Office Extensions with JavaScript with Tristan Davis and Sean Laberee
JavaScript Jabber JSJ 306: The Framework Summit with Joe Eames
JavaScript Jabber 167 JSJ TypeScript and Angular with Jonathan Turner and Alex Eagle
JavaScript Jabber 014 JSJ SVG and Data Visualization with Chris Bannon
JavaScript Jabber TC39 and Upcoming Proposals for ECMAScript (PART 1) - JSJ 532
JavaScript Jabber JSJ 477: Understanding Search Engines and SEO (for devs) - Part 2
JavaScript Jabber 166 JSJ New Relic with Wraithan and Ben Weintraub
JavaScript Jabber JSJ 316: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build
JavaScript Jabber 038 JSJ Jasmine with Justin Searls
JavaScript Jabber BONUS: Relationships Matter Most
JavaScript Jabber 047 JSJ Specialized vs Monolithic with James Halliday and Tom Dale
JavaScript Jabber 042 JSJ CSS and CSS Superset Languages
JavaScript Jabber 163 JSJ Flow with Jeff Morrison and Avik Chaudhuri
JavaScript Jabber 176 JSJ RethinkDB with Slava Akhmechet
JavaScript Jabber 153 JSJ Careers for Junior Developers with Aimee Knight
JavaScript Jabber JSJ 322: Building SharePoint Extensions with JavaScript with Vesa Juvonen LIVE at Microsoft Build
JavaScript Jabber 157 Moving Your Rendering Engine to React with Amit Kaufman and Avi Marcus
JavaScript Jabber 154 JSJ Raygun.io Error Reporting and Workflow with John-Daniel Trask
JavaScript Jabber JSJ 427: How to Start a Side Hustle as a Programmer with Mani Vaya
JavaScript Jabber 152 JSJ GraphQL and Relay with Nick Schrock and Joe Savona
JavaScript Jabber MeteorJS ft. Filipe Névola - JSJ 506
JavaScript Jabber 150 JSJ OIMs with Richard Kennard, Geraint Luff, and David Luecke
JavaScript Jabber How to Check Your Application Security featuring Liran Tal - JSJ 493
JavaScript Jabber 148 JSJ i.cx and EveryBit.js with Matt Asher and Dann Toliver
JavaScript Jabber JSJ 386: Gatsby.js with Chris Biscardi
JavaScript Jabber WebAuthn With Dan Moore - JSJ 562
JavaScript Jabber JSJ 406: Security in Node
JavaScript Jabber What's New with Elm? ft. Lindsay Wardell - JSJ 527
JavaScript Jabber 147 JSJ io.js with Isaac Schleuter and Mikeal Rogers
JavaScript Jabber Where is JAMstack and Dev Tooling Headed Today? - Putting JetPacks on Developers ft. Tejas Kumar - JSJ 514
JavaScript Jabber 146 JSJ React with Christopher Chedeau and Jordan Walke
JavaScript Jabber BONUS: Measuring Apps and Entrepreneurship with John-Daniel Trask
JavaScript Jabber JSJ 462: The Ultimate Guide to JavaScript Testing with Lucas da Costa
JavaScript Jabber Wix Velo with Yoav Abrahami - JSJ 558
JavaScript Jabber 144 JSJ Marionette.js 2.0 with Sam Saccone
JavaScript Jabber JSJ 340: JavaScript Docker with Julian Fahrer
JavaScript Jabber 143 JSJ Teaching Programming and Computer Science with Pamela Fox
JavaScript Jabber 141 JSJ Firefox OS with Jason Weathersby
JavaScript Jabber JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen
JavaScript Jabber 140 JSJ Using Art to Get and Keep People Interested in Programming with Jenn Schiffer
JavaScript Jabber JSJ 350: JavaScript Jabber Celebrates Episode 350!
JavaScript Jabber 139 JSJ The Mozilla Developer Network with Les Orchard and David Walsh
JavaScript Jabber Episode 500 Celebration! - JSJ 500
JavaScript Jabber JSJ 352: Caffeinated Style Sheets: Supporting High Level CSS with JavaScript with Tommy Hodgins
JavaScript Jabber 106 JSJ Protractor with Julie Ralph
JavaScript Jabber 138 JSJ {Track:js} with Todd Gardner
JavaScript Jabber 135 JSJ Smallest Federated Wiki with Ward Cunningham
JavaScript Jabber Navigating Online Events and Conferences - JSJ 541
JavaScript Jabber 127 JSJ Changes in npm-Land with Forrest Norvell, Rebecca Turner, Ben Coe, and Isaac Z. Schlueter
JavaScript Jabber 126 JSJ The Ionic Framework with Max Lynch and Tyler Renelle
JavaScript Jabber 124 JSJ The Origin of Javascript with Brendan Eich
JavaScript Jabber 133 JSJ Remote Work with Mike Hostetler
JavaScript Jabber Supply Chain Security - Part 2 - JSJ 525
JavaScript Jabber 123 JSJ Traceur with Erik Arvidsson
JavaScript Jabber JSJ 380: Expo for Web with Charlie Cheever
JavaScript Jabber Personal Branding for Developers with Morad Stern - JSJ 642
JavaScript Jabber JSJ 253 Gomix with Daniel X Moore
JavaScript Jabber 120 JSJ Google Polymer with Rob Dodson and Eric Bidelman
JavaScript Jabber Unveiling Qwik and JavaScript Streamlining Web Development with Shai Reznik - JSJ 628
JavaScript Jabber 069 JSJ The Application Cache with Jake Archibald
JavaScript Jabber JSJ 276: Vue.js with Maximilian Schwarzmüller
JavaScript Jabber 115 JSJ The ES6 Module Loader Polyfill, SystemJS, and jspm with Guy Bedford
JavaScript Jabber Supply Chain Security - Part 1 - JSJ 524
JavaScript Jabber 110 JSJ Zones with Brian Ford
JavaScript Jabber 104 JSJ Hypermedia APIs with Steve Klabnik
JavaScript Jabber 103 JSJ Robots with Raquel Vélez
JavaScript Jabber JSJ 376: Trix: A Rich Text Editor for Everyday Writing with Javan Makhmali
JavaScript Jabber 136 JSJ TrackingJS with Eduardo Lundgren
JavaScript Jabber 116 JSJ jQuery UI vs KendoUI with Burke Holland and TJ VanToll
JavaScript Jabber 052 JSJ Node & NPM with Isaac Schlueter
JavaScript Jabber 099 JSJ npm, Inc. with Isaac Schlueter, Laurie Voss, and Rod Boothby
JavaScript Jabber 098 JSJ Assemble.io with Brian Woodward and Jon Schlinkert
JavaScript Jabber 097 JSJ Gulp.js with Eric Schoffstall
JavaScript Jabber 095 JSJ AngularUI with Dean Sofer
JavaScript Jabber 118 JSJ Web Developer Skills
JavaScript Jabber 093 JSJ The New York Times and JavaScript with Eitan Konigsburg, Alastair Coote and Reed Emmons
JavaScript Jabber Builder.io and Qwik - JSJ 540
JavaScript Jabber 091 JSJ JSON APIs
JavaScript Jabber 090 JSJ Users Groups
JavaScript Jabber JSJ 382: Mental Health with Anatoliy Zaslavskiy
JavaScript Jabber 220 JSJ Teaching JavaScript with Kyle Simpson
JavaScript Jabber Changes in the JAMstack Landscape with Sean C Davis - JSJ 482
JavaScript Jabber JSJ 278 Machine Learning with Tyler Renelle
JavaScript Jabber 088 JSJ Lazy.js with Daniel Tao
JavaScript Jabber 087 JSJ TC39 with Alex Russell
JavaScript Jabber 030 JSJ Learning & Teaching JavaScript with Noel Rappin
JavaScript Jabber Structuring Node.js Applications: Event Loop, Metrics, and Efficient Processing Techniques - JSJ 657
JavaScript Jabber To TypeScript or Not to TypeScript - JSJ 538
JavaScript Jabber The Story of Mel with Tomer Lichtash and David Frankiel - JSJ 544
JavaScript Jabber 184 JSJ Web Performance with Nik Molnar
JavaScript Jabber Upcoming Performance Metrics for the Web - JSJ 542
JavaScript Jabber 219 JSJ Learning JavaScript in 2016
JavaScript Jabber 083 JSJ FRP and RxJS with Matthew Podwysocki
JavaScript Jabber 081 JSJ Promises for Testing Async JavaScript with Pete Hodgson
JavaScript Jabber SolidJS with Ryan Carniato - JSJ 528
JavaScript Jabber JSJ 354: Elm with Richard Feldman
JavaScript Jabber 077 JSJ Monocle with Alex MacCaw
JavaScript Jabber JSJ 447: Using Javascript for Data Analysis and Data Science with Daniel Lathrop
JavaScript Jabber New Horizons in Web Development with Danny Moerkerke - JSJ 658
JavaScript Jabber BONUS: Adding a Content Engine to Your App with a Headless CMS with Jake Lumetta
JavaScript Jabber 075 JSJ Maintainable JavaScript with Nicholas Zakas
JavaScript Jabber 016 JSJ SQL and NoSQL
JavaScript Jabber 071 JSJ JavaScript Strategies at Microsoft with Scott Hanselman
JavaScript Jabber JSJ 281: CodeSponsor - Sustaining Open-Source Software through Ethical Advertising with Eric Berry
JavaScript Jabber Interactive Coding Tutorials with Tomek Salkowski: Enhancing Developer Experiences - JSJ 651
JavaScript Jabber JSJ 287: Blockchain and JS with Ari Lerner
JavaScript Jabber 068 JSJ ES6 with Aaron Frost
JavaScript Jabber Core Web Vitals and Whatnot - JSJ 537
JavaScript Jabber 001 JSJ Asynchronous Programming
JavaScript Jabber Slaughtering Sacred Cows: Reconsidering Software Dev Truisms - JSJ 653
JavaScript Jabber 063 JSJ Burnout
JavaScript Jabber 062 JSJ Dojo with Dylan Schiemann
JavaScript Jabber 149 JSJ Passenger Enterprise with Node.js with Hongli Lai and Tinco Andringa
JavaScript Jabber What Is Functional Programming and What It's Not With Lane Wagner- JSJ 557
JavaScript Jabber 060 JSJ Development Environments
JavaScript Jabber 059 JSJ jQuery Mobile with Todd Parker
JavaScript Jabber JSJ 471: Things Every JavaScript Developer Must Know - Part 3
JavaScript Jabber 057 JSJ Functional Programming with Zach Kessin
JavaScript Jabber 056 JSJ Marionette.js with Derick Bailey
JavaScript Jabber 082 JSJ JSHint with Anton Kovalyov
JavaScript Jabber JSJ 458: Codota Tabnine and the Rise of Ai-powered Developer Tooling with Kyle Simpson
JavaScript Jabber 212 JSJ Horizon.js with Horizon.js with Michael Glukhovsky: Live from ng-conf!
JavaScript Jabber How to Get Hired at a FANG Company - BONUS
JavaScript Jabber Opinionated Core Web Vitals - JSJ 647
JavaScript Jabber 055 JSJ Web Developer Skills
JavaScript Jabber Deep Dive into Metrics and Monitoring with Prometheus and Grafana - JSJ 645
JavaScript Jabber Monitoring Performance and Core Web Vitals ft. Bianca Grizhar and Sumitra Manga - JSJ 501
JavaScript Jabber 053 JSJ Software Team Dynamics
JavaScript Jabber Flutter Essentials ft. Allen Wyma - JSJ 494
JavaScript Jabber 145 JSJ Meteor.js with Matt DeBergalis
JavaScript Jabber Adapting to Effect Cluster: JavaScript Developers' Guide to Enhancing Code Maintainability - JSJ 639
JavaScript Jabber 051 JSJ Finding a Job
JavaScript Jabber 049 JSJ MooTools with Valerio Proietti and Arian Stolwijk
JavaScript Jabber 044 JSJ Book Club: Effective JavaScript with David Herman
JavaScript Jabber Framework Comparisons, Real User Metrics, and Effective Performance Tools - JSJ 640
JavaScript Jabber State Management ft. Assaf Krintza - JSJ 508
JavaScript Jabber 040 JSJ Conferences
JavaScript Jabber JSJ 282: Trails.js with Scott Wyatt
JavaScript Jabber 039 JSJ Sweet.js with Tim Disney
JavaScript Jabber JSJ 360: Evolutionary Design with James Shore
JavaScript Jabber JSJ 264 Mendel with Irae Carvalho
JavaScript Jabber 037 JSJ Promises with Domenic Denicola and Kris Kowal
JavaScript Jabber 015 JSJ Open Discussion
JavaScript Jabber 013 JSJ Knockout.js with Steven Sanderson
JavaScript Jabber 067 JSJ Testem with Toby Ho
JavaScript Jabber 035 JSJ node-webkit
JavaScript Jabber 033 JSJ enyo.js
JavaScript Jabber 032 JSJ Angular.js
JavaScript Jabber JSJ 309: WebAssembly and JavaScript with Ben Titzer
JavaScript Jabber JSJ 262 Mozilla Firefox Developer Tools with Jason Laster
JavaScript Jabber Crafting Code and Community: AI, LeetCode, and Meetups - JSJ 644
JavaScript Jabber JSJ 365: Do You Need a Front-End Framework?
JavaScript Jabber 029 JSJ Bower.js with Alex MacCaw and Jacob Thornton
JavaScript Jabber 028 JSJ Greenfield vs Brownfield Projects
JavaScript Jabber 027 JSJ The JavaScript Community
JavaScript Jabber How to Become a Senior Developer with Shem Magnezi - JSJ 521
JavaScript Jabber Web3 with Nik Kalyani - JSJ 520
JavaScript Jabber 023 JSJ Phantom.js with Ariya Hidayat
JavaScript Jabber 022 JSJ Node.js on Azure with Glenn Block
JavaScript Jabber 096 JSJ The Challenges of Large Single Page JavaScript Applications with Bart Wood
JavaScript Jabber 017 JSJ CoffeeScript with Jeremy Ashkenas
JavaScript Jabber 011 JSJ Can HTML5 and JavaScript Really Replace Flash?
JavaScript Jabber JSJ 426: Killing the Release Night with Progressive Delivery with Dave Karow
JavaScript Jabber 009 JSJ Testing JavaScript with Joe Eames
JavaScript Jabber HTMX and InterCooler ft. Carson Gross - JSJ 513
JavaScript Jabber Transforming React Development: The Experimental Compiler’s Approach to Memoization and Performance - JSJ 636
JavaScript Jabber Catching Up on InertiaJS with Jonathan Reinink - JSJ 511
JavaScript Jabber 170 JSJ RabbitMQ with Derick Bailey
JavaScript Jabber Software Development as a Craft with Netta Bondy - JSJ 551
JavaScript Jabber Writing Change-Proof Software with Tests - JSJ 555
JavaScript Jabber 008 JSJ V8 and Dart with Lars Bak and Kasper Lund
JavaScript Jabber D3 and Data Visualization ft. Ian Johnson - JSJ 507
JavaScript Jabber Creeds of Craftsmanship - JSJ 505
JavaScript Jabber JSJ 404: Edge on Chromium with Chris Heilmann
JavaScript Jabber Navigating Web Development Challenges - JSJ 624
JavaScript Jabber JSJ 411: Unit Testing Jest with Daniel Caldas
JavaScript Jabber 3 Fundamental Pillars You Need to Succeed as an Entrepreneur - BONUS
JavaScript Jabber Javascript and the Blockchain with Max Kordek - JSJ 503
JavaScript Jabber Alpinejs, Microservices, Code Completion, and Getting Paid for Open Source with Caleb Porzio - JSJ 497
JavaScript Jabber Opinionated Core Web Vitals - JSJ 495
JavaScript Jabber Virtual DOM and the React Way, Part 1 - JSJ 512
JavaScript Jabber JSJ 337: Microstates.js – Composable State Primitives for JavaScript with Charles Lowell & Taras Mankovski
JavaScript Jabber The New JAMstack with Brian Rinaldi - JSJ 491
JavaScript Jabber Web Performance and the Google WordPress Team with Felix Arntz - JSJ 548
JavaScript Jabber The React Way & Opinionated Practices with Ian Schwartz - JSJ 488
JavaScript Jabber CrUX and Core Web Vitals - What to Measure on the Web with Rick Viscomi - JSJ 486
JavaScript Jabber JSJ 440: Why Serverless with Gareth McCumskey
JavaScript Jabber 054 JSJ JavaScript Parsing, ASTs, and Language Grammar w/ David Herman and Ariya Hidayat
JavaScript Jabber Gal Schlezinger and Edge Functions - JSJ 536
JavaScript Jabber JSJ 408: Reading Source Code with Carl Mungazi
JavaScript Jabber 162 JSJ ESLint with Jamund Ferguson
JavaScript Jabber 187 JSJ Vue.js with Evan You
JavaScript Jabber 156 JSJ Soft Skills and Marketing Yourself as a Software Developer with John Sonmez
JavaScript Jabber SEO for Developers ft. Mordy Oberstein - JSJ 509
JavaScript Jabber 058 JSJ Building Accessible Websites with Brian Hogan
JavaScript Jabber JSJ 294: Node Security with Adam Baldwin
JavaScript Jabber JSJ 247 Building a Development Environment with Cory House
JavaScript Jabber 085 JSJ Huxley with Pete Hunt
JavaScript Jabber 078 Working From Home
JavaScript Jabber 050 JSJ QUnit with Jörn Zaefferer
JavaScript Jabber JSJ 423: State of JS
JavaScript Jabber 130 JSJ Browser Tools and Extensions
JavaScript Jabber Find Out More About Elliot Johnson - BONUS
JavaScript Jabber JSJ 418: Security Scary Stories and How to Avoid Them with Kevin A McGrail
JavaScript Jabber Getting to Know Bruce A. Tate - BONUS
JavaScript Jabber Everything Remult with Noam Honig and Yoni Rapoport - JSJ 579
JavaScript Jabber Jason Weimann - Learn Video Game Development with Chuck - BONUS
JavaScript Jabber TanStack Router with Tanner Linsley - JSJ 578
JavaScript Jabber How Do You Stop Hating Your Job? - BONUS
JavaScript Jabber 234 JSJ JAMStack with Brian Douglas and Matt Christensen
JavaScript Jabber Reverse Engineering with Joyce Lin - JSJ 577
JavaScript Jabber JSJ 480: Are Micro Frontends worth the effort? (And if so when?)
JavaScript Jabber BONUS: How Opportunities Come Your Way When You're an Influencer
JavaScript Jabber Signals: What You Should Know with Tejas Kumar - JSJ 576
JavaScript Jabber The Best of JavaScript and Ruby in 2023 - JSJ 575
JavaScript Jabber JSJ 479: Practical Microservices with Ethan Garofolo
JavaScript Jabber BONUS: What is Charles Max Wood's Biggest Payoff for Being a Dev Influencer?
JavaScript Jabber Functional Programming with Ian Schwartz - JSJ 574
JavaScript Jabber What To Expect For JSNation - BONUS
JavaScript Jabber Introducing Codux With Nadav Abrahami & Tom Raviv - JSJ 573
JavaScript Jabber Build Your Game Using JavaScript with Andrzej Mazur- JSJ 572
JavaScript Jabber JSJ 392: The Murky Past and Misty Future of JavaScript with Douglas Crockford
JavaScript Jabber The State of JS Frameworks with Ryan Carniato: Part 2 - JSJ 571
JavaScript Jabber 114 JSJ Asynchronous UI and Non-Blocking Interactions with Elliott Kember
JavaScript Jabber 117 JSJ The Koa Framework with Gerred Dillon and Will Conant
JavaScript Jabber The State of JS Frameworks with Ryan Carniato: Part 1 - JSJ 570
JavaScript Jabber Web Performance With Alex Russell - JSJ 569
JavaScript Jabber 113 JSJ Community Dynamics with Reginald Braithwaite
JavaScript Jabber React Native & Every-Platform Embeddable UI With Taz Singh - JSJ 568
JavaScript Jabber BONUS: How Jason Weimann Became a Game Developer
JavaScript Jabber JSJ 452: Caddy 2 Web Server with Matthew Holt
JavaScript Jabber JSJ 475: DevOps for the JavaScript Developer
JavaScript Jabber JSJ 473: The Elements framework with Chris Mather
JavaScript Jabber Providing The Best User Experiences on the Web With Vercel- BONUS
JavaScript Jabber 228 JSJ React Native with Nader Dabit and Mike Grabowski
JavaScript Jabber Front-End Hydration - JSJ 567
JavaScript Jabber JSJ 472: RedwoodJS Brings Full-Stack to the JAMstack with Anthony Campolo
JavaScript Jabber 002 JSJ The Right Way to Build Web Applications
JavaScript Jabber Marvels Of Using Svelte and SvelteKit - JSJ 566
JavaScript Jabber JSJ 470: Fine Tuning Your Psychological Stack, or DevOps For Your Brain
JavaScript Jabber Runtime Security With Gal Weizman - JSJ 565
JavaScript Jabber 188 JSJ JavaScript Code Smells with Elijah Manor
JavaScript Jabber JSJ 468: The case for JavaScript iterators, part 1
JavaScript Jabber JSJ 460: The Things Every JavaScript Developer Must Know, Part 2
JavaScript Jabber JSJ 454: Mongoose, Mongo and Object Document Mapping (ODM) with Valeri Karpov
JavaScript Jabber 180 JSJ Finding a Job
JavaScript Jabber How To Plan For Success In 2023 - JSJ 564
JavaScript Jabber Qwik Part II With Misko Hevery - JSJ 563
JavaScript Jabber BONUS: How to do LARGE Volumes of HIGH Quality Work - While Spending Fewer Hours Working
JavaScript Jabber 213 JSJ Developer Evangelism with Greg Baugues
JavaScript Jabber Blockchain with Max Kordek - JSJ 529
JavaScript Jabber JSJ 399: Debugging with Async/Await with Valeri Karpov
JavaScript Jabber JSJ 457: Career Transitioning with Laura Harvey
JavaScript Jabber JSJ 456: Developer-First Security and Security Tooling For Developers with Liran Tal & Brian Vermeer
JavaScript Jabber JSJ 455: Introducing and Understanding Svelte and Sapper with Mark Volkmann
JavaScript Jabber JSJ 453: Debugging Third Party JavaScript with Ben Vinegar
JavaScript Jabber JSJ 335: “CanJS 4.0” with Justin Meyer
JavaScript Jabber JSJ 446: Achieving Work-Life Balance, Especially When WFH
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber JSJ 445: Augmented Reality for Mobile Browsers with Connell Gauld
JavaScript Jabber JSJ 441: The Present and Future of JavaScript Bundling and Delivery with Yoav Weiss
JavaScript Jabber JSJ 439: More Jabber About Less JavaScript with Alex Russell
JavaScript Jabber Remix and EpicWeb.dev with Kent C. Dodds - JSJ 554
JavaScript Jabber Unpacking Deno 2: Code Stability, Free Speech, and more - JSJ 648
JavaScript Jabber 019 JSJ Browserify with James Halliday
JavaScript Jabber JSJ 419: Google App Script with Ben Collins
JavaScript Jabber 034 JSJ Ember.js
JavaScript Jabber JSJ 302: Evaluating Web Frameworks with Kitson Kelly
JavaScript Jabber JSJ 465:The Power of Micro Front-Ends with Michael Geers
JavaScript Jabber JSJ 395: The New Ember with Mike North
JavaScript Jabber The Alphabet Soup of Performance Measurements - JSJ 622
JavaScript Jabber 031 JSJ history.js
JavaScript Jabber JSJ 436: MongoDB Basics with Joe Karlsson
JavaScript Jabber JSJ 379: FindCollabs and Podcasting with Jeff Meyerson
JavaScript Jabber JSJ 433: Understanding the Browser Layer with Noam Rosenthal
JavaScript Jabber 237 JSJ CLls - Ember Angular and React with Tracy Lee
JavaScript Jabber New Frontiers in Web Platform Development with Bruce Lawson - JSJ 634
JavaScript Jabber JSJ 310: Thwarting Insider Threats with Greg Kushto
JavaScript Jabber 125 JSJ WebGL with Sean Griffin
JavaScript Jabber Pain-Free Automated Deployments with DigitalOcean's App Platform - BONUS
JavaScript Jabber 061 JSJ Functional Reactive Programming with Juha Paananen and Joe Fiorini
JavaScript Jabber JSJ 424: UI5 and web components with Peter Muessig
JavaScript Jabber JSJ 250 Celebration
JavaScript Jabber 010 JSJ Node.js
JavaScript Jabber JSJ 422: CSS and Houdini with Una Kravets
JavaScript Jabber JSJ 421: Semantic HTML with Bruce Lawson
JavaScript Jabber JSJ 299: How To Learn JavaScript When You're Not a Developer with Chris Ferdinandi
JavaScript Jabber BONUS: Continuing Your Learning Journey by Finding Mentors as an Influencer
JavaScript Jabber JSJ 420: OpenAPI, Redoc, and API Documentation with Adam Altman
JavaScript Jabber JSJ 417: Serverless with Microsoft Azure with Burke Holland
JavaScript Jabber TypeScript, ESLint, and TypeScript ESLint with Josh Goldberg - JSJ 605
JavaScript Jabber Harnessing Module Federation and Micro Front-Ends in JavaScript Development - JSJ 603
JavaScript Jabber Unpacking Core Web Vitals - JSJ 620
JavaScript Jabber 072 JSJ Screencasts
JavaScript Jabber JSJ 416: GraphQL Developer Tools with Sean Grove
JavaScript Jabber JSJ 414: JavaScript Jabber Still at RxJs Live
JavaScript Jabber JSJ 409: Swagger and Open API with Josh Ponelat
JavaScript Jabber JSJ 405: Machine Learning with Gant Laborde
JavaScript Jabber JSJ 407: Reactive JavaScript and Storybook with Dean Radcliffe
JavaScript Jabber JSJ 450: Native Features Inside The Browser - Introducing Google's Project Fugu with Thomas Steiner
JavaScript Jabber JSJ 464: Web Components FTW with Ben Farrell
JavaScript Jabber JSJ 400: The Influence of JavaScript Jabber
JavaScript Jabber 185 JSJ PouchDB with Nolan Lawson
JavaScript Jabber DevOps for JavaScript ft. Will Button - JSJ 502
JavaScript Jabber 020 JSJ Cloud9
JavaScript Jabber 076 JSJ Meteor.js with Marcus Phillips and Fred Zirdung
JavaScript Jabber Astro with Fred K. Schott - JSJ 561
JavaScript Jabber JSJ 398: Node 12 with Paige Niedringhaus
JavaScript Jabber JSJ 396: Publishing Your Book with Jonathan Lee Martin
JavaScript Jabber JSJ 342: Aurelia in Action with Sean Hunter
JavaScript Jabber JSJ 394: SMS Integration with Dominik Kundel
JavaScript Jabber JSJ 393: Why You Should Be Using Web Workers with Surma
JavaScript Jabber Using Storybook and Nuxt To Quickly Build Websites - JSJ 531
JavaScript Jabber JSJ 336: “The Origin of ESLint” with Nicholas Zakas
JavaScript Jabber JSJ 332: “You Learned JavaScript, Now What?” with Chris Heilmann
JavaScript Jabber JSJ 391: Debugging with Todd Gardner
JavaScript Jabber JSJ 330: “AWS: Amplify” with Nader Dabit
JavaScript Jabber JSJ 448: MongoDB Schema Fundamentals with Joe Karlsson
JavaScript Jabber JSJ 323: "Building a JavaScript platform that gives you the power to build your own CDN" with Kurt Mackey
JavaScript Jabber JSJ 383: What is JavaScript?
JavaScript Jabber Transitioning a Large Front-End Codebase to TypeScript ft. Priscila Oliveira and Mark Story – JSJ 498
JavaScript Jabber The 3 Essentials for Successful Job Outcomes - BONUS
JavaScript Jabber JSJ 378: Stencil and Design Systems with Josh Thomas and Mike Hartington
JavaScript Jabber JSJ 372: Kubernetes Docker and Devops with Jessica Deen LIVE from Microsoft BUILD
JavaScript Jabber React Component and State Management - JSJ 526
JavaScript Jabber JSJ 474: Things JavaScript Developers Should Know, Part 1
JavaScript Jabber JSJ 371: The Benefits and Challenges of Server-Side Rendering (SSR) with Dan Shappir
JavaScript Jabber BONUS: How to Speed Up Your Website For Fun and Profit with Inian Parameshwaran
JavaScript Jabber JSJ 368: TypeScript - Good or Bad
JavaScript Jabber JSJ 370: Azure Functions Part II with Jeff Hollan LIVE at Microsoft BUILD
JavaScript Jabber JSJ 390: Transposit with Adam Leventhal
JavaScript Jabber JSJ 369: Azure Functions with Colby Tresness LIVE at MIcrosoft BUILD
JavaScript Jabber JSJ 367: Pair Programming
JavaScript Jabber AgGrid: From Open Source to Successful Business ft. Niall Crosby - JSJ 504
JavaScript Jabber Node in the Browser and Much more: Web Containers with Eric Simons - JSJ 487
JavaScript Jabber JSJ 463: Building Web Applications with Firebase
JavaScript Jabber JSJ 366: npm with Mikeal Rogers
JavaScript Jabber JSJ 364: Ember Octane with Sam Selikoff
JavaScript Jabber 238 JSJ Intellectual Property and Software Forensics with Bob Zeidman
JavaScript Jabber BONUS: How to do LARGE Volumes of HIGH Quality Work - While Spending Fewer Hours Working
JavaScript Jabber JSJ 362: Accessibility with Chris DeMars
JavaScript Jabber JSJ 363: Practical JAMstack and Serverless with Gareth McCumskey
JavaScript Jabber JSJ 361: Enough with the JS Already with Nicholas Zakas
JavaScript Jabber Virtual DOM and the React Way, Part Deux - JSJ 518
JavaScript Jabber How to Stay Current with JavaScript - JSJ 499
JavaScript Jabber NoSQL and RavenDB - JSJ 530
JavaScript Jabber JSJ 357: Event-Stream & Package Vulnerabilities with Richard Feldman and Hillel Wayne
JavaScript Jabber 233 JSJ Google Chrome Extensions with John Sonmez
JavaScript Jabber JSJ 353: Signal R with Brady Gaster LIVE at Microsoft Ignite
JavaScript Jabber JSJ 347: JAMstack with Divya Sasidharan & Phil Hawksworth
JavaScript Jabber JSJ 351: Dinero.js with Sarah Dayan
JavaScript Jabber JSJ 344: Inclusive Components with Heydon Pickering
JavaScript Jabber JSJ 341: Testing in JavaScript with Gil Tayar
JavaScript Jabber JSJ 333: “JavaScript 2018: Things You Need to Know, and a Few You Can Skip” with Ethan Brown
JavaScript Jabber JSJ 444: Coding Front-end JavaScript for Accessibility with Neha Sharma
JavaScript Jabber 231 JSJ Codewars with Nathan Doctor, Jake Hoffner, and Dan Nolan
JavaScript Jabber JSJ 415: Progressive Web Apps with Maximiliano Firtman
JavaScript Jabber JSJ 410: Iterating on Open Source
JavaScript Jabber JSJ 412: Svelte and Sapper with Svelte Master
JavaScript Jabber JSJ 403: Why Developers Need Social Skills with Mani Vaya
JavaScript Jabber JSJ 381: Building a Personal Brand with John Sonmez
JavaScript Jabber JSJ 387: How to Stay Current in the Tech Field
JavaScript Jabber JSJ 385: What Can You Build with JavaScript?
JavaScript Jabber JSJ 377: Bringing Maps and Location Into Your Apps with the ArcGIS API for JavaScript with Rene Rubalcava
JavaScript Jabber 221 JSJ Visual Studio Code with Wade Anderson Live From Microsoft Build 2016
JavaScript Jabber JSJ 375: Are You Hurting the Web?
JavaScript Jabber JSJ 373: What Do You Need to Do to Get a Website Up?
JavaScript Jabber 218 JSJ Ember.js with Yehuda Katz
JavaScript Jabber JSJ 359: Productivity with Mani Vaya
JavaScript Jabber JSJ 355: Progressive Web Apps with Aaron Gustafson LIVE at Microsoft Ignite
JavaScript Jabber JSJ 346: Azure Pipelines with Ed Thomson LIVE at Microsoft Ignite
JavaScript Jabber JSJ 317: Prisma with Johannes Schickling
JavaScript Jabber JSJ 315: The effects of JS on CSS with Greg Whitworth
JavaScript Jabber JSJ 313: Light Functional JavaScript with Kyle Simpson
JavaScript Jabber JSJ 300: Celebration
JavaScript Jabber JSJ 291: Serverless For JavaScript with Gareth McCumskey
JavaScript Jabber JSJ 295: Developers as Entrepreneurs with Ryan Glover
JavaScript Jabber JSJ 293: Big Data with Nishant Thacker
JavaScript Jabber JSJ 292: CosmosDB with Kirill Gavrylyuk
JavaScript Jabber JSJ 285 : Finding a Job Even If You're Not a Senior Developer by Charles Max Wood
JavaScript Jabber JSJ 284 : Helping Developers Build Healthy Bodies
JavaScript Jabber JSJ 277: Dojo 2 with Dylan Schiemann and Kitson Kelly
JavaScript Jabber JSJ 309: WebAssembly and JavaScript with Ben Titzer
JavaScript Jabber 048 JSJ Why JavaScript Is Hard

JavaScript Jabber

Subscribe

Follow

JSJ 434: Understanding and Using ES Modules in Node with Gil Tayar

Show Notes

Transcript