NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4048 most downloaded on npm
Routers to help build custom navigators
Last release 4 days ago
02 Oct 2026
Release timing varies
gaps range from 9 days to 2 months
Some releases are documented
notes for 13 of 27 stable releases
82 versions withdrawn
withdrawn after publishing
7 years old
146 releases · first in 2019
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
One column per quarter.
fix paths in sourcemap files (368e069) - by @satya164
handle merge: true with NAVIGATION_DEPRECATED in TabRouter (e5cf73d) - by @satya164
handle merge: true with NAVIGATION_DEPRECATED in TabRouter (e5cf73d) - by @satya164
feat!: add popTo method for stack and remove going back behaviour of (c9c2163) - by @satya164
refactor!: drop support for key property in navigate (61c53bb) - by @satya164
navigate method navigated back if the screen
already exists in the stack. I have seen many people get confused by this
behavior. This behavior is also used for sending params to a previous
screen in the documentation. However, it's also problematic since it could
either push or pop the screens based on the scenario.This removes the going back behavior from navigate and adds a new method
popTo to go back to a specific screen in the stack.
The methods now behave as follows:
navigate(screenName) will stay on the current screen if the screen is
already focused, otherwise push a new screen to the stack.popTo(screenName) will go back to the screen if it exists in the stack,
otherwise pop the current screen and add this screen to the stack.navigate, you can use the getId
prop in which case it'll go to the screen with the matching ID and push or
pop screens accordingly.key to navigate to, e.g.
navigation.navigate({ key: 'someuniquekey' }). It's problematic since key is an internal
implementation detail and created by the library internally - which makes it weird to use. None
of the other actions support such usage either.In addition, we have already added a better API (getId) which can be used for similar use
cases - and gives users full control since they provide the ID and it's not autogenerated by the
library.
So this change removes the key option from the navigate action.
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
add a navigationKey prop to Screen and Group
Nothing published for this version
Nothing published for this version
don't merge initial params when merge !== true
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
default to backBehavior: firstRoute for TabRouter
Following this the following exports have been renamed as well:
The old behaviour can still be achieved by passing merge: true explicitly:
CommonActions.navigate({
name: 'bar',
params: { fruit: 'orange' },
merge: true,
})
initialParams specified for the screen are always merged.
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
add a merge option to navigate to control merging params
Nothing published for this version
handle pushing a route with duplicate key
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
add openByDefault option to drawer
separate normal exports and type exports
Nothing published for this version
add keys to routes missing keys during reset
Nothing published for this version
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
### Bug Fixes * add licenses
Nothing published for this version
Note: Version bump only for package @react-navigation/routers
Note: Version bump only for package @react-navigation/routers
Your coding agent can read these notes before it upgrades. Set up the MCP server →