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

sjsx

v0.1.4

Published

> A super simple implementation of the JSX specification.

Downloads

4

Readme

sjsx

A super simple implementation of the JSX specification.

Really, another one?

Yes, because:

  • No current implementation of JSX contained the features I wanted, with all the ones it doesn't need.
  • Tooling

Features

  • Standard DOM attributes
    • Use class and onclick! Or className and onClick, if you're into that.
  • Render DOM references alongside JSX
    • I hate using ref and lifecycle callbacks. This removes them for my life forever, hallelujah!
  • No class components
    • Completely pointless. Hyperapp gets it. Even React is moving away from them with Hooks.
  • No automatic re-rendering of components
    • By giving up this so-called "convenience," we gain more control to fine-tune exactly when and where our app needs to be updated. There are render and patch functions available. This also gives us the additional benefit of:
  • No virtual DOM state stored in memory
    • Again, not necessary. Hyper fast diffs and patching can be accomplished via the DOM, especially if we're not re-rendering everything when any piece of our state or data changes.
  • Fragments
    • Because wrapper hell is real.
  • children as a separate argument
    • Makes your app easier to read and understand.
  • Stupid simple tooling (COMING SOON)
    • Because wtf eject? Really? Have a complete solution with production and development environments, up and running in less than a minute.
  • Small, under 3KB gzipped
    • And I haven't even tried to optimize this yet, which will only make this even smaller in the near future.