npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@bendtherules/prism-react-renderer

v1.2.2

Published

*Fork of prism-react-renderer with hooks* Renders highlighted Prism output using React

Downloads

5

Readme

Maintenance Status

This is a fork of prism-react-renderer with hooks like useHighlight.

Why?

Maybe you need to render some extra UI with your Prismjs-highlighted code, or maybe you'd like to manipulate what Prism renders completely, or maybe you're just using Prism with React and are searching for an easier, global-pollution-free way?

Then you're right where you want to be!

How?

This library tokenises code using Prism and provides two ways - a hook and a small render-props-driven component to quickly render it out into React. This is why it even works with React Native! It's bundled with a modified version of Prism that won't pollute the global namespace and comes with a couple of common language syntaxes.

(There's also an escape-hatch to use your own Prism setup, just in case)

It also comes with its own VSCode-like theming format, which means by default you can easily drop in different themes, use the ones this library ships with, or create new ones programmatically on the fly.

(If you just want to use your Prism CSS-file themes, that's also no problem)

Table of Contents

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's dependencies:

# npm
npm install --save @bendtherules/prism-react-renderer
# yarn
yarn add @bendtherules/prism-react-renderer

This package also depends on react. Please make sure you have those installed as well.

Usage

Try it out in the browser

Using Component

import React from "react";
import { render } from "react-dom";
import Highlight, { defaultProps } from "prism-react-renderer";

const exampleCode = `
(function someDemo() {
  var test = "Hello World!";
  console.log(test);
})();

return () => <App />;
`;

render(
  <Highlight {...defaultProps} code={exampleCode} language="jsx">
    {({ className, style, tokens, getLineProps, getTokenProps }) => (
      <pre className={className} style={style}>
        {tokens.map((line, i) => (
          <div {...getLineProps({ line, key: i })}>
            {line.map((token, key) => (
              <span {...getTokenProps({ token, key })} />
            ))}
          </div>
        ))}
      </pre>
    )}
  </Highlight>,
  document.getElementById('root')
);

<Highlight /> is the main component exposed by this package, as inspired by downshift.

It also exports a defaultProps object which for basic usage can simply be spread onto the <Highlight /> component or useHighlight hook. It also provides some default theming.

It doesn't render anything itself, it just calls the render function and renders that. "Use a render prop!"! <Highlight>{highlight => <pre>/* your JSX here! */</pre>}</Highlight>

Using hooks

import React from "react";
import { render } from "react-dom";
import { useHighlight, defaultProps } from "@bendtherules/prism-react-renderer";

const exampleCode = `
(function someDemo() {
  var test = "Hello World!";
  console.log(test);
})();

return () => <App />;
`;

function HighlightConsumer() {
  const {
    className,
    style,
    tokens,
    getLineProps,
    getTokenProps,
  } = useHighlight({
    ...defaultProps,
    code: exampleCode,
    language: "jsx",
  });

  return (
    <pre className={className} style={style}>
      {tokens.map((line, i) => (
        <div {...getLineProps({ line, key: i })}>
          {line.map((token, key) => (
            <span {...getTokenProps({ token, key })} />
          ))}
        </div>
      ))}
    </pre>
  );
}

render((
  <HighlightConsumer />,
  document.getElementById('root')
);

DefaultRenderer

You'll very likely end up changing the rendering logic to suit your usecase, but this is just a convenient component to reuse the default rendering logic seen above.
(To be honest, it also helps in testing within the package)

So, if you want to write the above code examples in a shorter way (but without any customization), you can use -

import React from "react";
import { render } from "react-dom";
import Highlight, {DefaultRenderer, useHighlight, defaultProps } from "prism-react-renderer";

// 1. using component -

render(
  <Highlight {...defaultProps} code={exampleCode} language="jsx">
    {(input) => (
      <DefaultRenderer {...input}/>
    )}
  </Highlight>,
  document.getElementById('root')
);


// 2. Or, using hooks -

function SomeComponent() {
  const input = useHighlight({
    ...defaultProps,
    code: exampleCode,
    language: "jsx",
  });

  return  <DefaultRenderer {...input}/>
}

render(<SomeComponent />, document.getElementById('root'));

Line Numbers

Add line numbers to your highlighted code blocks using the index parameter in your line.map function:

For example, if you were using styled-components, it could look like the following demo.

Demo with styled-components

import React from "react";
import styled from "styled-components";
import Highlight, { defaultProps } from "prism-react-renderer";
import theme from "prism-react-renderer/themes/nightOwl";

const exampleCode = `
import React, { useState } from "react";

function Example() {
  const [count, setCount] = useState(0);

  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => setCount(count + 1)}>
        Click me
      </button>
    </div>
  );
}
`.trim();

const Pre = styled.pre`
  text-align: left;
  margin: 1em 0;
  padding: 0.5em;
  overflow: scroll;
`;

const Line = styled.div`
  display: table-row;
`;

const LineNo = styled.span`
  display: table-cell;
  text-align: right;
  padding-right: 1em;
  user-select: none;
  opacity: 0.5;
`;

const LineContent = styled.span`
  display: table-cell;
`;

const WithLineNumbers = () => (
  <Highlight {...defaultProps} theme={theme} code={exampleCode} language="jsx">
    {({ className, style, tokens, getLineProps, getTokenProps }) => (
      <Pre className={className} style={style}>
        {tokens.map((line, i) => (
          <Line key={i} {...getLineProps({ line, key: i })}>
            <LineNo>{i + 1}</LineNo>
            <LineContent>
              {line.map((token, key) => (
                <span key={key} {...getTokenProps({ token, key })} />
              ))}
            </LineContent>
          </Line>
        ))}
      </Pre>
    )}
  </Highlight>
);

export default WithLineNumbers;

Basic Props

This is the list of props that you should probably know about. There are some advanced props below as well.

Most of these advanced props are included in the defaultProps.

children

function({}) | required

This is called with an object. Read more about the properties of this object in the section "Children Function".

language

string | required

This is the language that your code will be highlighted as. You can see a list of all languages that are supported out of the box here. Not all languages are included and the list of languages that are currently is a little arbitrary. You can use the escape-hatch to use your own Prism setup, just in case, or add more languages to the bundled Prism.

code

string | required

This is the code that will be highlighted.

Advanced Props

theme

PrismTheme | required; default is provided in defaultProps export

If a theme is passed, it is used to generate style props which can be retrieved via the prop-getters which are described in "Children Function".

A default theme is provided by the defaultProps object.

Read more about how to theme react-prism-renderer in the section "Theming".

Prism

PrismLib | required; default is provided in defaultProps export

This is the Prismjs library itself. A vendored version of Prism is provided (and also exported) as part of this library. This vendored version doesn't pollute the global namespace, is slimmed down, and doesn't conflict with any installation of prismjs you might have.

If you're only using Prism.highlight you can choose to use prism-react-renderer's exported, vendored version of Prism instead.

But if you choose to use your own Prism setup, simply pass Prism as a prop:

// Whichever way you're retrieving Prism here:
import Prism from 'prismjs/components/prism-core';

<Highlight Prism={Prism} {/* ... */} />

Children Function

This is where you render whatever you want to based on the output of <Highlight />. You use it like so:

const ui = (
  <Highlight>
    {highlight => (
      // use utilities and prop getters here, like highlight.className, highlight.getTokenProps, etc.
      <pre>{/* more jsx here */}</pre>
    )}
  </Highlight>
);

The properties of this highlight object can be split into two categories as indicated below:

state

These properties are the flat output of <Highlight />. They're generally "state" and are what you'd usually expect from a render-props-based API.

| property | type | description | | ----------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------- | | tokens | Token[][] | This is a doubly nested array of tokens. The outer array is for separate lines, the inner for tokens, so the actual content. | | className | string | This is the class you should apply to your wrapping element, typically a <pre> |

A "Token" is an object that represents a piece of content for Prism. It has a types property, which is an array of types that indicate the purpose and styling of a piece of text, and a content property, which is the actual text.

You'd typically iterate over tokens, rendering each line, and iterate over its items, rendering out each token, which is a piece of this line.

prop getters

See Kent C. Dodds' blog post about prop getters

These functions are used to apply props to the elements that you render. This gives you maximum flexibility to render what, when, and wherever you like.

You'd typically call these functions with some dictated input and add on all other props that it should pass through. It'll correctly override and modify the props that it returns to you, so passing props to it instead of adding them directly is advisable.

| property | type | description | | --------------- | -------------- | ----------------------------------------------------------------------------------------------------- | | getLineProps | function({}) | returns the props you should apply to any list of tokens, i.e. the element that contains your tokens. | | getTokenProps | function({}) | returns the props you should apply to the elements displaying tokens that you render. |

getLineProps

You need to add a line property (type: Token[]) to the object you're passing to getLineProps; It's also advisable to add a key.

This getter will return you props to spread onto your line elements (typically <div>s).

It will typically return a className (if you pass one it'll be appended), children, style (if you pass one it'll be merged). It also passes on all other props you pass to the input.

The className will always contain .token-line.

getTokenProps

You need to add a token property (type: Token) to the object you're passing to getTokenProps; It's also advisable to add a key.

This getter will return you props to spread onto your token elements (typically <span>s).

It will typically return a className (if you pass one it'll be appended), children, style (if you pass one it'll be merged). It also passes on all other props you pass to the input.

The className will always contain .token. This also provides full compatibility with your old Prism CSS-file themes.

Theming

The defaultProps you'd typically apply in a basic use-case, contain a default theme. This theme is duotoneDark.

While all classNames are provided with <Highlight />, so that you could use your good old Prism CSS-file themes, you can also choose to use react-prism-renderer's themes like so:

import dracula from 'prism-react-renderer/themes/dracula';

<Highlight theme={dracula} {/* ... */} />

These themes are JSON-based and are heavily inspired by VSCode's theme format.

Their syntax, expressed in Flow looks like the following:

{
  plain: StyleObj,
  styles: Array<{
    types: string[],
    languages?: string[],
    style: StyleObj
  }>
}

The plain property provides a base style-object. This style object is directly used in the style props that you'll receive from the prop getters, if a theme prop has been passed to <Highlight />.

The styles property contains an array of definitions. Each definition contains a style property, that is also just a style object. These styles are limited by the types and languages properties.

The types properties is an array of token types that Prism outputs. The languages property limits styles to highlighted languages.

When converting a Prism CSS theme it's mostly just necessary to use classes as types and convert the declarations to object-style-syntax and put them on style.

FAQ

By default prism-react-renderer only includes an arbitrary subset of the languages that Prism supports. You can add support for more by including their definitions from the main prismjs package:

import Prism from "prism-react-renderer/prism";

(typeof global !== "undefined" ? global : window).Prism = Prism;

require("prismjs/components/prism-kotlin");
require("prismjs/components/prism-csharp");

prism-react-renderer still returns you all proper classNames via the prop getters, when you use it. By default however it uses its new theming system, which output a couple of style props as well.

If you don't pass theme to the <Highlight /> component it will default to not outputting any style props, while still returning you the className props, like so:

<Highlight
  {...defaultProps}
  code={exampleCode}
  language="jsx"
  theme={undefined}
>
  {highlight => null /* ... */}
</Highlight>

Since the default theme and the vendored Prism library in prism-react-renderer come from defaultProps, if you wish to pass your own Prism library in, and not use the built-in theming, you simply need to leave it out to allow your bundler to tree-shake those:

import Highlight from "prism-react-renderer";
import Prism from "prismjs"; // Different source

<Highlight Prism={Prism} code={exampleCode} language="jsx">
  {highlight => null /* ... */}
</Highlight>;

You can also import the vendored Prism library on its own:

import { Prism } from "prism-react-renderer";
// or
import Prism from "prism-react-renderer/prism";

LICENSE

MIT

Maintenance Status

Active: Formidable is actively working on this project, and we expect to continue for work for the foreseeable future. Bug reports, feature requests and pull requests are welcome.