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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@markpage/svelte

v0.1.6

Published

Svelte integration for Markpage with component support

Readme

@markpage/svelte

Svelte integration for Markpage with component support and markdown extensions.

Features

  • Component Registration: Register Svelte components for use in markdown with the new MarkpageOptions API
  • Nested Component Support: Components can contain other components and full markdown content
  • Markdown Extensions: Add custom markdown syntax with components
  • Built-in Overrides: Override any built-in markdown token (paragraphs, headings, lists, etc.)
  • Enhanced Marked Integration: Automatic Marked instance management with extensions
  • SSR Support: Full server-side rendering support for SvelteKit
  • Type Safety: Full TypeScript support with improved type definitions
  • Automatic Parsing: Extensions are automatically applied to markdown parsing

Installation

npm install @markpage/svelte

Examples

1. Basic Markdown Rendering

Start with the simplest example - just render plain markdown:

<script lang="ts">
  import { Markdown } from '@markpage/svelte';

  const source = `
# Hello World

This is **bold** text and this is *italic*.

- List item 1
- List item 2

[Visit our website](https://example.com)
  `;
</script>

<Markdown {source} />

2. Custom Components with Nested Content

Add custom Svelte components that can be used as tags in markdown. Components now support full markdown content and can be nested:

<script lang="ts">
  import { Markdown, MarkpageOptions } from '@markpage/svelte';
  import Button from './Button.svelte';
  import Alert from './Alert.svelte';
  import Card from './Card.svelte';

  const options = new MarkpageOptions()
    .addCustomComponent('Button', Button)
    .addCustomComponent('Alert', Alert)
    .addCustomComponent('Card', Card);

  const source = `
# Custom Components

<Button variant="primary">Click me</Button>

<Alert variant="warning" title="Important">
  This is a warning message with **markdown** inside!
  
  - List items work
  - **Bold text** works
  - [Links](https://example.com) work too
</Alert>

<Card title="Nested Components" subtitle="Components can contain other components">
  <Alert variant="info">
    This alert is **inside** a card component!
  </Alert>
  
  <Button variant="secondary">Button in card</Button>
</Card>
  `;
</script>

<Markdown {source} {options} />

Button.svelte:

<script lang="ts">
  export let variant = 'default';
  export let size = 'medium';
  let { children } = $props();
</script>

<button class="btn btn-{variant} btn-{size}">
  {@render children()}
</button>

Alert.svelte:

<script lang="ts">
  export let variant = 'info';
  export let title = '';
  let { children } = $props();
</script>

