Under TiddlyMap, 'vis' became 'vis-network', but

1

…but I’m still getting an error:

Error: Cannot find module ‘$:/plugins/felixhayashi/vis/vis.js’

Some more detail:

At: GitHub - felixhayashi/TW5-TiddlyMap: Map drawing and topic visualization for your wiki · GitHub

…a few months ago, part of the instructions said to add, under “tiddlywiki.info”:

   "felixhayashi/tiddlymap",
   "felixhayashi/vis",
   "felixhayashi/hotzone",
   "felixhayashi/topstoryview"

Now, I read that has changed to

  "felixhayashi/vis-network",

…so that’s what I’ve installed, but.

Should I be using both? Or, am I overlooking something?

Thanks.

2

Little update: I tried just copying my past ‘TW5-Vis.js-master’ over to my newer setup, and adjusting ‘tiddlywiki.info’:

“plugins”: [
[…]
“felixhayashi/tiddlymap”,
“felixhayashi/vis”,
“felixhayashi/vis-network”,
“felixhayashi/hotzone”,
“felixhayashi/topstoryview”

So, “vis” and “vis-network” are both there. That hasn’t made any change; the tiddlywiki error is unchanged, referring to the inability to find vis.js.

For whatever that’s worth.

3

Oops, should have included the error I’m seeing.

Error executing boot module $:/plugins/felixhayashi/tiddlymap/js/lib/utils/tmap: {“code”:“MODULE_NOT_FOUND”,“requireStack”:[“/usr/lib64/node_modules/tiddlywiki/boot/boot.js”,“/usr/lib64/node_modules/tiddlywiki/tiddlywiki.js”]}

node:internal/modules/cjs/loader:998
throw err;
^

Error: Cannot find module ‘$:/plugins/felixhayashi/vis/vis.js’
Require stack:

  • /usr/lib64/node_modules/tiddlywiki/boot/boot.js
  • /usr/lib64/node_modules/tiddlywiki/tiddlywiki.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
    at Module._load (node:internal/modules/cjs/loader:841:27)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at $tw.modules.execute ($:/boot/boot.js:867:11)
    at require ($:/boot/boot.js:826:24)
    at $:/plugins/felixhayashi/tiddlymap/js/lib/utils/tmap:11:34
    at Script.runInContext (node:vm:141:12)
    at Script.runInNewContext (node:vm:146:17)
    at Object.runInNewContext (node:vm:306:38)
4

Ah. For our seats-of-chairs audience, here, I found my problem.

I didn’t build my setup on Gentoo… quite. I built it initially on Ubuntu; then For Reasons, started copy-and-pasting instances onto the “real” host, the Gentoo box; then tried to do updates (i.e., the newer version of TiddlyMap) onto an image of the “live” setting.

That copy and paste into a different runspace worked fine as long as it was only running, but fell apart when it was used as an update platform.

1 Like