pmtiles-swarm 0.24.0 → 0.24.2

package/CHANGELOG.md

@@ -7,6 +7,36 @@
 ### 🐞 Bug fixes
 - _...Add new stuff here..._
 
+## 0.24.2
+### 🐞 Bug fixes
+- **An empty `publicUrl` was read as an empty base rather than as no setting.** `??` treats only
+  null and undefined as absent, so `"publicUrl": ""` — which is how an operator naturally writes
+  "I do not want this" into a key already in the file — produced URLs like
+  `/archives/<hash>/{z}/{x}/{y}.pbf`. Those half-work, which is the trap: a browser resolves them
+  against the TileJSON it just fetched and renders perfectly, while everything needing an absolute
+  URL quietly gets something unusable — a torrent client handed the `torrent` link, another node
+  syncing from the feed. Empty and whitespace now mean unset, and the base falls back to the
+  request, which is what a node syncing internally by IP depends on.
+
+## 0.24.1
+### 🐞 Bug fixes
+- **Takes pmtiles-torrent 0.4.5, which stops a torrent that is not ready yet reporting a corrupt
+  one.** Reading a piece from an archive whose metadata had not arrived — or that was still checking
+  what is on disk, which is how a resync starts — came back as `invalid piece index in slot list`.
+  The piece count is zero until metadata lands, so every index is out of range including the valid
+  ones, and what is really "ask again in a moment" arrived under a name that reads as a damaged
+  archive. Head warming took that at its word and applied its full doubling backoff, so an archive
+  sat unservable for minutes on a node that was downloading it at 60 MiB/s throughout.
+
+  The floor is raised rather than the range widened, because `^0.4.2` already permitted 0.4.5 and
+  the lockfile is what a deployment installs from: `npm ci` would have kept fetching 0.4.2 and none
+  of this would have reached a node.
+
+  Worth knowing how much rides on that single read. The PMTiles v3 specification requires the root
+  directory to lie within the first 16,384 bytes, so a 16 KiB read at offset 0 fetches the header
+  and the root directory together — one piece, after which the archive is servable. A mirror is
+  unservable until exactly that read succeeds.
+
 ## 0.24.0
 ### ✨ Features and improvements
 - **A mirror now inherits the archive summary from the feed it follows.** `renderItem` has always

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmtiles-swarm",
-  "version": "0.24.0",
+  "version": "0.24.2",
   "description": "BitTorrent distribution for PMTiles map archives: create torrents, watch folders, publish and subscribe to RSS feeds, and seed through qBittorrent or an embedded client",
   "type": "module",
   "main": "src/index.js",
@@ -46,7 +46,7 @@
     "maplibre-gl": "^6.2.0",
     "parse-torrent": "^11.0.24",
     "pmtiles": "^4.4.1",
-    "pmtiles-torrent": "^0.4.2",
+    "pmtiles-torrent": "^0.4.5",
     "webtorrent": "^3.0.21"
   },
   "engines": {

package/src/api.js

@@ -213,8 +213,21 @@ export function createApp({
    * @param {import('express').Request} req - The request.
    * @returns {string} - Base URL without a trailing slash.
    */
-  const baseUrl = (req) =>
-    (config.publicUrl ?? `${req.protocol}://${req.host}`).replace(/\/$/, '');
+  const baseUrl = (req) => {
+    // An empty publicUrl means "not set", not "use an empty base".
+    //
+    // `??` reads only null and undefined as absent, so `"publicUrl": ""` --
+    // which is how an operator naturally writes "I do not want this" in a JSON
+    // file that already has the key -- produced a base of "" and URLs like
+    // `/archives/<hash>/{z}/{x}/{y}.pbf`. Those half-work, which is the worst
+    // of both: a browser resolves them against the TileJSON it fetched and
+    // renders perfectly, while every consumer that needs an absolute URL --
+    // a torrent client handed the `torrent` link, another node syncing from
+    // the feed -- silently gets something it cannot use.
+    const configured = String(config.publicUrl ?? '').trim();
+    const base = configured || `${req.protocol}://${req.host}`;
+    return base.replace(/\/$/, '');
+  };
 
   /**
    * Whether an archive should answer a missing tile with 404 rather than 204.