Skip to content
This repository has been archived by the owner on Dec 3, 2022. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

React Navigation Hooks (v3/v4 only)

npm version npm downloads CircleCI badge PRs Welcome

๐Ÿ„โ€โ™€๏ธ Surfing the wave of React Hook hype with a few convenience hooks for @react-navigation/core v3/v4. Destined to work on web, server, and React Native. Contributions welcome!

Only for react-navigation v3 / v4 (not v5)

react-navigation v5 is officially released as stable, and includes similar, but rewritten hooks (it should be easy to upgrade from v4 to v5).

If you use react-navigation v5, you should import hooks from react-navigation v5 directly, and should not add this project.


yarn add react-navigation-hooks

import { useNavigation, useNavigationParam, ... } from 'react-navigation-hooks'


This is the main convenience hook. It provides the regular navigation prop, as you'd get via the screen prop or by using withNavigation.

You can use the navigate functionality anywhere in your app:

function MyLinkButton() {
  // be careful to never call useNavigation in the press callback. Call hooks directly from the render function!
  const { navigate } = useNavigation();
  return (
      onPress={() => {
      title="Go Home"


Access a param for the current navigation state

function MyScreen() {
  const name = useNavigationParam('name');
  return <p>name is {name}</p>;

Literally the same as useNavigation().getParam(paramName)


Access the navigation state of the current route, or if you're in a navigator view, access the navigation state of your sub-tree.

function MyScreen() {
  const { routeName } = useNavigationState();
  return <p>My route name is {routeName}</p>;

Literally the same as useNavigation().state


Convenient way to access the key of the current route.

Literally the same as useNavigationState().key


Subscribe to navigation events in the current route context.

function ReportNavigationEvents() {
  const [events, setEvents] = useState([]);
  useNavigationEvents(evt => {
    // latest state on evt.state
    // prev state on evt.lastState
    // triggering navigation action on evt.action

    setEvents(events => [, evt]);
  // evt.type is [will/did][Focus/Blur]
  return (
      { => (

The event payload will be the same as provided by addListener, as documented here:


Convenient way to know if the screen currently has focus.

function MyScreen() {
  const isFocused = useIsFocused();
  return <Text>{isFocused ? 'Focused' : 'Not Focused'}</Text>;


Permit to execute an effect when the screen takes focus, and cleanup the effect when the screen loses focus.

function MyScreen() {
  useFocusEffect(useCallback(() => {
    console.debug("screen takes focus");
    return () => console.debug("screen loses focus");
  }, []));
  return <View>...</View>;

NOTE: To avoid the running the effect too often, it's important to wrap the callback in useCallback before passing it to useFocusEffect as shown in the example. The effect will re-execute everytime the callback changes if the screen is focused.

useFocusEffect can be helpful to refetch some screen data on params changes:

function Profile({ userId }) {
  const [user, setUser] = useState(null);

  const fetchUser = useCallback(() => {
    const request = API.fetchUser(userId).then(
      data => setUser(data),
      error => alert(error.message)

    return () => request.abort();
  }, [userId]);


  return <ProfileContent user={user} />;

useFocusEffect can be helpful to handle hardware back behavior on currently focused screen:

const useBackHandler = (backHandler: () => boolean) => {
  useFocusEffect(() => {
    const subscription = BackHandler.addEventListener('hardwareBackPress', backHandler);
    return () => subscription.remove();


deprecated: this hook does not exist in v5, you should rather use useIsFocused

Convenient way of subscribing to events and observing focus state of the current screen.

function MyScreen() {
  const focusState = useFocusState();
  return <Text>{focusState.isFocused ? 'Focused' : 'Not Focused'}</Text>;

One (always, and only one) of the following values will be true in the focus state:

  • isFocused
  • isBlurring
  • isBlurred
  • isFocusing

Web example

See an example web app which uses react-navigation and hooks on the client and the server: