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

@bearbytes/magellan

v3.0.1

Published

Simplified navigation for React Native with improved Typescript support, based on react-navigation

Downloads

16

Readme

@bearbytes/magellan

This is a wrapper around react-navigation, the popular navigation library for React Native.

It adds improved Typescript support and a simplified API for basic navigation needs.

Getting started

Install the dependency: npm i @bearbytes/magellan

Define the available screens and their corresponding navigation parameters:

export interface AppScreens {
  Home: {}
  UserProfile: { userId: string }
  Chat: { partnerUserId: string; isPrivate?: boolean }
}

Initialize the navigation system. It will create a StackNavigator which can be pre-configured with the usual configuration:

import { createNavigation } from './lib/Magellan/createNavigationRoot'
import { AppScreens } from './AppScreens'

export const {
  NavigationRoot,
  navigate,
  navigateBack,
  dispatchNavigationAction,
} = createNavigation<AppScreens>({
  // Pass configuration for the main StackNavigator here
  headerMode: 'none',
  transparentCard: true,
})

The NavigationRoot is a React Component that will contain the currently visible screen(s). Put it into the root of your app. You will need to pass it a component for each screen in the AppScreens interface.

export default function MyApp() {
  return (
    <SomeContextProvider>
      <MaybeReduxContainerOrSomething>
        {/* Should be the main component */}
        <NavigationRoot
          Home={HomeScreen}
          UserProfile={UserProfileScreen}
          Chat={props => {
            // You could also create adhoc components in here.
            // The props passed to the component are equivalent to
            // navigation parameters in react-navigation.
            if (props.isPrivate) {
              return <PrivateChatScreen {...props} />
            } else {
              return <PublicChatScreen {...props} />
            }
          }}
        />
      </MaybeReduxContainerOrSomething>
    </SomeContextProvider>
  )
}

To avoid having to maintain duplicate props definitions, I would advise to use the AppScreens interface to define the screen props:

export function UserProfileScreen(props: AppScreens['UserProfile']) {
  return <Text>Profile of {props.userId}.</Text>
}

Navigating

As you may have noticed, the navigation prop that is usually used in react-nativation is nowhere to be found here. Instead, magellan opts to use top level functions to navigate between screens:

// The navigate function knows about which screens exist and
// what parameters can or must be passed to them. Typescript
// will enforce that we never forget something here.

navigate('UserProfile', { userId: 'bob' })

// Navigation params must always be passed, even when empty.
navigate('Home', {})

// Go back to the previous screen.
// Does nothing when there is only one screen on the stack.
navigateBack()

// The above actions should be enough for most usecases.
// If you need to use a more complex action, you can dispatch
// it directly. Note that unlike the other functions, no
// typesafeness is guaranteed here.
dispatchNavigationAction({ type: 'Navigation/OPEN_DRAWER' })

dispatchNavigationAction({
  type: 'Navigation/POP_TO_TOP',
  immediate: true,
})