Bootstrapping problem: packaging tsex

[Julian Gilbey <jdg@debian.org>]

Dear all,

I'm trying to update nbconvert, and there is a privacy patch to avoid
using cdnjs.cloudflare.com to download various libraries, but to
instead use a local copy.  One of the packages involved is
(node-)mermaid.  I'm looking at updating it (the version in unstable
is 8.14.0 and FTBFS, but the current version is 10.2.4).  There are a
*lot* of missing dependencies, unfortunately (so any help would be
much appreciated :).

One really tricky one is that it depends on a recent version of khroma
(bundled with the node-mermaid package).  But khroma now uses tsex to
build it; tsex is "A little CLI for making TypeScript packages,
cleanly and effortlessly."  But building tsex for Debian gives a
bootstrap problem:

tsex 2.2.4
  - build-depends on tsex ^2.1.0
  - which build-depends on tsex ^2.0.0
  - which build-depends on tsex ^1.1.5
  - which has:

  "devDependencies": {
    "@types/node": "^18.11.9",
    "atomically": "^2.0.0",
    "dettle": "^1.0.0",
    "esbuild": "^0.15.14",
    "rimraf": "^3.0.2",
    "ripread": "^2.0.1",
    "specialist": "^0.6.1",
    "tiny-readdir": "^2.0.0",
    "typescript": "^4.9.3",
    "watcher": "^2.0.0"
  }

Any suggestions of how one might handle this situation?

Best wishes,

   Julian