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

react-scenic

v0.4.1

Published

The best observable router for React. 🌋

Downloads

4

Readme

react-scenic

The best observable router for React. 🌋

API

The API is under development. Expect breaking changes and undocumented features.

Scenic

The <Scenic> component decides which scenes are mounted, which scene is focused, and which scenes have been visited.

<Scenic>
  {children}
</Scenic>

 

ScenicRoot

The context of a <Scenic> component. It tracks the current scene as well as past scenes. Its properties can be used in a withAuto component (eg: to render elements conditionally).

 

useScenic

Use the ScenicRoot of the nearest <Scenic> ancestor.

const scenic = useScenic()
scenic.visit('/')

 

useScenicRef

Convenience hook for useRef<ScenicRoot>(null)

Useful in the parent that renders a <Scenic> component.

const scenicRef = useScenicRef()
const rootElement = <Scenic ref={scenicRef}>{scenes}</Scenic>

useEffect(() => {
  scenicRef.current.visit('/foo')
})

 

useScene

Use the Scene of the nearest <SceneMatch> ancestor.

const scene = useScene()

Or get the Scene for a path, creating one if necessary:

const scene = useScene(path)

 

Scene

Scenes are used to conditionally render elements based on the current path (or the history of paths) of the nearest <Scenic> component ancestor. Its properties can be observed by any withAuto component.

To create a Scene, you can call ScenicRoot#get or the useScene hook.

const scene = useScene('/')
// ..same as..
const scenic = useScenic()
const scene = scenic.get('/')

Both calls are idempotent, meaning they will always return the same Scene if you ever pass the same path multiple times.

 

SceneMatch

Render children if a given path or scene is mounted.

// with a path:
<SceneMatch path="/">
  {children}
</SceneMatch>

// or with a Scene object:
<SceneMatch scene={scene}>
  {children}
</SceneMatch>