Writing a Webmodule
summary
A how-to for shipping tiny npm modules aimed at the browser: export one function, keep each repo single-purpose, include a README, unit tests and npm and GitHub name parity, prefer hyphenated names, and use browserify for bundling. Tests run in the cloud with zuul driving travis ci and sauce labs so matrix failures show which browsers break; the annoying part is creating a Sauce Labs account per module but the end result is green builds and cross‑browser confidence.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:12Coding Standards
- 2:16Small and Focused
- 2:54Polyfills
- 3:31Inverses
- 4:26Browserify
- 5:04Naming
- 6:24Readme
- 8:00Cloud Testing
- 8:58Travis CI
- 10:05Sauce Labs
related talks
24mMaking small modules actually work with webpack and npm
36mUnbundling the JavaScript module bundler
23mPublishing in JavaScript Ecosystem: How to Keep Everyone Happy?
40mBuild Your Own webpack (Live Coding an Ultra-Simplified Example of a Modern Module Bundler in JavaScript)
24mPublishing in the JavaScript Ecosystem & Keeping Users Happy
35mBrowser Package Management
24mThe Ins-and-Outs of Publishing a Module to npm
47mNative JavaScript Modules: import {Browsers, Node.js}; export {production};