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

@futurevisuals/stinber

v1.1.5

Published

Vanilla two-way data binding made easy.

Downloads

1

Readme

Stinber

Stinber

Vanilla JS two-way databinding made easy! With this vanilla JS library (written in Typescript) it is easy to update the DOM based on data.

Installation

To incorporate Stinber in your project simply run:

npm install @futurevisuals/stinber

Usage

You can do a lot of things with Stinber, a very simple example might look something like this.

<!-- HTML -->
<div>
  <h1 data-binding="name"></h1>
  <h2 data-binding="job">Initial data, will be overwritten unless you define the 'initialRender' property.</h2>
</div>
<input type="text" data-model="name" />
// Javascript/Typescript
import { createState, listener } from '@futurevisuals/stinber';

const myState = createState({
  name: 'Future Visuals',
  job: 'Developer'
});

document.querySelector('input').addEventListener('keyup', listener.bind(myState));

API reference

Stinber exports two functions which you are gonna use primarily. These function are:

createState

import { createState } from '@futurevisuals/stinber';

const myState = {
  name: 'Future Visuals'
  // ... more data you want to bind
}

const renderConfig = {
  /**
   * description: Determines if a HTML string should be rendered as string or should be parsed to the DOM. False will render it as a string.
   * type: boolean
   * initialValue: false
   */
  allowHTML: false,

  /**
   * description: Sometimes when content comes out of a CMS you might not want to overwrite instantly. When set to false it doesn't render from the get go, only on change.
   * type: boolean
   * initialValue: true
   */
  initialRender: true,

  /**
   * description: The `innerHTML` and `textContent` methods (which are used under the hood) doesn't receive anything else other than String (officialy). With this method you can parse values to a string.
   * type: boolean
   * initialValue: false
   */
  stringifyValues: false
}

// The renderConfig and its properties are all optional.
createState(myState, renderConfig)

listener

To really create two-way databinding you should link your data to some kind of user input. For now Stinber only support binding with the following inputs:

  • <input />
  • <textarea></textarea>
  • <select></select>

You can ofcourse create your own listening event and update the state manually, however for simple usage you can use the built-in listener.

import { createState, listener } from '@futurevisuals/stinber';

const myState = createState({
  name: 'Future Visuals',
});

document.querySelector('input').addEventListener('keyup', listener.bind(myState));

Note: Don't forget to bind your state as in the example!

Contributing

If you experiencing bugs or like to see some feature added please create a feature request, issue or a PR on https://github.com/futurevisuals/snipsnip.