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

@doars/staark-patch

v1.0.1

Published

A teeny-tiny stateless framework for building web apps.

Downloads

6

Readme

staark patch

A teeny-tiny stateless framework for building web apps.

  • Minimal amount of concepts to learn in order to get going, meaning the system becomes incredibly easy to reason with.
  • Comes in at a kilobyte in size when compressed. Due to the minimal philosophy of the library and the simple concepts within the total size is tiny as well.
  • Has an efficient diffing algorithm. This ensures the node tree is morphed quickly from the old to the new with minimal overhead.
  • Written in TypeScript.

Looking for one with a state management solution checkout out staark.

To use staark patch, you need to know two main functions the prepare and node. With prepare, you set up the patch function, which will update a section of the node tree based on new abstract node tree you provide. The node function creates those abstract representations of document elements, which staark patch uses to manipulate the actual document.

import { node as n, prepare } from '@doars/staark-patch'

const patch = prepare(
  document.body.firstSibling,
)

patch(
  n('div', [
    n('p', 'Hello there'),
    n('p', 'General Kenobi'),
  ]),
)

The prepare function attaches the patch function to the document’s first sibling. The patch function is then used to apply a simple view of two paragraphs into the document. Every time patch is called, the document updates based on the new nodes passed to it.

Even though patch is stateless, you can still use it for dynamic updates by manually handling state changes within your code. The library provides an easy and efficient way to re-render parts of your document when you modify your data.

import { node as n, prepare } from '@doars/staark-patch'

const patch = prepare(
  document.body.firstSibling,
)

const state = {}
const update = () => {
  patch(
    n('div', [
      n('span', state.count),
      n('button', {
        click: () => {
          state.count++
          update()
        },
      }, 'add')
    ]),
  )
}

As you can read above, update re-renders the view with the current value of state.count whenever the button is clicked. Despite patch being stateless, it allows you to control state externally and reapply the patches as needed.

Then there is also another second parameter for the prepare function. This parameter can be the abstract node tree of the existing HTML. Typically rendered on the server and the provided to the client. See the staark isomorphic package for more in formation on this. And also important to note to make it easier, if the existing abstract node tree is a string it will automatically be parsed as JSON.

The full build of the library also exports the factory, fctory, nde, and text functions from staark so these don't have te imported from there separately. And do note that the memo function is not exported because this is not supported since there is no state to provide to these memoization functions.

Installation

Via NPM

npm install @doars/staark-patch

IIFE build via a CDN

<!-- Base bundle -->
<script src="https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.base.iife.js"></script>
<!-- Base bundle minified -->
<script src="https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.base.iife.min.js"></script>
<!-- Full bundle -->
<script src="https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.iife.js"></script>
<!-- Full bundle minified -->
<script src="https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.iife.min.js"></script>

ESM build via a CDN

// Base bundle.
import { node as n, prepare } from 'https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.base.js'
// Base bundle minified.
import { node as n, prepare } from 'https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.base.min.js'
// Full bundle.
import { node as n, prepare } from 'https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.js'
// Full bundle minified.
import { node as n, prepare } from 'https://cdn.jsdelivr.net/npm/@doars/staark-patch@1/dst/staark-patch.min.js'