Articles
Evergreen explainers on how the web platform works and the ideas WebJs is built on: web components, building with no build step, server-side rendering, and running TypeScript straight from the runtime. Reference reading, not release notes.
A web components framework builds your UI on native custom elements instead of a proprietary runtime, then adds the server rendering, routing, and data layer the platform leaves out. What that buys you, and how WebJs does it.
Server-side rendering for web components used to be the thing that did not work. Why the wall was there, how Declarative Shadow DOM removed it, and how WebJs renders custom elements to HTML with no build step.
A no-build JavaScript framework serves the code you wrote straight to the browser, no bundler and no compile step. What replaced the bundler, the honest tradeoff, and how WebJs runs a full-stack app this way.
Web components vs React: what each one actually is, where they genuinely differ on portability, state, and ecosystem, and how WebJs gives web components the full-stack story React users expect.
HTML web components wrap real server-rendered markup and enhance it, instead of rendering everything from an empty tag in JavaScript. Why the pattern is more resilient, and how WebJs makes it the default.
You can run TypeScript without compiling it by stripping the types at load. Why stripping is faster than tsc, the one real constraint, and how WebJs serves .ts files straight to Node, Bun, and the browser.
