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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@li3/sfc

v0.0.4

Published

Transform a single-file component into a component definition, or into an executable ES module with a custom element.

Downloads

21

Readme

@li3/sfc

Transform a single-file component into a component definition, or into an executable ES module with a custom element.

Usage

import { parseSFC, getComponentCode } from '@li3/sfc';

const sfc = parseSFC('<template><div>hello!</div></template>');
const code = getComponentCode('hello-world', sfc);

Single-file components

A single-file component has usually two parts: a template and a script. Optionally, it can also have a style tag.

<template>

A template can define options for ShadowDOM in an attribute. shadow-dom can either be a string or a JSON. For simplicity, open or closed are accepted as strings. Otherwise, a JSON object with the same options passed to element.attachShadow() can also be provided.

If no shadow-dom attribute is provided, the component behaves like a regular DOM structure, with the content of <template> processed and appended to the custom element's root node.

<script>

A script tag defines the code executed for every component instance. The content inside the script tag is implicitly wrapped by a function, which is then executed every time a new instance of a component is initialized.

If a component has any import or export statement, any code between the last import and the first export is considered as setup code. Because export statements can use values that would be part of the source, in case a component needs to export values, a setup function must be defined, and called defineComponent. The conversion will fail otherwise.

<style>

A style tag can be defined with styles that will be added to every component instance.

Examples

A component with only setup code:

<script>
  import { onInit } from '@li3/web';

  function componentLoaded() {
    // do something
  }

  onInit(componentLoaded);
</script>

A component with a template using shadowDom, a script and styles:

<template component="greeting-card" shadow-dom="open">
  <div class="hello">Hello, {{ name }}!</div>

  <script setup>
    import { defineProps } from '@li3/web';

    export default function () {
      defineProps(['name']);
    }
  </script>

  <style>
    .hello {
      font-size: 3rem;
    }
  </style>
</template>

A component that has only a template:

<template shadow-dom="open">
  <div>A static text with a tiny font size</div>
</template>
<style>
  div {
    font-size: 0.25rem;
  }
</style>

A component with imports and exports:

<template>
  <div>{{color}}</div>
</template>
<script>
  import { defineProps } from '@li3/web';

  const validColors = ['red', 'blue', 'green'];

  function defineComponent() {
    defineProps(['color']);
  }

  export { validColors };
</script>