# Using Native JavaScript Modules in Production Today

DevFeed: [Using Native JavaScript Modules in Production Today](<https://devfeed.tech/articles/using-native-javascript-modules-in-production-today-29532.md>)

Original publisher: [Read original article](<https://philipwalton.com/articles/using-native-javascript-modules-in-production-today/>)

Published: 2019-08-20T07:20:17Z

Content type: article

Language: en

Sources: [Philip Walton](<https://devfeed.tech/sources/philip-walton.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Transpilers](<https://devfeed.tech/topics/transpilers.md>), [browsers](<https://devfeed.tech/topics/browsers.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [modules](<https://devfeed.tech/tags/modules.md>), [performance](<https://devfeed.tech/tags/performance.md>), [transpilers](<https://devfeed.tech/tags/transpilers.md>)

## AI overview

The article argues that, with current bundler advances, production applications can use optimized ES2015 JavaScript modules with static and dynamic imports. It revisits earlier research that favored bundling and explains why that research did not compare optimized module deployments with optimized classic scripts.

## Source excerpt

Two years ago I wrote about a technique--now commonly referred to as the module/nomodule pattern--that allows you to write ES2015+ JavaScript and then use bundlers and transpilers to generate two versions of your codebase, one with modern syntax (loaded via ) and one with ES5 syntax (loaded via ). The technique allows you to ship significantly less code to module-supporting browsers, and it's now supported by most web frameworks and CLIs.