Pika: Reimagining The Registry
summary
Pika builds a registry and tools that let npm packages run in browsers without a full bundler by converting node_modules to single files at install time so browsers can import real ESM paths. Picoweb exists in production and powers the pika site. Goal: reduce dev startup to ~1 second and hot-reload to ~300 ms. It handles CommonJS shims, rewrites package-name imports, supports Babel/TypeScript transforms, and uses companion libs (eg csc) for CSS so development can skip heavy webpack builds.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:03Webpack struggles and bundle analysis
- 3:54Cost of waiting for bundlers
- 4:35Introducing Pika project
- 7:26Why we need web bundlers
- 10:55Node and npm’s impact on bundling
- 13:25Modern ES modules and limitations
- 14:50Introducing Picoweb tool
- 16:33Performance benefits of unbundled apps
- 17:56Handling CSS and other assets
- 19:00Choice over bundlers vs no bundlers
- 19:41JavaScript fatigue and community divide
- 20:43Simplifying the web development stack
- 21:57Conclusion and Q&A
related talks
27mPika: Reimagining the Registry
34mTowards a simpler JavaScript ecosystem
35mBrowser Package Management
30mSnowpack, Webpack and the Third Age of JavaScript
58m10KB or Bust: The Delicate Power of Webpack and Babel
39mWhat Can We Learn With JavaScript Fatigue?
46mES Modules: The next revolution?
52m10KB or Bust: The Delicate Power of Webpack and Babel