Going to talk with stories from my own past so that you have more context into why I'm saying what I'm saying. Starting around 2010 up til now.

JavaScript

History

node.js, commonjs, ES2015 (modules defined here)

Current

modules are kinda supported. commonjs still reigns supreme

Future

ESModules, import by URL, Browser support, HTTP2/3

Bundling Applications

History

Basic Script Concatenation

Current

Bundler-basic script concatenation and

Unbundling

ESModules, Snowpack

User-Centric Deployment

History

Running servers somewhere

Current

JAMStack

Future

CRDTs, Offline-first,

Data

History

REST

var Books = Backbone.Collection.extend({
  url: '/books'
});

Current

GraphQL, serverless

Future

GraphQL subscriptions, serverless at edge

Gatsby, Next, and CRA

The path to meta-frameworks and future.

History

React, 2013/4. Browserify, Webpack

Current Day

Future

History

We've gone from setting up Gulp pipelines, to manually writing babel and webpack config, to standardizing create-react-app, to higher level frameworks like Gatsby and Next. What's comes after that?* [true] incremental builds: How do we compile small pieces of application and ship less JS? Should we?* content mesh abstractions (onegraph, gatsby, etc)* serverless functions* spinning up databases, faster.