ts-liveview
TypeScript icon, indicating that this package has built-in type declarations

1.1.1 • Public • Published

TS LiveView

npm Package Version

LiveView enables rich, real-time user experiences with server-rendered HTML.

Just like Phoenix LiveView but in Typescript!

Examples

  • [x] Single-Page Application (SPA): Demo, Source. With:

    • url routing
    • rainbow animation
    • bandwidth quota
  • [x] Realtime chatroom: Demo, Source

Why server-rendered?

  • To make the PWA deliver initial meaningful paint as soon as possible
  • To avoid over bloating the amount of javascript the client need to download and execute
  • To allow 'over-the-air' update of application deployment

Features

  • [x] Return complete layout on initial GET request (in a single pass)
  • [x] Progressive enhancement for interactivity
  • [x] Realtime Server side 'rendering' for incremental update
  • [x] Bidirectional event push
  • [x] Auto reconnect websocket
  • [x] Attachable on custom express and primus instance

Size Comparison

Tools Runtime Code Size (minified)
TS LiveView v0 + morphdom 8K
(Phoenix) LiveView.js + morphdom 29K
TS LiveView v1 + morphdom + primus.js 46K
Vue 2.5.20 88K
React 16.6.3 + React DOM 112K
Ember 3.0.0.beta.2 468K
React + Ionic * 2.1M
Stencil + Ionic * 3.0M
Angular + Ionic * 4.2M

*: all Ionic build excluded the svg, assets, *.map and PWA json files

Not only is LiveView + morphdom much lighter than the JS frameworks, the frameworks are just the baseline. You still need to ship application-specific JS and often add supporting JS libraries such as react-router, redux and friends to get feature parity. Those can easily boom the code size for runtime to be over 10MB, causing the latency of the first meaningful paint to be over 25 seconds on mobile device.

reference: https://dockyard.com/blog/2018/12/12/phoenix-liveview-interactive-real-time-apps-no-need-to-write-javascript

The Gist (Example in Code)

Simple Clock

import { c, h, Session, startServer } from '../src'

function render(state: number) {
  return c(
    '#clock',
    h`<div id="clock">${new Date(state).toLocaleString()}</div>`,
  )
}

function createSession(session: Session): Session | void {
  let state = Date.now()

  function update() {
    const view = render(state)
    session.sendComponent(view)
  }

  const timer = setInterval(() => {
    state = Date.now()
    update()
  }, 1000)

  session.onClose(() => clearInterval(timer))

  return session
}

startServer({
  port: 3000,
  heads: [
    // default path for websocket lib
    `<script src="/primus/primus.js"></script>`,
  ],
  createSession,
  initialRender: (req, res) => {
    return render(Date.now())
  },
})

Using s-js to trigger updates

import S from 's-js'
import { c, genPrimusScript, h, Request, Response, Session, startServer, } from '../src'

function initialView(req: Request, res: Response) {
  return c('#app', h`<div id="app" class="init">
  <p>
    Now is: ${new Date().toLocaleString()}
  </p>
  <label>Name:</label>
  <input onchange="send('name', event.target.value)">
  <br>
  <p>
    Hello, Guest
  </p>
</div>`)
}

// this callback will be called from a S.root context
// the context will be cleanup automatically when the client connection is closed
function createSession(session: Session): Session | void {
  const clock = S.data(Date.now())
  const timer = setInterval(() => clock(Date.now()), 1000)
  S.cleanup(() => clearInterval(timer))
  setInterval(() => clock(Date.now()), 1000)

  function renderClock() {
    return c(
      '#clock',
      h`<p id="clock">Now is: ${new Date(clock()).toLocaleString()}</p>`,
    )
  }

  const name = S.data('')

  function renderName() {
    return c(
      '#name',
      h`<div id="name">
<label>Name: </label>
<input onchange="send('name', event.target.value)">
<p>
Hello, ${name() || 'Guest'}
</p>
</div>`,
    )
  }

  function renderRoot() {
    return S.sample(() =>
      c(
        '#app',
        h`<div id="app" class="live">
${renderClock()}
${renderName()}
</div>`,
      ),
    )
  }

  session.sendComponent(renderRoot())
  session.live(renderClock, { skipInitialSend: true })
  session.live(renderName, { skipInitialSend: true })

  session.onMessage(message => {
    const [k, v] = message
    if (k !== 'name') {
      console.warn('unknown client message:', message)
      return
    }
    name(v)
  })

  return session
}

startServer({
  port: 3000,
  heads: [genPrimusScript()],
  createSession,
  initialRender: (req, res) => {
    return initialView(req, res)
  },
})

More examples

Todo

  • [x] Auto reconnect the websocket*
  • [x] Recover session when reconnect*
  • [x] make session simpler and put s-js component into core?
  • [x] update spa example, tests, and readme to adopt the breaking change
  • [ ] abstract primus to allow custom transport and encoding
  • [ ] use history.pushState in demo instead of location hash, for easier sharing and initial rendering
  • [ ] support preventing XSS issue**

*: Solved by Primus

**: maybe use JSX/TSX? If so, will be costly to detect changes. Currently requires the developer to explicitly escape it, with the help of ts-liveivew/helpers/server#s()

Releases

v1

  • Made API more concise (especially for usage with s-js)
  • Support repeat components (e.g. map on array with shared template)

v0

  • Support pre-rendering
  • Support live-update with diff-based patching with morphdom

LICENSE

BSD-2-Clause LICENSE (Free Open Source Software)

Package Sidebar

Install

npm i ts-liveview

Weekly Downloads

14

Version

1.1.1

License

BSD-2-Clause

Unpacked Size

54.9 kB

Total Files

43

Last publish

Collaborators

  • beenotung