fortes / metalsmith-code-highlight Goto Github PK

My main usecase is that I have <code> tags that I don't want marked up by this plugin, but I still want the highlight for other code blocks.

I was writing some <code> elements that I wanted inline. The relevant DOM structure is
<li>blah blah text <code>$ cowsay </code> more text </li>, which will still be highlighted, and the code gets marked up because the the sourcecode looks up all <code>. If I have subsequent <code> elements in that <li>, nothing happens to them; they won't have the hljs class (not sure why).

highlight.js says that it finds <pre><code> tags.

Why does the sourcecode select all code instead of 'pre > code'?

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Replaced the old Node.js version in your .nvmrc with the new one

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

On npm, latest version is not up to date. It requires highlight.js 9, which is no longer supported. Where version 10 is in use in this git repository. It produces the following error:

Version 9 of Highlight.js has reached EOL and is no longer supported.
Please upgrade or ask whatever dependency you are using to upgrade.
https://github.com/highlightjs/highlight.js/issues/2877

# package.json from https://registry.npmjs.org/metalsmith-code-highlight/-/metalsmith-code-highlight-1.1.0.tgz
# [...]
  "dependencies": {
    "highlight.js": "^9.12.0",
    "metalsmith-dom-transform": "^2.0.0"
  },
# [...] 

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Hi!
So if one use pandoc, this code:

```js
var int = 0;
```

will render to this HTML:

<pre class="js">
  <code>var int = 0;</code>
</pre>

which means getLanguage(element) will fail.

As I think this is a common setup, would you approve a PR for a getLanguage(element) that also looks into if element got a parent which is <pre> with a language class?

Hi @fortes,

Thanks for this metalsmith plugin. It currently supports HTML fragments, but not an entire HTML document (strips out DOCTYPE, html, head, and body tags). I will submit a pull request to you if you'd like to incorporate the change.