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 Apr 3, 2024. It is now read-only.
When identifying a code block as JavaScript with uppercase 'J' and 'S', the highlighting doesn't kick in as expected. The highlighting works fine on Github, which means it is easy to miss until after a release.
The work around is to change the language identifier to javascript (lowecase). Still, it is reasonable to expect it to be compatible with Github given that NPM supports Github flavoured markdown.
Here is an example (difference is apparent in source):
CamelCase WON'T be highlighted on NPM:
import'marky-markdown'
Lowercase WILL be highlighted on NPM:
import'marky-markdown'
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When identifying a code block as
JavaScript
with uppercase 'J' and 'S', the highlighting doesn't kick in as expected. The highlighting works fine on Github, which means it is easy to miss until after a release.The work around is to change the language identifier to javascript (lowecase). Still, it is reasonable to expect it to be compatible with Github given that NPM supports Github flavoured markdown.
Here is an example (difference is apparent in source):
CamelCase WON'T be highlighted on NPM:
Lowercase WILL be highlighted on NPM:
The text was updated successfully, but these errors were encountered: