marked dependency causes problems with skypack

...and maybe other CDNs or build setups.

basically marked seems to result in this from skypack:

> Failed to load node_modules/marked/bin/marked.js
> Unexpected token (1:0) in marked/bin/marked.js

which makes little sense since it has no reason to try import the `bin` file. marked correctly points the main file (and via export maps) to their ESM bundle.

Check the package.json for the marked dependency and its export maps. Look at how skypack or other CDNs resolve imports, especially for bin files. Investigate the build setup in relit to see where marked is imported and how it's bundled. Test with a minimal reproduction to confirm the issue.

Vom Indexierungsmodell aus dem Issue-Text verfasst.