# Service Workers

Published articles for Service Workers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Running the full server-side Datasette Python app in the browser with service workers and Pyodide

DevFeed: [Running the full server-side Datasette Python app in the browser with service workers and Pyodide](<https://devfeed.tech/articles/running-the-full-server-side-datasette-python-app-in-the-browser-with-service-workers-and-pyodide-138121.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Nov/17/datasette-lite/>)

Author: Simon Willison

Published: 2026-11-17T16:48:33Z

Content type: article

Language: en

Sources: [Simon Willison](<https://devfeed.tech/sources/simon-willison.md>), [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [Web app](<https://devfeed.tech/topics/webapp.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [bug](<https://devfeed.tech/tags/bug.md>), [csv](<https://devfeed.tech/tags/csv.md>), [database](<https://devfeed.tech/tags/database.md>), [datasette](<https://devfeed.tech/tags/datasette.md>), [datasette-1-567](<https://devfeed.tech/tags/datasette-1-567.md>), [datasette-lite](<https://devfeed.tech/tags/datasette-lite.md>), [datasette-lite-27](<https://devfeed.tech/tags/datasette-lite-27.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [javascript-774](<https://devfeed.tech/tags/javascript-774.md>), [json](<https://devfeed.tech/tags/json.md>), [map](<https://devfeed.tech/tags/map.md>), [maps](<https://devfeed.tech/tags/maps.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [projects](<https://devfeed.tech/tags/projects.md>), [projects-566](<https://devfeed.tech/tags/projects-566.md>), [pyodide](<https://devfeed.tech/tags/pyodide.md>), [pyodide-53](<https://devfeed.tech/tags/pyodide-53.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [python](<https://devfeed.tech/tags/python.md>), [python-1-294](<https://devfeed.tech/tags/python-1-294.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [service-workers-6](<https://devfeed.tech/tags/service-workers-6.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [urls](<https://devfeed.tech/tags/urls.md>), [urls-83](<https://devfeed.tech/tags/urls-83.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [webassembly-136](<https://devfeed.tech/tags/webassembly-136.md>)

### AI overview

Datasette Lite now runs a near server-side Datasette experience in the browser using Pyodide and service workers. URL parameters can select a Datasette release or GitHub reference, install plugins, load SQLite, JSON, CSV or SQL resources, and choose among 163 WebAssembly SQLite builds. Remote files need open CORS headers. A service worker intercepts page and asset requests; session IDs route each browser tab to its own Datasette instance, while a web worker preserves state that Pyodide in a service worker may lose after about 30 seconds. This makes shareable demos and bug reproductions possible without hosting a server. The author says the approach could suit other Python apps, though SQLite works more readily than PostgreSQL or MySQL in WebAssembly.

### Source excerpt

Datasette Lite is my port of the Datasette Python application to run directly in the browser using WebAssembly and Pyodide. I've released a complete rewrite of Datasette Lite using service workers, and it's now almost indistinguishable from the real server-side application. You can now do all of the following, using a carefully crafted URL to lite.datasette.io: Load client-side Datasette to browse any SQLite database, JSON file, CSV file or SQL script Select a released version of Datasette to load from PyPI Load a specific commit, tag, or branch name from the Datasette GitHub repository Pick from over 100 versions of SQLite to use with Datasette Install additional Datasette plugins from PyPI or URLs to wheel files, including JavaScript visualization tools The ability to load specific Datasette references, plugins, and SQLite versions makes this a fantastic tool for linking to demos of work-in-progress features or bug reproductions, without needing to spin up a full web server to serve that demo. As an example, consider the following URL: https://lite.datasette.io/?install=datasette-maplibre&url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/demo/capitals_and_countries%23map=0/4.2/180&color=continent Follow that link and, after a short loading screen, you'll find yourself on a page that looks like this: That's Datasette running the new datasette-maplibre plugin, loading up a database of GeoJSON shapes of countries and displaying both a combined map and individual boundary maps in a table. Let's break down that URL to see what it's doing: https://lite.datasette.io/ ?install=datasette-maplibre &url=https://.../demo.db &metadata=https://.../metadata.yml #/demo/capitals_and_countries%23map=0/4.2/180&color=continent The ?install=datasette-maplibre inst

## SvelteKit 3 is here

DevFeed: [SvelteKit 3 is here](<https://devfeed.tech/articles/sveltekit-3-is-here-63450.md>)

Original publisher: [Read original article](<https://svelte.dev/blog/sveltekit-3-is-here>)

Author: The Svelte team

Published: 2026-10-01T00:00:00Z

Content type: release

Language: en

Sources: [Svelte](<https://devfeed.tech/sources/svelte-blog.md>)

Topics: [Svelte](<https://devfeed.tech/topics/svelte.md>), [Submodules](<https://devfeed.tech/topics/submodules.md>), [Null-Safety](<https://devfeed.tech/topics/null-safety.md>), [async](<https://devfeed.tech/topics/async.md>)

Tags: [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [migration](<https://devfeed.tech/tags/migration.md>), [release](<https://devfeed.tech/tags/release.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [sveltekit](<https://devfeed.tech/tags/sveltekit.md>), [type-safety](<https://devfeed.tech/tags/type-safety.md>)

### AI overview

SvelteKit 3 is available with a migration command, updated configuration and import conventions, improved type safety and error handling, and changes to environment variables and service workers. Remote functions remain experimental and require Async Svelte.

### Source excerpt

Version 3.0 of SvelteKit, the official application framework for Svelte, is now available. If you've used earlier versions of SvelteKit, everything will feel very familiar -- it's the same framework with a little more polish, a little more type safety, and a little less junk. We've made migration as seamless as we can with the sv migrate command... npx sv migrate sveltekit-3 --tasks all --confirm ...which will automatically migrate as much of your codebase as possible, and generate a TODO list for everything else. (If you're agentically inclined, your robot friends will make short work of it.) To create a new app, run sv create: npx sv create my-new-app As with any major version bump there are a handful of breaking changes to be aware of, which are covered in the migration guide (or, more briefly, in the recent release candidate announcement). Quick highlights: configuration now lives in vite.config.ts instead of svelte.config.js the $lib alias is now #lib, making use of standard subpath imports environment variables are more powerful and easier to use service workers are less boilerplatey error handling is improved across the board Are remote functions ready yet? Not quite. But it's our top priority! Remote functions are a set of utilities for secure, efficient, type-safe client-server communication. You've likely seen some version of this idea in other frameworks, but we think you're going to prefer this one. Using them requires Async Svelte, which for now requires an experimental flag. Bear with us. Join us in Ljubljana next month This is as good a place as any to remind everyone that the next in-person Svelte Summit is taking place on November 19-20 in the lovely town of Ljubljana, Slovenia. Among other things it will be a celebration of Svelte's 10th birthday, and we'd love to share some cake with you.

## Web-Perf Wednesday 010 - Safari Keeps Scrolled Content in Place

DevFeed: [Web-Perf Wednesday 010 - Safari Keeps Scrolled Content in Place](<https://devfeed.tech/articles/web-perf-wednesday-010-safari-keeps-scrolled-content-in-place-58523.md>)

Original publisher: [Read original article](<https://csswizardry.com/2026/09/web-perf-wednesday-010-safari-keeps-scrolled-content-in-place/>)

Author: Harry Roberts

Published: 2026-09-23T11:00:00Z

Content type: article

Language: en

Sources: [CSS Wizardry](<https://devfeed.tech/sources/css-wizardry.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [devtools](<https://devfeed.tech/tags/devtools.md>), [http](<https://devfeed.tech/tags/http.md>), [performance](<https://devfeed.tech/tags/performance.md>), [safari](<https://devfeed.tech/tags/safari.md>), [scrolling](<https://devfeed.tech/tags/scrolling.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

This article reviews browser performance changes in Safari 27, including scroll anchoring that keeps visible content in place when material is inserted above it. It also notes tighter HTTP caching, static Service Worker routes, and Chrome DevTools improvements, with testing guidance for sites affected by scrolling and layout changes.

### Source excerpt

Safari 27 adds scroll anchoring, tighter HTTP caching, and static Service Worker routes, while Chrome improves performance tooling.

## WebKit Features for Safari 26.6

DevFeed: [WebKit Features for Safari 26.6](<https://devfeed.tech/articles/webkit-features-for-safari-26-6-49192.md>)

Original publisher: [Read original article](<https://webkit.org/blog/18178/webkit-features-for-safari-26-6/>)

Author: Jen Simmons

Published: 2026-07-27T18:00:52Z

Content type: release

Language: en

Sources: [WebKit](<https://devfeed.tech/sources/webkit.md>)

Topics: [WebKit](<https://devfeed.tech/topics/webkit.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [CSS](<https://devfeed.tech/topics/css.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [WebRTC](<https://devfeed.tech/topics/webrtc.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [css](<https://devfeed.tech/tags/css.md>), [ios-26](<https://devfeed.tech/tags/ios-26.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [news](<https://devfeed.tech/tags/news.md>), [safari](<https://devfeed.tech/tags/safari.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [webkit](<https://devfeed.tech/tags/webkit.md>), [webrtc](<https://devfeed.tech/tags/webrtc.md>)

### AI overview

Safari 26.6 adds support for passing options to WebAssembly streaming compilation paths, allowing WebAssembly modules to use JavaScript String Builtins without falling back from streaming compilation. The release also includes eight bug fixes covering CSS, networking, service workers, web extensions, and WebRTC, and is delivered through updates to supported Apple operating systems.

### Source excerpt

Safari 26.6 is here.

## Offline support and service workers

DevFeed: [Offline support and service workers](<https://devfeed.tech/articles/offline-support-and-service-workers-89161.md>)

Original publisher: [Read original article](<https://specification.website/spec/resilience/offline-support/>)

Author: Joost de Valk

Published: 2026-07-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>)

Tags: [devtools](<https://devfeed.tech/tags/devtools.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [kill-switch](<https://devfeed.tech/tags/kill-switch.md>), [lighthouse](<https://devfeed.tech/tags/lighthouse.md>), [optional](<https://devfeed.tech/tags/optional.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>)

### AI overview

A practical guide to using service workers for offline support in websites and applications. It covers a cached fallback page, resource-specific caching strategies, deployment pitfalls, and ways to verify or disable a worker.

### Source excerpt

A service worker can serve a cached offline fallback page when the network fails, keeping the site usable on flaky connections and turning hard failures into graceful ones.

## Harnessing the Power of Service Workers: Building Offline-Ready Web Apps

DevFeed: [Harnessing the Power of Service Workers: Building Offline-Ready Web Apps](<https://devfeed.tech/articles/harnessing-the-power-of-service-workers-building-offline-ready-web-apps-26512.md>)

Original publisher: [Read original article](<https://medium.com/engineering-housing/harnessing-the-power-of-service-workers-building-offline-ready-web-apps-135c338c349f?source=rss----3a69e32e2594---4>)

Author: Jitendra Kumar

Published: 2024-06-12T06:49:30Z

Content type: article

Language: en

Sources: [Housing.com](<https://devfeed.tech/sources/housing-com.md>)

Topics: [Web app](<https://devfeed.tech/topics/webapp.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [interception](<https://devfeed.tech/tags/interception.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [network](<https://devfeed.tech/tags/network.md>), [offline](<https://devfeed.tech/tags/offline.md>), [scope](<https://devfeed.tech/tags/scope.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [storage](<https://devfeed.tech/tags/storage.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [web](<https://devfeed.tech/tags/web.md>), [web-apps](<https://devfeed.tech/tags/web-apps.md>)

### AI overview

Service workers run separately from a page's main JavaScript thread and can intercept network requests to serve cached resources, enabling offline access. The excerpt distinguishes their Cache Storage from Local Storage and Session Storage, and contrasts programmable request handling and cache management with the browser's more passive HTTP cache. It outlines registration and scope, installation for caching assets, activation for cleanup, fetch handling, and page-to-worker messaging. Its example registers `/sw.js`, precaches selected files, removes other named caches on activation, serves a cache hit or fetches and caches a miss, and falls back to `/offline.html` on fetch failure. The text advises reloading after first registration so earlier requests can be cached. It claims offline access can improve experience and speed and reduce server requests; it does not discuss browser support or security considerations.

### Source excerpt

In the dynamic world of web development, where user experience reigns supreme, having a web application that functions seamlessly even in offline mode is no longer a luxury but a necessity. Enter service workers -- the unsung heroes behind the scenes, making this magic possible. In this blog post, we'll delve into the world of service workers, exploring what they are, how they work, and how you can harness their power to supercharge your web applications. What is a service worker ? At its core, a service worker is a script that runs in the background of a web application, separate from the main JavaScript thread. It acts as a proxy between your web page and the network, enabling a host of powerful features such as offline functionality. This means that even if the user loses internet connection, the service worker can still serve cached content, providing a seamless offline experience. How service worker caching is different than standard browser caching ? Location and Scope: Service Worker: JavaScript files running in the background, separate from the main browser thread. Browser Caching: Resources stored within the browser itself, part of the main browsing environment. 2. Control Over Network Requests: Service Worker: Provides fine-grained control over network requests, allowing interception and customized handling. Browser Caching: More passive, resources are stored and retrieved by the browser without direct developer intervention. 3. Offline Functionality: Service Worker: Enables creation of offline experiences by caching and serving resources even when offline. Browser Caching: Improves performance but doesn't inherently provide offline functionality. 4. Persistence and Management: Service Worker: Persistent and programmatically managed caches, controlled by developers. Browser Caching: Managed by the browser, with limited developer control over cache lifecycle. Where service worker data is stored ? Service worker caching is stored in a separate storage called

## Different remote and local resource URLs, with Service Workers!

DevFeed: [Different remote and local resource URLs, with Service Workers!](<https://devfeed.tech/articles/different-remote-and-local-resource-urls-with-service-workers-52102.md>)

Original publisher: [Read original article](<https://lea.verou.me/2017/10/different-remote-and-local-resource-urls-with-service-workers/>)

Author: Lea Verou

Published: 2017-10-30T00:00:00Z

Content type: article

Language: en

Sources: [Lea Verou's blog](<https://devfeed.tech/sources/lea-verou-s-blog.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [development](<https://devfeed.tech/tags/development.md>), [http](<https://devfeed.tech/tags/http.md>), [https](<https://devfeed.tech/tags/https.md>), [js](<https://devfeed.tech/tags/js.md>), [library](<https://devfeed.tech/tags/library.md>), [local](<https://devfeed.tech/tags/local.md>), [localhost](<https://devfeed.tech/tags/localhost.md>), [mavo](<https://devfeed.tech/tags/mavo.md>), [original](<https://devfeed.tech/tags/original.md>), [remote](<https://devfeed.tech/tags/remote.md>), [repo](<https://devfeed.tech/tags/repo.md>), [request](<https://devfeed.tech/tags/request.md>), [resource](<https://devfeed.tech/tags/resource.md>), [resources](<https://devfeed.tech/tags/resources.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [test](<https://devfeed.tech/tags/test.md>), [tips](<https://devfeed.tech/tags/tips.md>), [url](<https://devfeed.tech/tags/url.md>), [urls](<https://devfeed.tech/tags/urls.md>), [web](<https://devfeed.tech/tags/web.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

The author's Service Worker setup lets local Mavo development keep the normal remote URLs in HTML: on localhost, it intercepts matching Mavo requests, tries a local server URL with a cache-busting timestamp, and falls back to the original request if the local fetch fails. The author says this works more smoothly than earlier approaches, with caveats: the worker only takes effect on a cached page load, must be copied into each repository because of same-origin limits, and may need explanation for new contributors. Earlier options include manually switching URLs, which risks committing a broken local URL; an onerror fallback, which adds a failed request before loading remotely and exposes debug URLs; conditional JavaScript URL selection, which the author calls clunky; and gulp copying and watching, which requires remembering to run the watcher and maintaining copies. The excerpt also lists untested alternatives: .htaccess redirects, symbolic links, user scripts, and hosts-file changes.

### Source excerpt

I often run into this issue where I want a different URL remotely and a different one locally so I can test my local changes to a library. Sure, relative URLs work a lot of the time, but are often not an option. Developing Mavo is yet another example of this: since Mavo is in a separate repo from mavo.io (its website) as well as test.mavo.io (the testsuite), I can't just have relative URLs to it that also work remotely. I've been encountering this problem way too frequently pretty much since I started in web development. In this post, will describe all solutions and workarounds I've used over time for this, including the one I'm currently using for Mavo: Service Workers! The manual one Probably the first solution everyone tries is doing it manually: every time you need to test, you just change the URL to a relative, local one and try to remember to change it back before committing. I still use this in some cases, since us developers are a lazy bunch. Usually I have both and use my editor's (un)commenting shortcut for enabling one or the other: <script src="https://get.mavo.io/mavo.js"></script> <!--<script src="../mavo/dist/mavo.js"></script>--> However, as you might imagine, this approach has several problems, the worst of which is that more than once I forgot and committed with the active script being the local one, which resulted in the remote website totally breaking. Also, it's clunky, especially when it's two resources whose URLs you need to change. The JS one This idea uses a bit of JS to load the remote URL when the local one fails to load. <script src="http://localhost:8000/mavo/dist/mavo.js" onerror="this.src='https://get.mavo.io/mavo.js'"></script> This works, and doesn't introduce any cognitive overhead for the developer, but the obvious drawback is that it slows things down for the server since a request needs to be sent and fail before the real resource can be loaded. Slowing things down for the local case might be acceptable, even though undesirable,

## Boot your ajax app: Creating a splash screen with NProgress

DevFeed: [Boot your ajax app: Creating a splash screen with NProgress](<https://devfeed.tech/articles/boot-your-ajax-app-creating-a-splash-screen-with-nprogress-21208.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2013/12/nprogress-splash-screen/>)

Published: 2013-12-05T00:00:00Z

Content type: article

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [app startup](<https://devfeed.tech/topics/app-startup.md>), [Cache](<https://devfeed.tech/topics/cache.md>)

Tags: [ajax](<https://devfeed.tech/tags/ajax.md>), [app](<https://devfeed.tech/tags/app.md>), [backend](<https://devfeed.tech/tags/backend.md>), [boot](<https://devfeed.tech/tags/boot.md>), [caching](<https://devfeed.tech/tags/caching.md>), [code-splitting](<https://devfeed.tech/tags/code-splitting.md>), [lazy-loading](<https://devfeed.tech/tags/lazy-loading.md>), [loading](<https://devfeed.tech/tags/loading.md>), [progress](<https://devfeed.tech/tags/progress.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [resources](<https://devfeed.tech/tags/resources.md>), [screen](<https://devfeed.tech/tags/screen.md>), [server](<https://devfeed.tech/tags/server.md>), [service-workers](<https://devfeed.tech/tags/service-workers.md>), [spa](<https://devfeed.tech/tags/spa.md>), [splash-screen](<https://devfeed.tech/tags/splash-screen.md>), [startup](<https://devfeed.tech/tags/startup.md>), [templates](<https://devfeed.tech/tags/templates.md>)

### AI overview

The excerpt recommends optimizing single-page app startup first, since progress bars can be an antipattern, but describes a splash screen as a fallback to avoid showing the app assembling in pieces. The suggested sequence is to hide the app's main DOM container, show a progress indicator while JavaScript, templates, and backend data load, then reveal the app and hide the indicator when loading finishes. It presents NProgress as an option whose bar advances indefinitely after a simple start call; loading logic can advance it faster before completion. The excerpt begins to introduce a centered splash screen as an alternative when a progress indicator seems too easy to miss, but cuts off before explaining it.

### Source excerpt

Lorem ipsum dolor sit amet