While I initially started using just one single HTML file for my tiddlers, I soon switched over to the nodeJS installation. This still has better benefits like: you can run the instance in Docker install tiddlywiki and its dependencies without messing around with your system you’ll get multiple “flat” files (.tid files are in plain text) you can apply sed, awk, bash foo to extract/modify data even if Tiddlywiki will be discontinued some day, you’ll still be able to import your notes in whatever note-taking syntax

There are a lot of nasty gotchas with unhandled rejections. That's why Node.js gives you a mechanism for globally handling unhandled rejections.

the Unix Philosophy is a crucial part of the patterns, opinions, and culture of Node.js

this in NodeJS global scope is the current module.exports object, not the global object

Secondly, whether this works is highly dependent on the module bundler. For example, in codesandbox, when bundling our app with Parcel (or Webpack or Rollup), this solution doesn’t work. However, when running this locally with Node.js and commonJS modules this workaround might work just fine.

browserify is a tool for compiling node-flavored commonjs modules for the browser.

Node doesn't have a DOM available. So in order to render HTML we use string concatenation instead. This has the fun benefit of being quite efficient, which in turn means it's great for server rendering!

Comparison to Node.js

Since most CommonJS packages you are importing are probably dependencies in node_modules, you may need to use @rollup/plugin-node-resolve:

k6 does not run in Node.js because it would perform poorly while running larger tests.Javascript is not generally well suited for high performance. It's a Go program - to achieve maximum performance - embedding a JavaScript runtime for running tests written in JavaScript.

Node.js Training

It’s a bit like chat roulette in that way