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

@jsx6/jsx6

v1.8.13

Published

JSX and ES6+ UI library

Downloads

200

Readme

JSX6

From validation

We provide here way to walk through a form that can be used to mark validation results. The actual code that does markging ins not in the source, but examples are provided instaed, as it may depend greatly form project to project.

Exmaple validation result:

let exampleValid = window.exampleValid = {
  items:{
    name: {message:'Required', type:'required'},// validation error
    address: {},// ok
    // city: undefined,// missing key means validation has no error for that field
    contact: {// subform
      message: 'general message for subform',
      items:{
        name: {message:'Required', type:'required'},// validation error
        email: {message:'Invalid email format', type:'invalid'},// has value but it is invalid
      }
    }
  }
}

Example validation setup:

// actual function you will use in your project
function markValid(el, vErr){
  formForEach(el, vErr, validationMarker, validationMarker)
}

// the function doing all the hard work, deciding how to convey validation information into the DOM
export function validationMarker(el, vErr){
  el = toDomNode(el)
  if(!el) return
  let err = vErr?.message
  let parent = el.parentNode
  if(!parent) {
    console.warn(el, vErr)
    throw Error('element without parent HTMLElement')
  }
  // loop can have textNode as base element, and it can not have attributes or calss
  if(el.setAttribute) classIf(el, 'validation-error', err)
  setAttribute(parent,'validation-error-message', err)
  setAttribute(parent,'validation-error-type', vErr?.message)
}

// define how components can declare a custom validation function
validationMarker.hasOverride = el=>el?.markValid
// call the custom validation function
validationMarker.callOverride = function(el, vErr){
  if(el?.markValid){
    try{
      el?.markValid(vErr)
    }catch(e){
      console.error('problem with ',el,'.markValid',e)
    }
  }
}

web components tricks

vanilla JS automatic registration using static initilaizer

  class MyCustomElement extends HTMLElement{
    static { customElements.define('my-custom-element', this) } 
  }

or let user define the component and even change the element name

  class MyCustomElement extends HTMLElement {
    static define(tag='my-custom-element'){ customElements.define(tag, this) } 
  }
  // in that case user must call define before using it
  MyCustomElement.define()