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

@mini-apps/navigation-react

v1.3.0

Published

React wrapper for @mini-apps/navigation

Downloads

5

Readme

Navigation NPM

React implementation of @mini-apps/navigation

Installation

yarn add @mini-apps/navigation-react

or

npm i @mini-apps/navigation-react

Components

Usage

Firstly, you have to create instance of BrowserNavigator from @mini-apps/navigation:

import {BrowserNavigator as Navigator} from '@mini-apps/navigation';

const navigator = new Navigator();

Then, you should import BrowserNavigator component from @mini-apps/navigation-react and pass created navigator:

import React, {useEffect, useMemo} from 'react';

import {BrowserNavigator} from '@mini-apps/navigation-react';

// App component will be shown later
import {App} from './App';

import {
  BrowserNavigator as Navigator,
  extractInitOptions,
} from '@mini-apps/navigation';

function Root() {
  // Create navigator
  const navigator = useMemo(() => new Navigator(), []);

  // Initialize it with extracted from browser settings
  useEffect(() => {
    const settings = extractInitOptions();

    navigator.init(settings || undefined);

    // We could pass any data we need in init. Moreover, we could just
    // call mount() if extracting initial navigator state is not required
  }, [navigator]);

  return (
    <BrowserNavigator navigator={navigator}>
      <App/>
    </BrowserNavigator>
  );
}

To make routing work, we could use native browser a tags along with createLink from @mini-apps/navigation which creates appropriate links for navigator with something like this:

import React from 'react';
import {createLink} from '@mini-apps/navigation';

function SomeBanner() {
  return (
    <div>
      <a href={createLink({view: 'promo'})}>Go to promo</a>
      <a href={createLink({view: '', modifiers: ['back']})}>Go back</a>
    </div>
  );
}

When using this way of defining links, make sure you already created and initialized BrowserNavigator instance, because otherwise, nothing will watch for history updates and as a result, nothing happens.

Nevertheless, using default a tags has a big defect. Clicking these links will make browser splice all history items after current history element. So, you will lose part of history, but BrowserNavigator will keep working fine and correct.

We recommend more comfortable and stable way of defining links like this:

import React from 'react';
import {Link} from '@mini-apps/navigation-react';

function SomeBanner() {
  return (
    <div>
      <Link state={{view: 'promo'}}>
        <a>Go to promo</a>
      </Link>
      <Link state={{view: 'promo-2'}} replace={true}>
        <a>Replace with another promo</a>
      </Link>
      <Link back={true}>
        <a>Go back</a>
      </Link>
    </div>
  );
}

It looks much better and has a good benefit. When back property is passed, Go back link will not make browser cut its history. Internally, navigator.back() is called.

Link component is just passing props href and onClick (onClick is just extended, original callback is not lost) to child component

Complete example
import React, {useEffect, useMemo} from 'react';

import {
  BrowserNavigator as Navigator,
  extractInitOptions,
} from '@mini-apps/navigation';
import {
  BrowserNavigator,
  Link,
  useHistory, 
  useNavigatorState, 
  useNavigator,
} from '@mini-apps/navigation-react';

export function App() {
  const navigator = useNavigator();
  const state = useNavigatorState();
  const history = useHistory();

  return (
    <div>
      <p>Current history</p>
      <div>
        {history.map((s, idx) => {
          const stringified = JSON.stringify(s);
          let content = s === state 
            ? <b>{stringified}</b> 
            : stringified;

          return <div key={idx}>{content}</div>;
        })}
      </div>
      <button onClick={() => navigator.back()}>Back</button>
      <button onClick={() => navigator.forward()}>Forward</button>
      <Link state={{view: 'main'}}>
         <a>Link to main</a>
      </Link>
      <Link state={{view: 'main', popup: 'delete-user'}} oneTime={true}>
        <a>Show one time popup which prompts for user delete</a>
      </Link>
      <Link state={{view: 'onboarding'}} replace={true}>
        <a>Replace current state with onboarding</a>
      </Link>
      <Link back={true}>
        <a>Link to previous state (Back button alternative)</a>
      </Link>
    </div>
  );
}

function Root() {
  // Create navigator
  const navigator = useMemo(() => new Navigator(), []);

  // Initialize it with extracted from browser settings
  useEffect(() => {
    const settings = extractInitOptions();

    navigator.init(settings || undefined);

    // We could pass any data we need in init. Moreover, we could just
    // call mount() if extracting initial navigator state is not required
  }, [navigator]);

  return (
    <BrowserNavigator navigator={navigator}>
      <App/>
    </BrowserNavigator>
  );
}

BrowserNavigator