I’m afraid I’ve missed the bus as far as porting to Chrome/Edge/etc, for now.
Previously, I hesitated because Chrome’s API lacked modern promise/async/await interfaces to extension APIs, meaning I’d have had to either rewrite much of the extension logic as a 2010-style pyramid of doom, or vendor in Mozilla’s MPL’d WebExtensions shim.
Now, though, Google are going full steam ahead with Manifest V3, which brings these to the APIs, but as Google giveth, Google taketh away: there seems to be literally zero support for arbitrary code execution, even arbitrary code specified by the user. This would completely eliminate arbitrary tiddler formatting, which I consider one of the core features of the addon: as recently demonstrated [1] by amreus, it lets users write in features after the fact that I didn’t even anticipate.
There seems to be some vague interest in giving developers some of that power back in MV3, but for the time being, other addons intended to run user code, such as Tampermonkey, remain on MV2 [2].
I say I’ve missed the bus, because as of the 17th of this month, Google have stopped accepting new MV2 extensions on the web store, and I neglected reserve a cheeky spot by publishing a dummy addon or something before making a proper Chrome port.
Mozilla will be rolling out MV3 much more gently and slowly, preserving older APIs for now, so the Firefox version should work fine as is for the foreseeable future.
If I catch any news about some kind of sandboxed eval landing in MV3, I’ll be sure to give an update on the feasibility of a Chrome port.
For the time being though, it looks like TiddlyMarker will remain Firefox-exclusive.
Many thanks go out to the current users of the addon; the appreciation and 5-star reviews are great to see. This was a personal project to achieve a workflow I wanted, and even 24 users listed on AMO is 23 more than I ever expected.
[1] Add created field · Issue #3 · ylh/tiddlymarker · GitHub
[2] tampermonkey/manifest.json.google.com at master · Tampermonkey/tampermonkey · GitHub