<div class="alert alert-{variant}">
  {#if title}<h4>{title}</h4>{/if}
  {@render children()}
</div>

3. Override Built-in Tokens

Override any built-in markdown token with your own component:

<script lang="ts">
  import { Markdown, MarkpageOptions } from '@markpage/svelte';
  import CustomCodeSpan from './CustomCodeSpan.svelte';

  const options = new MarkpageOptions()
    .overrideBuiltinToken('codespan', CustomCodeSpan);

  const source = `
# Custom Code Styling

Here is some \`inline code\` with custom styling!
  `;
</script>

<Markdown {source} {options} />

CustomCodeSpan.svelte:

<script lang="ts">
  export let token;
</script>

<code class="custom-code" data-overridden="true">
  {token.text}
</code>

4. Markdown Extensions (LaTeX Math)

Add completely new markdown syntax with custom components:

<script lang="ts">
  import { Markdown, MarkpageOptions } from '@markpage/svelte';
  import MathInline from './MathInline.svelte';
  import MathBlock from './MathBlock.svelte';

  function mathExtension() {
    return {
      extensions: [
        {
          name: 'math_block',
          level: 'block' as const,
          component: MathBlock,
          start(src: string) {
            const i = src.indexOf('$$');
            return i < 0 ? undefined : i;
          },
          tokenizer(src: string) {
            if (!src.startsWith('$$')) return;
            const end = src.indexOf('$$', 2);
            if (end === -1) return;
            const raw = src.slice(0, end + 2);
            const text = src.slice(2, end).trim();
            return { type: 'math_block', raw, text } as any;
          }
        },
        {
          name: 'math_inline',
          level: 'inline' as const,
          component: MathInline,
          start(src: string) {
            const i = src.indexOf('$');
            return i < 0 ? undefined : i;
          },
          tokenizer(src: string) {
            if (src.startsWith('$$')) return; // let block handle
            if (!src.startsWith('$')) return;
            const end = src.indexOf('$', 1);
            if (end === -1) return;
            const raw = src.slice(0, end + 1);
            const text = src.slice(1, end).trim();
            return { type: 'math_inline', raw, text } as any;
          }
        }
      ]
    };
  }

  const options = new MarkpageOptions()
    .extendMarkdown(mathExtension());

  const source = `
# Mathematical Expressions

Here is inline math: $E = mc^2$

And here is a block equation:

$$
\\int_{-\\infty}^{\\infty} e^{-x^2} dx = \\sqrt{\\pi}
$$
  `;
</script>

<Markdown {source} {options} />

MathInline.svelte:

<script lang="ts">
  export let token;
</script>

<span class="math-inline" data-math="inline">
  {token.text}
</span>

MathBlock.svelte:

<script lang="ts">
  export let token;
</script>

<div class="math-block" data-math="block">
  {token.text}
</div>

API Reference

MarkpageOptions

The main configuration class for all markdown customization. This class provides a fluent interface for setting up component registration, token overrides, and markdown extensions:

const options = new MarkpageOptions()
  .addCustomComponent(name, component)      // Register custom component tags
  .overrideBuiltinToken(name, component)    // Override built-in tokens
  .extendMarkdown(extensions)               // Add markdown extensions
  .useMarkedInstance(instance)              // Use custom Marked instance
  .useMarkedFactory(factory);               // Use custom Marked factory

Methods

  • addCustomComponent(name, component): Register a custom component for use as a tag in markdown. Components can contain nested markdown content and other components.
  • overrideBuiltinToken(name, component): Override a built-in markdown token with a custom component (e.g., paragraph, heading, list, etc.)
  • extendMarkdown(extensions): Register markdown extensions with their associated components. Extensions can add completely new markdown syntax.
  • useMarkedInstance(instance): Use a specific Marked instance for parsing. Useful for advanced customization.
  • useMarkedFactory(factory): Use a factory function to create Marked instances. Allows for dynamic instance creation.

Internal Methods

  • getComponents(): Get the Map of registered custom components
  • getExtensionComponents(): Get the Map of extension and override components
  • getMarked(): Get the configured Marked instance (creates default with extensions if none set)
  • getExtensions(): Get all registered markdown extensions

Built-in Tokens You Can Override

  • heading - Headers (# ## ###)
  • paragraph - Paragraphs
  • list - Lists
  • list_item - List items
  • blockquote - Blockquotes
  • code - Code blocks
  • codespan - Inline code
  • link - Links
  • image - Images
  • strong - Bold text
  • em - Italic text
  • hr - Horizontal rules
  • table - Tables
  • And more...

Extension Format

interface MarkdownExtension {
  name: string;                    // Token type name
  level: 'block' | 'inline';       // Block or inline level
  component: Component;            // Svelte component to render
  start(src: string): number | undefined;  // Find start position
  tokenizer(src: string): any;     // Parse the token
}

Advanced Usage

Nested Component Support

The new API provides enhanced support for nested components. Components can contain other components and full markdown content:

<script lang="ts">
  import { Markdown, MarkpageOptions } from '@markpage/svelte';
  import Card from './Card.svelte';
  import Alert from './Alert.svelte';
  import Button from './Button.svelte';

  const options = new MarkpageOptions()
    .addCustomComponent('Card', Card)
    .addCustomComponent('Alert', Alert)
    .addCustomComponent('Button', Button);

  const source = `
<Card title="Complex Nested Example">
  <Alert variant="info">
    This alert contains:
    
    - **Bold text**
    - *Italic text*
    - [A link](https://example.com)
    
    And even another component:
    
    <Button variant="primary">Nested Button</Button>
  </Alert>
</Card>
  `;
</script>

<Markdown {source} {options} />

Manual Marked Instance

For advanced use cases where you need custom Marked configuration:

<script lang="ts">
  import { Markdown, MarkpageOptions, Marked } from '@markpage/svelte';

  const markedInstance = new Marked();
  // Add custom configuration here
  markedInstance.setOptions({ breaks: true });

  const options = new MarkpageOptions()
    .extendMarkdown(myExtensions)
    .useMarkedInstance(markedInstance);
</script>

<Markdown {source} {options} />

Combining All Features

<script lang="ts">
  import { Markdown, MarkpageOptions } from '@markpage/svelte';
  import Button from './Button.svelte';
  import CustomCodeSpan from './CustomCodeSpan.svelte';
  import MathInline from './MathInline.svelte';

  const options = new MarkpageOptions()
    .addCustomComponent('Button', Button)           // Custom tags
    .overrideBuiltinToken('codespan', CustomCodeSpan) // Override built-ins
    .extendMarkdown(mathExtension());               // Add extensions
</script>

<Markdown {source} {options} />

SSR Support

  • Built using @sveltejs/package for SvelteKit compatibility
  • Works in SSR; avoid direct browser globals in your components during SSR

TypeScript Support

Full TypeScript support is included:

import type { 
  MarkpageOptions,
  MarkdownExtension,
  MarkdownExtensionSet
} from '@markpage/svelte';

Security

  • Components must be registered upfront
  • No arbitrary code execution
  • No dynamic imports
  • Component names are validated

Performance

  • Extensions are automatically applied to parsing
  • Components are registered once at startup
  • Efficient component lookup using Map
  • No runtime compilation overhead

Contributing

This package is part of the Markpage monorepo. See the main README for contribution guidelines.

License

MIT License - see LICENSE file for details.