# @stackline/remark > unified processor with support for parsing markdown input and serializing markdown as output. [](https://www.npmjs.com/package/@stackline/remark) [](https://github.com/alexandroit/stackline-remark) [](https://github.com/alexandroit/stackline-remark) [](https://alexandro.net/docs/vanilla/remark/) [](https://www.reddit.com/r/Stackline/) **[Documentation](https://alexandro.net/docs/vanilla/remark/)** | **[npm](https://www.npmjs.com/package/@stackline/remark)** | **[Issues](https://github.com/alexandroit/stackline-remark/issues)** | **[Repository](https://github.com/alexandroit/stackline-remark)** **Current package version:** `1.0.2` --- ## Why this package? `@stackline/remark` is the Stackline-maintained distribution of `remark@14.0.3`. It is an independent continuation of [remark](https://github.com/remarkjs/remark); original authors and licenses remain credited below. ## Compatibility | Item | Value | | :--- | :--- | | Package | `@stackline/remark@1.0.2` | | API target | `remark@14.0.3` | | Supported Node.js | `See supported framework requirements` | | License | `MIT` | | Module type | `module` | | Main entry | `index.js` | | Types | `index.d.ts` | | Runtime dependencies | `unified, @types/mdast, remark-parse, remark-stringify` | ## Installation ```bash npm install @stackline/remark ``` Preserve existing imports and plugin resolution with an npm alias: ```bash npm install remark@npm:@stackline/remark ``` ## Usage and API reference ### remark **[unified][]** processor with support for parsing markdown input and serializing markdown as output. ## Contents * [What is this?](#what-is-this) * [When should I use this?](#when-should-i-use-this) * [Install](#install) * [Use](#use) * [API](#api) * [`remark()`](#remark-1) * [Examples](#examples) * [Example: checking markdown](#example-checking-markdown) * [Example: passing options to `remark-stringify`](#example-passing-options-to-remark-stringify) * [Syntax](#syntax) * [Syntax tree](#syntax-tree) * [Types](#types) * [Compatibility](#compatibility) * [Security](#security) * [Contribute](#contribute) * [Sponsor](#sponsor) * [License](#license) ## What is this? This package is a [unified][] processor with support for parsing markdown input and serializing markdown as output by using unified with [`remark-parse`][remark-parse] and [`remark-stringify`][remark-stringify]. **unified** is a project that transforms content with abstract syntax trees (ASTs). **remark** adds support for markdown to unified. **mdast** is the markdown AST that remark uses. Please see [the monorepo readme][remark] for what the remark ecosystem is. ## When should I use this? You can use this package when you want to use unified, have markdown as input, and want markdown as output. This package is a shortcut for `unified().use(remarkParse).use(remarkStringify)`. When the input isn’t markdown (meaning you don’t need `remark-parse`) or the output is not markdown (you don’t need `remark-stringify`), it’s recommended to use unified directly. When you want to inspect and format markdown files in a project on the command line, you can use [`remark-cli`][remark-cli]. ## Install This package is [ESM only](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c). In Node.js (version 12.20+, 14.14+, or 16.0+), install with [npm][]: ```sh npm install @stackline/remark ``` In Deno with [`esm.sh`][esmsh]: ```js import {remark} from 'https://esm.sh/remark@14' ``` In browsers with [`esm.sh`][esmsh]: ```html ``` ## Use Say we have the following module `example.js`: ```js import {remark} from '@stackline/remark' import remarkGfm from 'remark-gfm' import remarkToc from 'remark-toc' main() async function main() { const file = await remark() .use(remarkGfm) .use(remarkToc) .process('# Hi\n\n## Table of contents\n\n## Hello\n\n*Some* ~more~ _things_.') console.error(String(file)) } ``` Running that with `node example.js` yields: ```markdown # Hi ## Table of contents * [Hello](#hello) ## Hello *Some* ~~more~~ *things*. ``` ## API This package exports the following identifier: `remark`. There is no default export. ### `remark()` Create a new (unfrozen) unified processor that already uses `remark-parse` and `remark-stringify` and you can add more plugins to. See [`unified`][unified] for more information. ## Examples ### Example: checking markdown The following example checks that markdown code style is consistent and follows some best practices: ```js import {reporter} from 'vfile-reporter' import {remark} from '@stackline/remark' import remarkPresetLintConsistent from 'remark-preset-lint-consistent' import remarkPresetLintRecommended from 'remark-preset-lint-recommended' main() async function main() { const file = await remark() .use(remarkPresetLintConsistent) .use(remarkPresetLintRecommended) .process('1) Hello, _Jupiter_ and *Neptune*!') console.error(reporter(file)) } ``` Yields: ```txt 1:1 warning Missing newline character at end of file final-newline remark-lint 1:1-1:35 warning Marker style should be `.` ordered-list-marker-style remark-lint 1:4 warning Incorrect list-item indent: add 1 space list-item-indent remark-lint 1:25-1:34 warning Emphasis should use `_` as a marker emphasis-marker remark-lint ⚠ 4 warnings ``` ### Example: passing options to `remark-stringify` When you use `remark-stringify` manually you can pass options to `use`. Because `remark-stringify` is already used in `remark`, that’s not possible. To define options for `remark-stringify`, you can instead pass options to `data`: ```js import {remark} from '@stackline/remark' main() async function main() { const file = await remark() .data('settings', {bullet: '*', setext: true, listItemIndent: 'one'}) .process('# Moons of Neptune\n\n- Naiad\n- Thalassa\n- Despine\n- …') console.log(String(file)) } ``` Yields: ```markdown Moons of Neptune ================ * Naiad * Thalassa * Despine * … ``` ## Syntax Markdown is parsed and serialized according to CommonMark. Other plugins can add support for syntax extensions. ## Syntax tree The syntax tree format used in remark is [mdast][]. ## Types This package is fully typed with [TypeScript][]. There are no extra exported types. ## Compatibility Projects maintained by the unified collective are compatible with all maintained versions of Node.js. As of now, that is Node.js 12.20+, 14.14+, and 16.0+. Our projects sometimes work with older versions, but this is not guaranteed. ## Security As markdown can be turned into HTML and improper use of HTML can open you up to [cross-site scripting (XSS)][xss] attacks, use of remark can be unsafe. When going to HTML, you will likely combine remark with **[rehype][]**, in which case you should use [`rehype-sanitize`][rehype-sanitize]. Use of remark plugins could also open you up to other attacks. Carefully assess each plugin and the risks involved in using them. For info on how to submit a report, see our [security policy][security]. ## Contribute See [`contributing.md`][contributing] in [`remarkjs/.github`][health] for ways to get started. See [`support.md`][support] for ways to get help. Join us in [Discussions][chat] to chat with the community and contributors. This project has a [code of conduct][coc]. By interacting with this repository, organization, or community you agree to abide by its terms. ## Sponsor Support this effort and give back by sponsoring on [OpenCollective][collective]!
|
Vercel |
Motif |
HashiCorp |
GitBook |
Gatsby |
|||||
Netlify
|
Coinbase |
ThemeIsle |
Expo |
Boost Note
|
Holloway |
||||
|
You? |
|||||||||