https://github.com/NaitLee/Tradit-TPL/blob/11129a328a6033d84a331e982a3957b3af003cea/tradit-constants.ts#L3

you'd better use __dirname to tell where your tpl is. It's neater, but also your folder may have a different name when downloaded.

https://github.com/NaitLee/Tradit-TPL/blob/11129a328a6033d84a331e982a3957b3af003cea/plugin.ts#L20

__dirname is a symbol, you shouldn't surround it with quotes

The code can work.

Though I want to make following changes, for less overhead ("pre-mature optimization"), or at least to try out new things:

• Implement most macros in WebAssembly, with AssemblyScript. Notably non-async & trivial ones.

  • Sync & trivial e.g. add, replace, urlvar
  • Async e.g. %list% (symbols are also macros here)

• Only optimize macro if all its parameters are "known"

  • like {.replace|a|b|c|d|abc.} and {.add|1|{.add|1|1.}.}
  • but not {.replace|a|{.urlvar|b.}|c|d|abc.}

The bad side:

• Regular Expressions used in serializer are potentially buggy.
• Many features are not implemented: special:alias etc. etc.
• Should harden security more.
• No document yet.
• No real "use cases" yet, i.e. need a good template to show off :)

... These will be done step by step.

Some dev "flags":

• A custom configuration page, like HFS Admin
  • Of course security will be considered
• Extended features (for templates) to provide flexibility, but compatible to HFS 2.4
  • something like [special:strings;zh-CN] to do better backend localization (when see HTTP header Accept-Language: zh-CN)
  • optional feature flags in section [special:features] to request different behavior. Example:
    • no-sort for by default preventing backend from sorting file list (to save resource) (in this case browser/client do it)
• Some good templates to make use of these

Not in a hurry. But wouldn't it be great?