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

@metaliq/metadoc

v1.0.0-beta.134

Published

MetaliQ publication target for generating MetaViews from documents

Downloads

274

Readme

@metaliq/metadocs

This module provides a MetaliQ publication target enabling lit-based MetaViews to be generated from documents authored in the Markdown format.

Usage

A typical setup would be to process documents in a "content" directory and produce MetaView modules within the src/gen directory, which is then included in downstream compilation of other publication targets (such as @metaliq/web-page-app), but excluded from version control in the default MetaliQ solution template.

  export const metadocGeneration: MetaModel<any> = {
    label: "Generate MetaViews from MetaDocs",
    publicationTarget: metadoc({
      inDir: "content",
      outDir: ""
    })
  }

Such a MetaModel doesn't really need to be based on a specific data type (hence the use of any), but this approach will be compatible with possible future support for multiple publication targets, enabling the metadoc stage to be added to a typical web page app MetaModel.