Content-Type header not being rewritten properly.css-tree, esotope-hammerhead, and mime-db.uv.route() which allows the service worker to easily detect if the worker should route this request.importScripts("uv.bundle.js");
importScripts("uv.config.js");
importScripts(__uv$config.sw || "uv.sw.js");
const uv = new UVServiceWorker();
self.addEventListener("fetch", (event) => {
event.respondWith(
(async () => {
if (uv.route(event)) {
return await uv.fetch(event);
}
return await fetch(event.request);
})()
);
});
cache option when making a request.blob: URLs.uv.config.js file. This allows users to specify multiple servers that the service worker can choose from, improving reliability and failover.uv.client.js script was bundled with uv.bundle.js. In this version, uv.client.js is separate and needs to be included separately in any workflows that use it.uvPath export was the default export from the Ultraviolet module. In this version, uvPath is no longer the default export and needs to be imported explicitly.import { uvPath } from "@titaniumnetwork-dev/ultraviolet";
sw.js script that users can use as a starting point for their service worker.sw.js script, users must now import uv.bundle.js and uv.config.js in that order. This is because uv.config.js relies on uv.bundle.js, and the paths to these files cannot be hard-coded in the sw.js script.uv.config.js file to specify the paths to all the Ultraviolet scripts, including uv.bundle.js and uv.config.js.sw.js script in this Ultraviolet version:+ importScripts('./uv/uv.bundle.js');
+ importScripts('./uv/uv.config.js');
importScripts('./uv/uv.sw.js');
const sw = new UVServiceWorker();
self.addEventListener('fetch', (event) => event.respondWith(sw.fetch(event)));
uv.bundle.js script is built using Webpack, allowing users to easily bundle their own scripts and dependencies with Ultraviolet.