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-stack-navigator

v0.4.2

Published

A native-like stack navigator for React DOM, inspired by Flutter's Navigator v1

Downloads

20

Readme

React Stack Navigator

npm package build status

A stack navigator for React inspired by Flutter's Navigator API and entirely based on pushing and popping.

Installation

With npm,

npm i react-stack-navigator

With Yarn,

yarn add react-stack-navigator

TypeScript types are included out of the box! 📦

Usage

Using the library is quite simple: just include a <StackNavigator> component, specifying the root route (i.e., the route at the bottom of the stack).

import { StackNavigator } from 'react-stack-navigator';

export const App = () => {
	return <StackNavigator root={<HomePage />} />;
};

Then, inside your components, you can push and pop routes using the functions provided by the useStackNavigator hook (or, if you prefer, the RoutingFunctionsContext context).

import { useStackNavigator } from 'react-stack-navigator';

export const ScreenA = () => {
	const { push } = useStackNavigator();

	return <button onClick={() => push(<ScreenB />)}>Push!</button>;
};

This is very similar to Flutter's Navigator: indeed, when you pop a route, you can pass in a result, which will be returned asynchronously by the last push function.

import { useStackNavigator } from 'react-stack-navigator';

export const ScreenA = () => {
	const { push } = useStackNavigator();

	return (
		<button onClick={async () => {
			const result = await push(<ScreenB />)
			console.log('Hello, ' + result); // Hello, World!
		}}>Push!</button>
	);
};

export const ScreenB: React.FC = () => {
	const { pop } = useStackNavigator();

	return <button onClick={() => pop('World!')}>Pop!</button>;
};

Modal and non-modal routes

By passing a second argument to the push function, you can mark a route as modal. This option will affect the route's animation and will be available to the child route.

import { useStackNavigator } from 'react-stack-navigator';

export const ScreenA = () => {
	const { push } = useStackNavigator();

	return (
		<button onClick={() => push(<ScreenB />, true)}>Push!</button>
	);
};

export const ScreenB: React.FC = () => {
	// The given options are accessible to the child route
	const { pop, isModal } = useStackNavigator();

	return <button onClick={() => pop()}>Pop!</button>;
};

With React Router

Since navigating the stack does not alter the URL pathname but only the hash, you can include as many stack navigators as you wish in your React Router routes, without changing a single line of code—as you're not using a hash-based history: if you are, this library most likely doesn't suit your needs.

Thanks

Big thanks to Flutter for the inspiration!