- 0.1.0Latest
- 0.1.1
- 0.1.2
- 0.1.3
- 0.2.0
- 0.2.1
- 0.2.2
- 0.3.0
- 0.4.0
- 0.4.1
- 0.4.2
- 0.4.3
- 0.5.0
- 0.5.1
- 0.5.2
- 0.5.3
- 0.5.4
- 0.6.0
- 0.6.1
- 1.0.0
- 1.1.0
- 1.2.0
- 1.2.1
- 1.2.2
- 1.2.3
- 1.2.4
- 1.2.5
- 1.3.0
- 1.3.1
- 1.3.2
- 2.2.0
- 2.1.0
- 2.0.0
- 2.0.0-beta
- 1.9.0
- 1.8.3
- 1.8.2
- 1.8.1
- 1.8.0
- 1.7.5
- 1.7.4
- 1.7.3
- 1.7.2
- 1.7.1
- 1.7.0
- 1.6.0
- 1.5.3
- 1.5.2
- 1.5.1
- 1.5.0
- 1.4.1
- 1.4.0
- 1.3.5
- 1.3.4
- 1.3.3
- v.1.3.2
- v1.3.1
- v1.3.0
- v1.2.5
- v1.2.4
- v1.2.3
- v1.2.2
- v1.2.1
- v1.2.0
- v1.1.0
- v1.0.0
- v0.6.1
- v0.6.0
- v0.5.4
- v0.5.3
- v0.5.2
- v0.5.1
- v0.5
- v0.4.3
- v0.4.2
- v0.4.1
- v0.4.0
- v0.3.0
- v0.2.2
- v0.2.1
- v0.2.0
- v0.1.3
- v0.1.2
- v0.1.1
- v0.1.0
Peko
The featherweight & UI-library-agnostic SSR toolkit for Deno.
No bundling or build process. Server & Browser share all source modules!
Summary
- First-class frontend - server-side rendered then rapidly hydrated with preloaded JS modules (~10kb in Preact example dir).
- Production-ready backend - reliablility and performance with Typescript and configurable page caching.
- Software minimalism - zero build-time technologies or bloated node_modules (<80MB Docker images).
- Ease of adoption - intuitive functions & zero fixed project structure.
Read on, star/fork/clone away and feel free to contribute any ideas!
Getting started
- Install Deno
-
$ git clone https://github.com/sebringrose/peko.git -
$ cd peko -
$ deno run --allow-net --allow-env --allow-read --watch example.js -
Check out
./examples/preact/srcfor frontend code and play around with./examples/preact/app.jsfor app server changes.
Import Peko into your own Deno project:
import Peko from "https://github.com/sebringrose/peko/mod.ts"
Note: Lit-html VS Code plugin recommended if using HTM & Preact.
Deployment
Docker & Deno Deploy deployment guides coming soon!
This project aims to be ready for production soon but it is not complete with extensive testing yet! Use at your own risk.
How does it work?
Deno http server receives page requests and renders your source UI library modules to HTML. The example uses Preact UI components and preact-render-to-string for Server-Side Rendering (SSR). The HTML is injected into an HTML template along with configurable CSS, JS & metadata before being served to the user’s browser client.
If env.ENVIRONMENT === "production" page renders are also cached so subsequent requests can be served instantly until the page’s configurable cache lifetime is reached.
Why is this cool?
Because it provides all of the SEO and UX benefits of SSR with no JavaScript transpilation or bundling required - the server and browser use the exact same code! This completely eliminates part of the traditional JavaScript SSR toolchain, increasing project maintainability and simplicity of development.
It is all possible because of the unique combination of powerful new JavaScript tools. Deno, unlike Node.js, is built to the ECMAScript specification. This makes it compatible with browser JavaScript and vice versa which elimates the need to generate separate client and server JavaScript bundles (the support for URL imports is the secret sauce). UI libraries like Preact combined with htm offer lightning fast client-side hydration with a transpiler-free JavaScript markup syntax. On top of this Deno has native TypeScript support, a rich runtime API and a standard library full of great tools as well as a passionate community supporting it.
Differences between other frameworks like Next.js, etc.
Peko is built with one radical design decision: it isn’t built to support the infinite universe of npm UI libraries (as these often require bundling and transpilation). This is a deliberate step away from the inflated state that many modern web applications find themselves in. Just make sure your source modules can run directly in the browser without transpilation!