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

petite-arch

v1.0.1

Published

Node.JS petite-arch module

Downloads

6

Readme

path

This is an exact copy of the NodeJS ’petite-arch’ module published to the NPM registry.

Documentation

Install

$ npm install --save petite-parch

petite arch

  • petite arch is a project derived from a petite-vue problem, meaning is a pretty simple add-on.

  • although is the problem is based on petite-vue, it doesn't only work for petite-vue.

Status

  • This is have started as an experiment for a personal project. So we highly suggest the use of parse for inputs.
  • Project is also Open Source so if anything that is needed it can be modified

Usage

  • How to use petite-arch
import { parch } from 'petite-arch';

//parch({props, template})

const my_template = parch({
  props: {
    attr: "id='container' class='active'",
    content: {
      title: "hello world",
      paragraph: "im greeting in my title ;)"
    }
  },

  //template: `hello if no props is passed else -> template(props) {}`

  template(props){
    //it is recommended to use the backtick or concatenate
    return `
      <div ${props.attr} >
        <h2>${props.content.title}</h2>
        <p>${props.content.paragraph}</p>
      </div>
    `
  }
})
  • for inputs in forms or applications you might want to use the parse utility.
//in this example we import petite vue so you can see an example
//file -> main.js

import {createApp} from 'petite-vue';
import {parch, parse } from 'petite-arch';

const templates = parch({
  props: {
    title: "",
    letter: ""
  },
  template(props){
    return `
      <form>
        <h2>${props.title}</h2>
        <input v-model=${props.letter}>
      </form>

      <div>
        <p>${parse(props.letter)}</p>
      <div>
    `
  }
})

const app = props => {
  return {
    title: props.title,
    letter: props.letter,
    //$template -> is not used because its a loaded template and is kind of like static so instead el.innerHTML is used
    
    mounted(){
      el.innerHTML = my_template
    }
  }
}
  • in the example above we use this line:
<p>${parse(props.letter)}</p>

parse is the built-in input filter for petite-arch/parch <-- name was taken

<!--html file-->
<div v-scope="app({title: 'my letter'})"></div>

Security and CSP

  • in Order to avoid possible XSS attacks, use the parse utility

  • in case of you having a backend, we recommend the use of filters pipes or guards as well

sources

License

MIT