0.3.0 • Published 10 years ago
node-serviceworker v0.3.0
node-serviceworker
Environment for running serviceworkers in node.js, as 'isomorphic' request handlers for clients without SW support.
Features and status
Based on this task.
- Registration to a scope. This introduces a very basic routing scope, but finer-grained routing is normally happening inside the service worker.
- fetch, via https://github.com/gwicke/node-fetch
- Added
ReadableStreamsupport. - This also provides a basic
Responseimplementation, wrapping the node HTTP response object.
- Added
Requestwrapper for Node's IncomingMessage.- Cache. On the server, this is useful for in-process caching of frequently-used fragments.
- Accept
ReadableStreambody responses inFetchEvent.respondWith - IndexedDB, via https://github.com/dumbmatter/fakeIndexedDB
- Runs basic sw-toolbox based ServiceWorkers.
- Periodic ServiceWorker code refreshs.
- Per-domain configuration support.
Demo
A demo service based on node-serviceworker-proxy is running at https://swproxy.wmflabs.org/wiki/Foobar. This is serving a demo streaming serviceworker, which composes templates and streamed HTML content using web-stream-util and web-html-stream.
TODO
- More closely implement
WorkerGlobalScope. Roughly in order of importance:
consolehas a lot more methods in browsers than in nodelocation: doneperformanceobject: Lots missing.navigatorobject: Partly done, but more to do.
0.3.0
10 years ago
0.2.9
10 years ago
0.2.8
10 years ago
0.2.7
10 years ago
0.2.6
10 years ago
0.2.5
10 years ago
0.2.4
10 years ago
0.2.3
10 years ago
0.2.2
10 years ago
0.2.1
10 years ago
0.2.0
10 years ago
0.1.9
10 years ago
0.1.8
10 years ago
0.1.7
10 years ago
0.1.6
10 years ago
0.1.5
10 years ago
0.1.4
10 years ago
0.1.3
10 years ago
0.1.2
10 years ago
0.1.1
10 years ago