Javascript in 2015
Glen Maddern3 HN recommenders · recommended in 4 months, 2015–2017
tutorial · intermediate · 2015–2017 on HN
A short screencast tour of JSPM, SystemJS and ES6 features, building a small app with the then-new JavaScript module and package tooling. It shows how JSPM works as a package manager, bundler and loader.
Commenters credit it with opening their eyes to JSPM and using it to choose build systems.
Up next
3 mo on HNCRDTs and the Quest for Distributed Consistency
InfoQ
3 HN recommender · 2018–2020
2 mo on HNContainer Hacks and Fun Images
Jessie Frazelle
2 HN recommender · 2019–2022
2 mo on HNNetdev 0x16 - Keynote: It's Time to Replace TCP in the Datacenter
netdevconf
2 HN recommender · 2023–2023
13 mo on HNRich Harris - Rethinking reactivity
You Gotta Love Frontend
15 HN recommender · 2019–2026
3 mo on HNCgroups, namespaces, and beyond: what are containers made from?
Docker
4 HN recommender · 2017–2023
5 mo on HNGolang UK Conf. 2016 - Liz Rice - What is a container, really? Let's write one in Go from scratch
GopherCon UK
3 HN recommender · 2016–2019
12 mo on HN8-bit computer update
Ben Eater
14 HN recommender · 2017–2023
1 mo on HNLecture 7A: Metacircular Evaluator, Part 1
MIT OpenCourseWare
1 HN recommend · 2020–2023
14 mo on HNWhat the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
16 HN recommender · 2015–2025
10 mo on HNCrockford on JavaScript - Volume 1: The Early Years
YUI Library
10 HN recommender · 2013–2022
10 mo on HNRailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Confreaks
6 HN recommender · 2017–2020
10 mo on HNJavaScript: The Good Parts
Google TechTalks
11 HN recommender · 2009–2020
4 comments from Hacker News
If you're looking for alternatives to Webpack, please also check out JSPM (a good short description might be "preprocessing system + package manager + systemjs"): link It takes a little more to get it to work with vue (the plugin that makes .vue files work is older and unsupported nowadays), but I use it just fine, with my template, styling and component files separated (I wrote a little thing: link ) If you dislike how complex webpack is, you'll like JSPM -- here's the video that got me hooked (it's pretty old but still valid): ▶ this video
I regularly use JSPM (with systemJS) for new projects, and I've liked it a lot. Back when webpack first came out, I struggled a little bit with figuring out what it actually did. While I understand now, I am not why I would want to (or you) switch from JSPM to webpack. I don't see any features that webpack has that JSPM doesn't (and JSPM offered ES6 support well before of course, with babel on by default). I like to use JSPM because of how relatively easy everything fits together -- and how straightforward it is to use and configure. For those not familiar, JSPM is a package manager, module bundler, and module loader all in one for javascript applications. This means you can: jspm install <package> And JSPM will look in NPM/Github (and it's possible to add registries, like bower) for stuff . That's the package management facet. jspm bundle-sfx js/main dist/build.js Bundle your code all together, and drop it in a file <import src="system.js"> <script> // set our baseURL reference path System.config({ baseURL: '/app' }); // loads /app/main.js System.import('main.js'); </script> Load your modules on the fly like you would with something like RequireJS. As you may have guessed, JSPM relies on SystemJS ( link ) internally for some of the features above. This video really opened my eyes to what it could do: ▶ this video
My favourite way is via JSPM and live-server. I got into that after watching this amazing dev video: ▶ this video
As if the churn wasn't already bad enough, I've recently started using JSPM[1] and it's pretty awesome. I'm writing ES6+ code with hot reloading react components. If you're trying to decide between build systems I would recommend checking it out, and watching this video[2] for a nice overview. [1] link [2] ▶ this video