You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2018. It is now read-only.
I use some special characters (backticks for example) in published package description. npm site parses it as Markdown text. But they display as escaped HTML in package page like below:
It should not be parsed as Markdown.
The text was updated successfully, but these errors were encountered:
We're tracking this in our internal bug tracker. This one's been around a while and really has to get fixed. It's not our top priority, but we'll try to squeeze it in when we have a moment.
I use some special characters (backticks for example) in published package description. npm site parses it as Markdown text. But they display as escaped HTML in package page like below:
It should not be parsed as Markdown.
The text was updated successfully, but these errors were encountered: