styling markdown code snippets with prismjs



~7 min read


1215 words

There are a number of different syntax highlighters for Javascript, but the one I’ve been using lately is PrismJS (due in large part to its great Gatsby support).

I use PrismJS’s highlighting primarily within the context of writing Markdown posts (like this one) on my Gatsby site.

Taking advantage of the different tools, however, requires adding additional detials to code that might otherwise not be there.

PrismJS has a ton of features, but understanding how to use them was not immediately intuitive to me.

This post is mostly an exploration of working through the Gatsby PrismJS Plugin, its README, and documentation for PrismJS itself. It’s meant as a guide for my future self (and anyone else who might use PrismJS with Gatsby)

Some of the features I’ve explored so far include:

  1. Code Titles
  2. Language Support
  3. Line Highlighting
  4. Line Numbering
  5. Inline Code Styling
  6. Diff Highlighting

Code Titles

// ... code goes here

Update: Continuing to play around with titles and noticing a few things:

  1. By default, the title can only be one word, however, this limit can be avoided using the non-breaking space encoding:  , e.g., lang:title=word second

  2. You can wrap your title in quotations, however, I find these unhelpful generally as:

    • a. they appear in the title
    • b. they do not help with multiple words (i.e. they don’t create a single title - for that, you still need the non-breaking space).

    e.g., lang:title="quoted-title"

Using with Gatsby: Gatsby Remark Code Titles


PrismJS will try to auto-detect which language is used. As the author, you can define the language by placing it in at the top of the code snippet.

For example:

const meaningOfLife = 42;

Here, we’re telling the code snippet to use javascript the language.

Supported PrismJS languages


Line highlighting allows specific lines to be highlighted in the code block.

There are several different options for this, but all of them require that additional CSS is added to your style sheet since the mechanism by which it works is to add a new class to the indicated lines. The Gatsby docs have a nice example, particularly if your PrismJS theme is solarized-light

Also check out the plugin README for details on the different ways to highlight row(s) in code snippets. These include:

  1. highlight-line to highlight the current line
  2. to highlight the enxt line
  3. and highlight-end to highlight a span of lines
  4. will highlight the next line and 4th through 6th lines relative to where the comment is included.

The code snippet below comes directly from the README referenced above. It demonstrates all of these in practice.

Of note, , , highlight-end, and are treated as if the lines do not exist by the renderer.

So - whereas when writing the code snippet, there’s a line between super(props) and this.state = ..., when rendered the latter immediately follows the former without a new line space.

class FlavorForm extends React.Component {
  constructor(props) {    super(props);
    this.state = {value: 'coconut'};
    this.handleChange = this.handleChange.bind(this);
    this.handleSubmit = this.handleSubmit.bind(this);

  handleChange(event) {

  handleSubmit(event) {    alert('Your favorite flavor is: ' + this.state.value);    event.preventDefault();  }
  render() {
    return (
      <form onSubmit={this.handleSubmit}>        <label>
          Pick your favorite flavor:
          <select value={this.state.value} onChange={this.handleChange}>            <option value="grapefruit">Grapefruit</option>            <option value="lime">Lime</option>            <option value="coconut">Coconut</option>            <option value="mango">Mango</option>          </select>        </label>
        <input type="submit" value="Submit" />
      </form>    );

Line Hiding

This is the exact same syntax as line highlighting, but with instead of highlight-line, etc.

See the documentation for more info.

This is often used in conjunction with embedding snippets.

Line Numbering

To indicate that you want to use numberlines in a snippet you will need to:

  1. Configure a global setting (in Gatsby, this would be adding showNumberLines to the resolver for the plugin in your gatsby-config.js
  2. Indicate it for a specific snippet if you want something other than what’s set in the global config
  3. Provide styling for the numbers

For more on adding line numbers, see the Gatsby plugin docs

Once all of this is setup, adding line numbers can be done by noting it at the top of the snippet with {numberLines: true}. For example:

;```javascript{numberLines: true}
const meaningOfLife = 42;

Alternatively, you can start at a specified line number (in this case, line 5):

;```javascript{numberLines: 5}
const meaningOfLife = 42;

Inline Code

Gatsby’s PrismJS plugin also allows for styling of inline code blocks (single ticks) versus code fences (```).

To do this, set an inlineCodeMarker in your gatsby-config:

    resolve: `gatsby-remark-prismjs`,
    options: {
        inlineCodeMarker: '>',

The recommendation is to use a non-ASCII character, such as the > recommended in the plugin (it’s useful to use something that’s not too esoteric otherwise it will be difficult to actually use).

Once done, you can write an inline code like “css> .some-class { background-color: red }” (using ticks instead of the quotes) to get it styled as CSS, like so: .some-class { background-color: red }.

Alternatively, javascript can be done with “js> const variable = 42;”, like so: const variable = 42;.

One thing I noticed while playing with the inline code styles is the styles will be applied similarly as to a fenced code block. Specifically, I noticed this because of the white-space attribute in the solarized-light theme is white-space: pre.

As a result, if any of the inline block would break on a line, the entire line was moved to the next line. This is different from standard <p> tag styling (where each word is treated as an independent token and a new line can occur at any point). Refer to MDN for more on the white-space attribute.

I didn’t like this behavior and wanted inline code to behave more like normal text. The fix was a relatively minor CSS adjustment in the end.

The big difference between the code blocks and inline code was the former was wrapped in <pre> tags, whereas inline code was not. So, I just needed a specific rule to target this kind of element. Mine looked like:

/* Inline code */
:not(pre) > code[class*="language-"] {
  white-space: normal;

With that in place, I made sure that I was importing my code.css into my gatsby-browser file:

import "./src/stylesheets/_reset.css"
import "./src/stylesheets/global.css"
import "./src/stylesheets/code.css"

import "prismjs/plugins/command-line/prism-command-line.css"
import "prismjs/plugins/line-numbers/prism-line-numbers.css"
import "prismjs/plugins/line-highlight/prism-line-highlight.css"
import "prismjs/themes/prism-solarizedlight.css"

With that done, my inline code was once again breaking as expected.

Diff Highlighting

This is more calling out that diff is a language in PrismJS and can be used to notate changes between snippets.

-    resolve: `old-plugin`,
+    resolve: `gatsby-remark-prismjs`,
    options: {
        inlineCodeMarker: '>',

Normally, PrismJS also enables several other features such as language specific diffs (instead of just diff, it’s diff-javascript for example), and diff highlighting.

See the PrismJS page for more specifics.

I plan on investigating these further in the future to see what CSS I’m missing with my Gatsby site that is preventing this styling.


There’s an example site for using snippets:

Related Posts
  • Writing Markdown Diffs and Adventures In Open-Source

  • Hi there and thanks for reading! My name's Stephen. I live in Chicago with my wife, Kate, and dog, Finn. Want more? See about and get in touch!