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

@edsolater/pivkit

v0.0.36

Published

1. _STATIC_ means that the prop is not reactive and will changing it will not trigger a rerender\ 2. all are optional

Downloads

96

Readme

props

Piv's(global props)

  1. STATIC means that the prop is not reactive and will changing it will not trigger a rerender\
  2. all are optional
  • if?: MayFn<BooleanLike>> --- STATIC. if is settled and is false , it self and it's children will not render
  • ifSelfShown?: MayFn<BooleanLike>> --- STATIC. if is settled and is false , only it's children will render
  • debugLog?: (keyof PivProps)[] --- only use this for debug mode. it will log all you need
  • domRef?: MayArray<CallbackRef<any> | null | undefined> --- accept domSetter(return from createDomRef) to access the dom
  • class?: MayArray<ClassName<Controller>> --- htmlElement's class
  • id?: string --- id for useComponentByID. So others can access component's controller without set props:controllerRef to component, this have to have access to certain component instance

special

  • render - render_SUBCOMPONENT or render_item
  • TODO: layout

ICSSBlock (style)

determin what component looks like

Component (UI)

  • <Piv> base component. all other components is based on this
  • <AddProps> base component. StateManager is based on this

Box Component

  • <Box> base component. all box-like components is based on this

Content Component

  • <Text> ui text

PluginContext (UI)

  • <PluginContext> base component. all other plugin components is based on this
  • <EditablePluginContext> with editablePlugin

StateManager (UI)

if use hooks to hold state, the user's component's code will be too complicated to understand

  • <Detector> detect state (hover)

useKitProps - a very important hook

Main idea:

  • normal props can accept promise and fn which return value

Q&A

what is different from props:variant and props:icss?

  • props:icss reflect componet's verbose style, which is the "looks like" of the component.
  • props:variant reflect component's state, which is the "is like" of the component.