Option to enable HeaderIds in marked

Is your feature request related to a problem? It would be helpful if you could jump directly to a give location the project page/README.md. Today tools like oclif create README.md files that contain e.g. a TOC that relies on HTML anchors. Websites like github or gitlab also support these anchors.

Describe the solution you’d like The marked package used by verdaccio can generate these anchors( as id=…) by setting marked.use({renderer,headerIds: true}) If there are usecases where headerIds are not welcome, i’d like to have a config option where i can enable them manually for my verdaccio installation.

[mknj]

just tried with docker run -p 4873:4873 verdaccio/verdaccio:5.x-next.

curl http://localhost:4873/-/verdaccio/package/readme/minipackage shows the header id

curl http://localhost:4873/-/verdaccio/package/readme/minipackage
<p>hallo</p>
<h1 id="some-header">some header</h1>
<p>demo</p>

but the webapp http://localhost:4873/-/web/detail/minipackage still has

<h1>some header</h1>

it seems that the webapp does some sanitize() too.

Is there some way to customize the webapp rendering?

[juanpicado]

@mknj master uses still yarn v1. The master only allows deps updates or urgent bug fixes. New development happens only on 5.x otherwise is crazy keep both on sync.

The 5.x-next on Docker hub yeah, it is old, I should remove that tag. I’m deploying here https://github.com/verdaccio/verdaccio/packages/13531 in every merge to 5.x