react-stack-navigator
v0.4.2
Published
A native-like stack navigator for React DOM, inspired by Flutter's Navigator v1
Downloads
20
Maintainers
Readme
React Stack Navigator
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!