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

@cartamd/plugin-component

v1.0.2

Published

This plugin adds support for mapping certain elements to **components** inside the editor.

Downloads

399

Readme

Carta Component Plugin

This plugin adds support for mapping certain elements to components inside the editor.

Installation

npm i @cartamd/plugin-component

Usage

Mapping components

The first thing to do is to map certain elements(nodes) to their corresponding components. For example, if you want to use a custom renderer for images:

<!-- Image.svelte -->
<script>
	export let src;
	export let alt;
</script>

<!-- Your custom component... -->
<img {src} {alt} />
import { Carta } from 'carta-md';
import { component } from '@cartamd/plugin-component';
import { svelte, initializeComponents } from '@cartamd/plugin-component/svelte';
import Image from './Image.svelte';

const mapped = [svelte('img', Image) /* other components ... */];

const carta = new Carta({
	extensions: [component(mapped, initializeComponents)]
	// ...
});

You can use custom logic when selecting which nodes to map:

import { svelteCustom } from '@cartamd/plugin-component/svelte';
import MyComponent from '...';

const mapped = [
	svelteCustom(
		'my-component-id',
		(node) => {
			// Do something with the node to determine whether to replace it
		},
		MyComponent
	) /* other components ... */
];

Using <slot />

To render children, you need to use a custom <Slot /> component:

<!-- Heading.svelte -->
<script>
	import { Slot } from '@cartamd/plugin-component/svelte';
</script>

<h1>
	<Slot />
</h1>

Usage with pre-rendering

When pre-rendering content on the server (using the <PreRendered> component), the components will not be mounted by default. You need to use the initializeComponents function yourself.

<script>
	import { initializeComponents } from '@cartamd/plugin-component/svelte';
	import { onMount } from 'svelte';
	// ...

	export let data;

  let container;

  // Needs access to the mapped components
  const mapped = /* ... */;

  onMount(() => {
    initializeComponents(mapped, container);
  })
</script>

<div bind:this={container}>
	<PreRendered html={data.html} />
</div>

Limitations

  • During server-side rendering, embedded styles for the mapped components are not added to the bundle. Use a dedicated stylesheet instead.
  • <svelte:head> is not available during server-side rendering.