feat: marked extensions

[nobkd]

• resolve Allow adding Marked Extensions in NueJS #182

WIP/POC implementation for marked extension loading.

Description

The default file to load from is marked.config.js but this can be changed using the marked_config key in site.yaml.
The provided file path currently has to be relative to the root folder of the project / the root passed to nue command

The config js file has to be of format:

// e.g. imports

export default [ // has to be an array
  // initialize marked extensions with functions / own objects here
]

If no file is found, the import() function silently returns an empty object which, on unpacking, results in an empty list for marked_extensions variable

TODO

• exclude marked config file from output folder
• add tests

Notes

• https://marked.js.org/using_pro#use

Maybe allow additional renderers with the following?

marked.use({
 extensions: [
   //...
 ]
})

[tipiirai]

Seems legit. This should only cover extensions that are not possible to implement as Nuemark extensions/tags. Footnote is probably the only one. Anything else?

[nobkd]

Well, you can also add all the other marked extensions.
It is sometimes easier to just use an existing package instead of re-building stuff yourself.

e.g.

• extended tables syntax
• footnotes, smartypants (lite) (as it was removed from the base package)
• katex could also be interesting for some use cases
• etc.

https://marked.js.org/using_advanced#extensions

---

Still WIP, as I have to do the todos, and want to use joinRootPath (or changed name) to import the file.

---

BTW, I think, this config isn't needed, as the options are deprecated (smartypants, headerIds, mangle) or nonexistent (smartLists at least it's not in this table):
https://github.com/nuejs/nue/pull/230/files#diff-9aaf075b4e5c776d59c27ef6c62e9c1079673f706482643126f348d7c6550cdfR9-R14

[nobkd]

Note

I'm not sure, if the config file might be better to be implemented with name nue.config.js (or changeable in site.yaml) with option marked (or similar), so that other js-required options can be implemented, e.g. some lightningcss configs (see #220) 🤷.

[tipiirai]

I've been hesitant to merge this, even when completed, due to increasing dependency to Marked, which is not my favorite parser.

[nobkd]

Closing because of upcoming nuemark version, that doesn't depend on marked anymore