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

@rustle/oops

v0.0.6

Published

A tiny hooks library

Downloads

7

Readme

npm version

oops has built-in jsx parsing function, but you can also compile jsx with babel.

Hooks

Basic Hooks

  • [x] useState
  • [x] useEffect
  • [x] useContext

Additional Hooks

  • [x] useReducer
  • [x] useCallback
  • [x] useMemo
  • [x] useRef
  • [x] useLayoutEffect
  • [x] useImperativeHandle
  • [ ] useTransition
  • [ ] useDeferredValue

API

  • [x] h
  • [x] jsx
  • [x] memo
  • [x] render
  • [x] createContext
  • [x] createRef
  • [x] forwardRef
  • [x] isValidElement
  • [x] createPortal
  • [ ] lazy
  • Children
    • [x] map
    • [x] forEach
    • [x] count
    • [x] toArray
    • [x] only

Built-in components

  • [x] <Fragment/>
  • [ ] <Suspense/>
  • [x] <Context.Provider/>
  • [x] <Context.Consumer/>

Caveats

  1. The observedBits function of context is not implemented yet.

  2. The functional components also supports defaultProps.

  3. Beacase the React event system is customized, so, the dom created by the createPortal methods allow event bubbling to parent node in vitualDOM tree. But oops uses native event system. our event bubbling behaviors exist in real dom tree that result we can't achieve the same behavior with the React, But our bubbling behavior can still be performed according to the structure of the vitualDOM tree.

  import { render, useState, useEffect, createPortal } from '@rustle/oops'

  const el = document.createElement('div')
  const appRoot = document.getElementById('app-root')
  const modalRoot = document.getElementById('modal-root')

  // Listening to the bubbling behavior of the native event system 
  el.onclick = e => {
    console.log(e.target)
  }

  function Modal(props) {
    useEffect(() => {
      modalRoot.appendChild(el)
      return () => modalRoot.removeChild(el)
    })
    return createPortal(props.children, el)
  }

  const modalStyles = {
      position: 'fixed',
      top: 0,
      left: 0,
      height: '100%',
      width: '100%',
      display: 'flex',
      alignItems: 'center',
      justifyContent: 'center',
      backgroundColor: 'rgba(0,0,0,0.5)',
  }

  function Child() {
    // The click event on this button will bubble up to parent,
    // because there is no 'onClick' attribute defined
    return (
      <div style={ modalStyles }>
        <button>Click</button>
      </div>
    )
  }

  function Parent(props) {
    const [clicks, handleClick] = useState(0)
    return (
      <div onClick={e => {
        console.log(e.target, e.currentTarget, e.nativeEvent)
        handleClick(clicks + 1)
      }}>
        <p>Number of clicks: { clicks }</p>
        <p>
          Open up the browser DevTools
          to observe that the button
          is not a child of the div
          with the onClick handler.
        </p>
        <Modal>
          <Child />
        </Modal>
      </div>
    )
  }

  render(<Parent />, appRoot)