remark-typescript

A remark plugin to transpile TypeScript code blocks.

• Installation
• Usage
  • Gatsby example
• API
  • remark().use(remarkTypescript[, options])
• Preserving unused imports
• License

Installation

npm install remark-typescript

Usage

import remark from 'remark';
import {remarkTypescript} from 'remark-typescript';

remark()
  .use(remarkTypescript)
  .process(...);

Gatsby example

// gatsby-config.js
const {remarkTypescript} = require('remark-typescript');

module.exports = {
  plugins: [
    {
      resolve: 'gatsby-plugin-mdx',
      options: {
        remarkPlugins: [remarkTypescript]
      }
    }
  ]
}

API

remark().use(remarkTypescript[, options])

Transform TypeScript code blocks to JavaScript and inserts them back into the page. Use options to affect the formatting or control which code blocks get transpiled.

options.prettierOptions

An object of options supplied to prettier.format when formatting the JS output. See Prettier's docs for more information.

import remark from 'remark';
import typescript from 'remark-typescript';

remark()
  .use(
    typescript,
    {
      prettierOptions: {
        semi: false,
        singleQuote: false
      }
    }
  )
  .process(...);

options.customTransformations

Custom transformations allow code and node manipulation to occur during the transpilation process. There are four code hook locations beforeTranspile, afterTranspile, beforeFormat and afterFormat. As well as one node manipulation callback that occurs after all text manipulation is complete.

Transformer Structure

Custom transformations take the following shape, note that every single property listed below is optional.

{
  code: {
    beforeTranspile: () => "",
    afterTranspile: () => "",
    beforeFormat: () => "",
    afterFormat: () => "",
  },
  node: () => {},
}

Code Transformer Signature

The code transformer functions all have the same signature, (code: string, meta?: string) => string. Code represents the source code at that point, and meta describes the meta string attached to the code block. Note, the meta string is optional. The decision to pass meta as a string as opposed to the node is that the intent is that nodes are immutable until the final node transformer. The returned string is then applied to the forward processes.

Node Transformer Signature

The node transformer as the signature (originalCodeNode, transpiledCodeNode): void where all mutations of the nodes happens in place on the object, so no return type is required. Full access to all properties is available here, and certain tasks can be done like cleaning up meta tags.

options.filter

The filter callback allows for fine-tuned selection of TypeScript blocks. By default, remark-typescript will visit all TypeScript code blocks in your site and insert the transformed and formatted JavaScript after each of them. This feature allows the author to choose which TypeScript code blocks to transform by returning true or false.

To keep migration easy, a helper function is included to return the wrapperComponent functionality.

isWrapped(options: {wrapperComponent: string}) MDX only

The isWrapped helper allows for easy filtering for code blocks only in a certain component. The option wrapperComponent is a string representing the name of the React component used to wrap code blocks that you wish to transform.

// gatsby-config.js
const {remarkTypescript, isWrapped} = require('remark-typescript');

module.exports = {
  plugins: [
    {
      resolve: 'gatsby-plugin-mdx',
      options: {
        remarkPlugins: [
          [
            remarkTypescript,
            {
              // configure the JSX component that the plugin should check for
              filter: isWrapped({wrapperComponent: 'CodeBlockWrapper'})
            }
          ]
        ]
      }
    }
  ]
};

In your MDX file, surround code blocks that you want to be transformed with their own pair of opening and closing JSX tags. The name of the component that you use here must match the wrapperComponent option that you passed along to this plugin.

import {CodeBlockWrapper} from '../components';

<CodeBlockWrapper>

```ts
// this code block will be transformed
```

</CodeBlockWrapper>

```ts
// this one will be ignored
```

Your wrapper component could include some additional logic, like allowing users to switch between the original and transformed code blocks. Check out Apollo's MultiCodeBlock component for an example of how to accomplish this.

options.throwOnError

Set throwOnError to true to throw when the transpilation step results in an error. By default, errors will be logged to the console and will not cause your build to fail.

Preserving unused imports

This plugin uses Babel to do the transpilation, and because of this, you might notice unused imports being removed from your transpiled JavaScript codeblocks. To avoid this behavior, you can use a // preserve-line directive on lines that you don't want to be removed from the transpiled version.

```ts
import gql from 'graphql-tag';
import {ApolloClient} from 'apollo-client'; // preserve-line

export const typeDefs = gql`
  type Query {
    posts: [Post]
  }
`;
```

License

MIT