堆

了解如何使用 Expo Router 中的 Stack 导航器。

Using a Stack Navigator with Expo Router

Navigate between screens, pass params between screens, create dynamic routes, and configure the screen titles and animations.

堆栈导航器是在应用中的路由之间导航的基本方式。在 Android 上，堆叠路由会在当前屏幕顶部动画。在 iOS 上，堆叠路由从右侧动画显示。Expo Router 提供了一个 Stack 导航组件，可创建导航堆栈并允许你在应用中添加新路由。

¥A stack navigator is the foundational way of navigating between routes in an app. On Android, a stacked route animates on top of the current screen. On iOS, a stacked route animates from the right. Expo Router provides a Stack navigation component that creates a navigation stack and allows you to add new routes in your app.

本指南提供有关如何在项目中创建 Stack 导航器以及自定义单个路由的选项和标题的信息。

¥This guide provides information on how you can create a Stack navigator in your project and customize an individual route's options and header.

开始使用

¥Get started

你可以使用基于文件的路由来创建堆栈导航器。这是一个示例文件结构：

¥You can use file-based routing to create a stack navigator. Here's an example file structure:

app

_layout.tsx

index.tsx

details.tsx

此文件结构生成一个布局，其中 index 路由是堆栈中的第一个路由，而 details 路由在导航时被推到 index 路由的顶部。

¥This file structure produces a layout where the index route is the first route in the stack, and the details route is pushed on top of the index route when navigated.

你可以使用 app/_layout.tsx 文件通过以下两个路由定义应用的 Stack 导航器：

¥You can use the app/_layout.tsx file to define your app's Stack navigator with these two routes:

app/_layout.tsx

import { Stack } from 'expo-router';

export default function Layout() {
  return <Stack />;
}

屏幕选项和标题配置

¥Screen options and header configuration

静态配置路由选项

¥Statically configure route options

你可以在布局组件路由中使用 <Stack.Screen name={routeName} /> 组件来静态配置路由的选项。这对 tabs 或 drawers 也很有用，因为它们需要提前定义图标。

¥You can use the <Stack.Screen name={routeName} /> component in the layout component route to statically configure a route's options. This is also useful for tabs or drawers as they need an icon defined ahead of time.

app/_layout.tsx

import { Stack } from 'expo-router';

export default function Layout() {
  return (
    <Stack
      screenOptions={{
        headerStyle: {
          backgroundColor: '#f4511e',
        },
        headerTintColor: '#fff',
        headerTitleStyle: {
          fontWeight: 'bold',
        },
      }}>
      {/* Optionally configure static options outside the route.*/}
      <Stack.Screen name="home" options={{}} />
    </Stack>
  );
}

作为 <Stack.Screen> 组件的替代方案，你可以使用 navigation.setOptions() 从路由的组件文件中配置路由的选项。

¥As an alternative to the <Stack.Screen> component, you can use navigation.setOptions() to configure a route's options from within the route's component file.

app/index.tsx

import { Stack, useNavigation } from 'expo-router';
import { Text, View } from 'react-native';
import { useEffect } from 'react';

export default function Home() {
  const navigation = useNavigation();

  useEffect(() => {
    navigation.setOptions({ headerShown: false });
  }, [navigation]);

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Text>Home Screen</Text>
    </View>
  );
}

配置标题栏

¥Configure header bar

你可以使用 screenOptions 属性配置 Stack 导航器中所有路由的标题栏。这对于在所有路由上设置通用标题样式很有用。

¥You can configure the header bar for all routes in a Stack navigator by using the screenOptions prop. This is useful for setting a common header style across all routes.

app/_layout.tsx

import { Stack } from 'expo-router';

export default function Layout() {
  return (
    <Stack
      screenOptions={{
        headerStyle: {
          backgroundColor: '#f4511e',
        },
        headerTintColor: '#fff',
        headerTitleStyle: {
          fontWeight: 'bold',
        },
      }}
    />
  );
}

要为单个路由动态配置标题栏，请在路由文件中使用该导航器的 <Stack.Screen> 组件。这对于更改 UI 的交互很有用。

¥To configure the header bar dynamically for an individual route, use that navigator's <Stack.Screen> component in the routes's file. This is useful for interactions that change the UI.

app/index.tsx

import { Link, Stack } from 'expo-router';
import { Image, Text, View, StyleSheet } from 'react-native';

function LogoTitle() {
  return (
    <Image style={styles.image} source={{ uri: 'https://rn.nodejs.cn/img/tiny_logo.png' }} />
  );
}

export default function Home() {
  return (
    <View style={styles.container}>
      <Stack.Screen
        options={{
          title: 'My home',
          headerStyle: { backgroundColor: '#f4511e' },
          headerTintColor: '#fff',
          headerTitleStyle: {
            fontWeight: 'bold',
          },

          headerTitle: props => <LogoTitle {...props} />,
        }}
      />
      <Text>Home Screen</Text>
      <Link href={{ pathname: 'details', params: { name: 'Bacon' }}}>Go to Details</Link>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
  },
  image: {
    width: 50,
    height: 50,
  },
});

可用的标头选项

¥Available header options

Stack 导航器支持全面的标题配置选项。以下是所有可用的标头相关选项：

¥The Stack navigator supports comprehensive header configuration options. Below are all the header-related options available:

Header options

Option	Platform	Description
`header`	Android iOS	Custom header to use instead of the default header. This accepts a function that returns a React Element to display as a header. The function receives an object containing the following properties as the argument: `navigation` - The navigation object for the current screen. `route` - The route object for the current screen. `options` - The options for the current screen `back` - Options for the back button, contains an object with a `title` property to use for back button label. To set a custom header for all the screens in the navigator, you can specify this option in the `screenOptions` prop of the navigator. Note that if you specify a custom header, the native functionality such as large title, search bar etc. won't work.
`headerBackButtonDisplayMode`	iOS	How the back button displays icon and title. Supported values: "default" - Displays one of the following depending on the available space: previous screen's title, generic title (e.g. 'Back') or no title (only icon). "generic" – Displays one of the following depending on the available space: generic title (e.g. 'Back') or no title (only icon). "minimal" – Always displays only the icon without a title. The space-aware behavior is disabled when: The iOS version is 13 or lower Custom font family or size is set (e.g. with `headerBackTitleStyle`) Back button menu is disabled (e.g. with `headerBackButtonMenuEnabled`) In such cases, a static title and icon are always displayed.
`headerBackButtonMenuEnabled`	iOS	Boolean indicating whether to show the menu on longPress of iOS >= 14 back button. Defaults to `true`.
`headerBackground`	Android iOS	Function which returns a React Element to render as the background of the header. This is useful for using backgrounds such as an image or a gradient.
`headerBackImageSource`	Android iOS	Image to display in the header as the icon in the back button. Defaults to back icon image for the platform A chevron on iOS An arrow on Android
`headerBackTitle`	iOS	Title string used by the back button on iOS. Defaults to the previous scene's title, "Back" or arrow icon depending on the available space. See `headerBackButtonDisplayMode` to read about limitations and customize the behavior. Use `headerBackButtonDisplayMode: "minimal"` to hide it.
`headerBackTitleStyle`	iOS	Style object for header back title. Supported properties: `fontFamily` `fontSize`
`headerBackVisible`	Android iOS	Whether the back button is visible in the header. You can use it to show a back button alongside `headerLeft` if you have specified it. This will have no effect on the first screen in the stack.
`headerBlurEffect`	iOS	Blur effect for the translucent header. The `headerTransparent` option needs to be set to `true` for this to work. Supported values: `extraLight`, `light`, `dark`, `regular`, `prominent`, `systemUltraThinMaterial`, `systemThinMaterial`, `systemMaterial`, `systemThickMaterial`, `systemChromeMaterial`, `systemUltraThinMaterialLight`, `systemThinMaterialLight`, `systemMaterialLight`, `systemThickMaterialLight`, `systemChromeMaterialLight`, `systemUltraThinMaterialDark`, `systemThinMaterialDark`, `systemMaterialDark`, `systemThickMaterialDark`, `systemChromeMaterialDark`
`headerLargeStyle`	iOS	Style of the header when a large title is shown. The large title is shown if `headerLargeTitle` is `true` and the edge of any scrollable content reaches the matching edge of the header. Supported properties: backgroundColor
`headerLargeTitle`	iOS	Whether to enable header with large title which collapses to regular header on scroll. Defaults to `false`. For large title to collapse on scroll, the content of the screen should be wrapped in a scrollable view such as `ScrollView` or `FlatList`. If the scrollable area doesn't fill the screen, the large title won't collapse on scroll. You also need to specify `contentInsetAdjustmentBehavior="automatic"` in your `ScrollView`, `FlatList` etc.
`headerLargeTitleShadowVisible`	Android iOS	Whether drop shadow of header is visible when a large title is shown.
`headerLargeTitleStyle`	iOS	Style object for large title in header. Supported properties: `fontFamily` `fontSize` `fontWeight` `color`
`headerLeft`	Android iOS	Function which returns a React Element to display on the left side of the header. This replaces the back button. See `headerBackVisible` to show the back button along side left element.
`headerRight`	Android iOS	Function which returns a React Element to display on the right side of the header.
`headerSearchBarOptions`	iOS	Options to render a native search bar on iOS. Search bars are rarely static so normally it is controlled by passing an object to `headerSearchBarOptions` navigation option in the component's body. You also need to specify `contentInsetAdjustmentBehavior="automatic"` in your `ScrollView`, `FlatList` etc. If you don't have a `ScrollView`, specify `headerTransparent: false`. Supported properties are: ref Ref to manipulate the search input imperatively. It contains the following methods: `focus` - focuses the search bar `blur` - removes focus from the search bar `setText` - sets the search bar's content to given value `clearText` - removes any text present in the search bar input field `cancelSearch` - cancel the search and close the search bar autoCapitalize Controls whether the text is automatically auto-capitalized as it is entered by the user. Possible values: `none` `words` `sentences` `characters` Defaults to `sentences`. autoFocus Whether to automatically focus search bar when it's shown. Defaults to `false`. barTintColor The search field background color. By default bar tint color is translucent. tintColor The color for the cursor caret and cancel button text. cancelButtonText The text to be used instead of default `Cancel` button text. disableBackButtonOverride Whether the back button should close search bar's text input or not. Defaults to `false`. hideNavigationBar Boolean indicating whether to hide the navigation bar during searching. Defaults to `true`. hideWhenScrolling Boolean indicating whether to hide the search bar when scrolling. Defaults to `true`. inputType The type of the input. Defaults to `"text"`. Supported values: `"text"`, `"phone"`, `"number"`, `"email"` obscureBackground Boolean indicating whether to obscure the underlying content with semi-transparent overlay. Defaults to `true`. placeholder Text displayed when search field is empty. textColor The color of the text in the search field. hintTextColor The color of the hint text in the search field. headerIconColor The color of the search and close icons shown in the header shouldShowHintSearchIcon Whether to show the search hint icon when search bar is focused. Defaults to `true`. onBlur A callback that gets called when search bar has lost focus. onCancelButtonPress A callback that gets called when the cancel button is pressed. onChangeText A callback that gets called when the text changes. It receives the current text value of the search bar.
`headerShadowVisible`	Android iOS	Whether to hide the elevation shadow (Android) or the bottom border (iOS) on the header.
`headerShown`	Android iOS	Whether to show the header. The header is shown by default. Setting this to `false` hides the header.
`headerStyle`	Android iOS	Style object for header. Supported properties: `backgroundColor`
`headerTintColor`	Android iOS	Tint color for the header. Changes the color of back button and title.
`headerTitle`	Android iOS	String or a function that returns a React Element to be used by the header. Defaults to `title` or name of the screen. When a function is passed, it receives `tintColor` and`children` in the options object as an argument. The title string is passed in `children`. Note that if you render a custom element by passing a function, animations for the title won't work.
`headerTitleAlign`	Android iOS	How to align the header title. Possible values: `left` `center` Defaults to `left` on platforms other than iOS. Not supported on iOS. It's always `center` on iOS and cannot be changed.
`headerTitleStyle`	Android iOS	Style object for header title. Supported properties: `fontFamily` `fontSize` `fontWeight` `color`
`headerTransparent`	Android iOS	Boolean indicating whether the navigation bar is translucent. Defaults to `false`. Setting this to `true` makes the header absolutely positioned - so that the header floats over the screen so that it overlaps the content underneath, and changes the background color to `transparent` unless specified in `headerStyle`. This is useful if you want to render a semi-transparent header or a blurred background. Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically. To get the height of the header, you can use `HeaderHeightContext` with React's Context API or `useHeaderHeight`.
`title`	Android iOS	String that can be used as a fallback for `headerTitle`.

动态设置屏幕选项

¥Set screen options dynamically

要动态配置路由选项，你始终可以使用该路由文件中的 <Stack.Screen> 组件。

¥To configure a route's option dynamically, you can always use the <Stack.Screen> component in that route's file.

作为替代方案，你也可以使用命令式 API 的 router.setParams() 函数动态配置路由。

¥As an alternative, you can also use the imperative API's router.setParams() function to configure the route dynamically.

app/details.tsx

import { Stack, useLocalSearchParams, useRouter } from 'expo-router';
import { View, Text, StyleSheet } from 'react-native';

export default function Details() {
  const router = useRouter();
  const params = useLocalSearchParams();

  return (
    <View style={styles.container}>
      <Stack.Screen
        options={{
          title: params.name,
        }}
      />
      <Text
        onPress={() => {
          router.setParams({ name: 'Updated' });
        }}>
        Update the title
      </Text>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
  },
});

标题按钮

¥Header buttons

你可以使用 headerLeft 和 headerRight 选项向标题添加按钮。这些选项接受在标题中渲染的 React 组件。

¥You can add buttons to the header by using the headerLeft and headerRight options. These options accept a React component that renders in the header.

app/index.tsx

import { Stack } from 'expo-router';
import { Button, Text, Image, StyleSheet } from 'react-native';
import { useState } from 'react';

function LogoTitle() {
  return (
    <Image style={styles.image} source={{ uri: 'https://rn.nodejs.cn/img/tiny_logo.png' }} />
  );
}

export default function Home() {
  const [count, setCount] = useState(0);

  return (
    <>
      <Stack.Screen
        options={{
          headerTitle: props => <LogoTitle {...props} />,
          headerRight: () => <Button onPress={() => setCount(c => c + 1)} title="Update count" />,
        }}
      />
      <Text>Count: {count}</Text>
    </>
  );
}

const styles = StyleSheet.create({
  image: {
    width: 50,
    height: 50,
  },
});

其他屏幕选项

¥Other screen options

有关所有可用其他屏幕选项（包括动画、手势和其他配置）的完整列表：

¥For a complete list of all available other screen options including animations, gestures, and other configurations:

Screen options

Option	Platform	Description
`animation`	Android	How the screen should animate when pushed or popped. Supported values: `default`, `fade`, `fade_from_bottom`, `flip`, `simple_push`, `slide_from_bottom`, `slide_from_right`, `slide_from_left`, `none`
`animationDuration`	iOS	Changes the duration (in milliseconds) of `slide_from_bottom`, `fade_from_bottom`, `fade` and `simple_push` transitions on iOS. Defaults to `350`. The duration of `default` and `flip` transitions isn't customizable.
`animationMatchesGesture`	iOS	Whether the gesture to dismiss should use animation provided to `animation` prop. Defaults to `false`. Doesn't affect the behavior of screens presented modally.
`animationTypeForReplace`	Android iOS	The type of animation to use when this screen replaces another screen. Defaults to `push`. Supported values: `push`, `pop`
`autoHideHomeIndicator`	iOS	Boolean indicating whether the home indicator should prefer to stay hidden. Defaults to `false`.
`contentStyle`	Android iOS	Style object for the scene content.
`freezeOnBlur`	iOS	Boolean indicating whether to prevent inactive screens from re-rendering. Defaults to `false`. Defaults to `true` when `enableFreeze()` from `react-native-screens` package is run at the top of the application. Only supported on iOS and Android.
`fullScreenGestureEnabled`	iOS	Whether the gesture to dismiss should work on the whole screen. Using gesture to dismiss with this option results in the same transition animation as `simple_push`. This behavior can be changed by setting `customAnimationOnGesture` prop. Achieving the default iOS animation isn't possible due to platform limitations. Defaults to `false`. Doesn't affect the behavior of screens presented modally.
`fullScreenGestureShadowEnabled`	Android iOS	Whether the full screen dismiss gesture has shadow under view during transition. Defaults to `true`. This does not affect the behavior of transitions that don't use gestures enabled by `fullScreenGestureEnabled` prop.
`gestureDirection`	iOS	Sets the direction in which you should swipe to dismiss the screen. Supported values: `vertical`, `horizontal` When using `vertical` option, options `fullScreenGestureEnabled: true`, `customAnimationOnGesture: true` and `animation: 'slide_from_bottom'` are set by default.
`gestureEnabled`	iOS	Whether you can use gestures to dismiss this screen. Defaults to `true`.
`navigationBarColor`	Android	This option is deprecated and will be removed in a future release (for apps targeting Android SDK 35 or above edge-to-edge mode is enabled by default and it is expected that the edge-to-edge will be enforced in future SDKs, see here for more information). Sets the navigation bar color. Defaults to initial status bar color.
`navigationBarHidden`	Android	Boolean indicating whether the navigation bar should be hidden. Defaults to `false`.
`orientation`	Android	The display orientation to use for the screen. Supported values: `default`, `all`, `portrait`, `portrait_up`, `portrait_down`, `landscape`, `landscape_left`, `landscape_right`
`presentation`	Android	How should the screen be presented. Supported values: `card`, `modal`, `transparentModal`, `containedModal`, `containedTransparentModal`, `fullScreenModal`, `formSheet`
`sheetAllowedDetents`	Android	Works only when `presentation` is set to `formSheet`. Describes heights where a sheet can rest. Supported values: `fitToContents` Defaults to `[1.0]`.
`sheetCornerRadius`	Android	Works only when `presentation` is set to `formSheet`. The corner radius that the sheet will try to render with. If set to non-negative value it will try to render sheet with provided radius, else it will apply system default. If left unset, system default is used.
`sheetElevation`	Android	Works only when `presentation` is set to `formSheet`. Integer value describing elevation of the sheet, impacting shadow on the top edge of the sheet. Not dynamic - changing it after the component is rendered won't have an effect. Defaults to `24`.
`sheetExpandsWhenScrolledToEdge`	iOS	Works only when `presentation` is set to `formSheet`. Whether the sheet should expand to larger detent when scrolling. Defaults to `true`. Please note that for this interaction to work, the ScrollView must be "first-subview-chain" descendant of the Screen component. This restriction is due to platform requirements.
`sheetGrabberVisible`	iOS	Works only when `presentation` is set to `formSheet`. Boolean indicating whether the sheet shows a grabber at the top. Defaults to `false`.
`sheetInitialDetentIndex`	Android	Works only when `presentation` is set to `formSheet`. Index of the detent the sheet should expand to after being opened. If the specified index is out of bounds of `sheetAllowedDetents` array, in dev environment more errors will be thrown, in production the value will be reset to default value. Additionaly there is `last` value available, when set the sheet will expand initially to last (largest) detent. Defaults to `0` - which represents first detent in the detents array.
`sheetLargestUndimmedDetentIndex`	Android	Works only when `presentation` is set to `formSheet`. The largest sheet detent for which a view underneath won't be dimmed. This prop can be set to an number, which indicates index of detent in `sheetAllowedDetents` array for which there won't be a dimming view beneath the sheet. Additionaly there are following options available: `none` - there will be dimming view for all detents levels, `last` - there won't be a dimming view for any detent level. Defaults to `none`, indicating that the dimming view should be always present.
`statusBarAnimation`	Android	Sets the status bar animation (similar to the `StatusBar` component). Defaults to `fade` on iOS and `none` on Android. Supported values: `"fade"`, `"none"`, `"slide"` On Android, setting either `fade` or `slide` will set the transition of status bar color. On iOS, this option applies to appereance animation of the status bar. Requires setting `View controller-based status bar appearance -> YES` (or removing the config) in your `Info.plist` file.
`statusBarBackgroundColor`	Android	This option is deprecated and will be removed in a future release (for apps targeting Android SDK 35 or above edge-to-edge mode is enabled by default and it is expected that the edge-to-edge will be enforced in future SDKs, see here for more information). Sets the background color of the status bar (similar to the `StatusBar` component).
`statusBarHidden`	Android	Whether the status bar should be hidden on this screen. Requires setting `View controller-based status bar appearance -> YES` (or removing the config) in your `Info.plist` file.
`statusBarStyle`	Android	Sets the status bar color (similar to the `StatusBar` component). Defaults to `auto`. Supported values: `"auto"`, `"inverted"`, `"dark"`, `"light"` Requires setting `View controller-based status bar appearance -> YES` (or removing the config) in your `Info.plist` file.
`statusBarTranslucent`	Android	This option is deprecated and will be removed in a future release (for apps targeting Android SDK 35 or above edge-to-edge mode is enabled by default and it is expected that the edge-to-edge will be enforced in future SDKs, see here for more information). Sets the translucency of the status bar (similar to the `StatusBar` component). Defaults to `false`.

自定义推送行为

¥Custom push behavior

默认情况下，Stack 导航器在推送堆栈中已有的路由时会删除重复的屏幕。例如，如果你两次按下同一个屏幕，第二次按下将被忽略。你可以通过向 <Stack.Screen> 提供自定义 getId() 函数来更改此推送行为。

¥By default, the Stack navigator removes duplicate screens when pushing a route that is already in the stack. For example, if you push the same screen twice, the second push will be ignored. You can change this push behavior by providing a custom getId() function to the <Stack.Screen>.

例如，以下布局结构中的 index 路由显示应用中不同用户配置文件的列表。让我们将 [details] 路由设为动态路由，以便应用用户可以导航查看配置文件的详细信息。

¥For example, the index route in the following layout structure shows a list of different user profiles in the app. Let's make the [details] route a dynamic route so that the app user can navigate to see a profile's details.

app

_layout.tsx

index.tsx

[details].tsxmatches dynamic paths like '/details1'

每次应用用户导航到不同的配置文件时，Stack 导航器都会推送一个新屏幕，但会失败。如果你提供每次都返回新 ID 的 getId() 函数，则每次应用用户导航到个人资料时，Stack 都会推送一个新屏幕。

¥The Stack navigator will push a new screen every time the app user navigates to a different profile but will fail. If you provide a getId() function that returns a new ID every time, the Stack will push a new screen every time the app user navigates to a profile.

你可以在布局组件路由中使用 <Stack.Screen name="[profile]" getId={}> 组件来修改推送行为：

¥You can use the <Stack.Screen name="[profile]" getId={}> component in the layout component route to modify the push behavior:

app/_layout.tsx

import { Stack } from 'expo-router';

export default function Layout() {
  return (
    <Stack>
      <Stack.Screen
        name="[profile]"
        getId={
          ({ params }) => String(Date.now())
        }
      />
    </Stack>
  );
}

删除堆栈屏幕

¥Removing stack screens

你可以使用不同的操作来关闭和删除堆栈中的一个或多个路由。

¥There are different actions you can use to dismiss and remove one or many routes from a stack.

`dismiss` 行动

¥dismiss action

关闭最近堆栈中的最后一个屏幕。如果当前屏幕是堆栈中的唯一路由，它将关闭整个堆栈。

¥Dismisses the last screen in the closest stack. If the current screen is the only route in the stack, it will dismiss the entire stack.

你可以选择传递一个正数来关闭指定数量的屏幕。

¥You can optionally pass a positive number to dismiss up to that specified number of screens.

Dismiss 与 back 不同，因为它针对最近的堆栈而不是当前导航器。如果你有嵌套导航器，调用 dismiss 将带你返回多个屏幕。

¥Dismiss is different from back as it targets the closest stack and not the current navigator. If you have nested navigators, calling dismiss will take you back multiple screens.

app/settings.tsx

import { Button, View } from 'react-native';
import { useRouter } from 'expo-router';

export default function Settings() {
  const router = useRouter();

  const handleDismiss = (count: number) => {
    router.dismiss(count)
  };

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button title="Go to first screen" onPress={() => handleDismiss(3)} />
    </View>
  );
}

`dismissTo` 行动

¥dismissTo action

dismissTo 已添加到 Expo Router 4.0.8 中。它的操作类似于 Expo Router v3 中的 navigation 函数。

¥dismissTo was added in Expo Router 4.0.8. It operates similarly to the navigation function in Expo Router v3.

在达到指定的 Href 之前，关闭当前 <Stack /> 中的屏幕。如果历史记录中没有 Href，则将改为执行 push 操作。

¥Dismisses screens in the current <Stack /> until the specified Href is reached. If the Href is absent in the history, a push action will be performed instead.

例如，考虑 /one、/two、/three 路由的历史记录，其中 /three 是当前路由。操作 router.dismissTo('/one') 将导致历史记录回溯两次，而 router.dismissTo('/four') 将 push 历史记录转发到 /four 路由。

¥For example, consider the history of /one, /two, /three routes, where /three is the current route. The action router.dismissTo('/one') will cause the history to go back twice, while router.dismissTo('/four') will push the history forward to the /four route.

app/settings.tsx

import { Button, View, Text } from 'react-native';
import { useRouter } from 'expo-router';

export default function Settings() {
  const router = useRouter();

  const handleDismissAll = () => {
    router.dismissTo('/')
  };

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button title="Go to first screen" onPress={handleDismissAll} />
    </View>
  );
}

`dismissAll` 行动

¥dismissAll action

要返回最近堆栈中的第一个屏幕。这与 popToTop 堆栈操作类似。

¥To return to the first screen in the closest stack. This is similar to popToTop stack action.

例如，home 路由是第一个屏幕，settings 是最后一个。要从 settings 转到 home 路由，你必须返回 details。但是，使用 dismissAll 操作，你可以从 settings 转到 home 并关闭中间的任何屏幕。

¥For example, the home route is the first screen, and the settings is the last. To go from settings to home route you'll have to go back to details. However, using the dismissAll action, you can go from settings to home and dismiss any screen in between.

app/settings.tsx

import { Button, View, Text } from 'react-native';
import { useRouter } from 'expo-router';

export default function Settings() {
  const router = useRouter();

  const handleDismissAll = () => {
    router.dismissAll()
  };

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button title="Go to first screen" onPress={handleDismissAll} />
    </View>
  );
}

`canDismiss` 行动

¥canDismiss action

要检查是否可以关闭当前屏幕。如果路由位于堆栈中，并且堆栈历史记录中有多个屏幕，则返回 true。

¥To check if it is possible to dismiss the current screen. Returns true if the router is within a stack with more than one screen in the stack's history.

app/settings.tsx

import { Button, View } from 'react-native';
import { useRouter } from 'expo-router';

export default function Settings() {
  const router = useRouter();

  const handleDismiss = (count: number) => {
    if (router.canDismiss()) {
      router.dismiss(count)
    }
  };

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button title="Maybe dismiss" onPress={() => handleDismiss()} />
    </View>
  );
}

与 Native Stack Navigator 的关系

¥Relation with Native Stack Navigator

Expo Router 中的 Stack 导航器封装了 React Navigation 中的原生堆栈导航器。Native Stack Navigator 中可用的选项在 Expo Router 中的 Stack 导航器中均可用。

¥The Stack navigator in Expo Router wraps the Native Stack Navigator from React Navigation. Options available in the Native Stack Navigator are all available in the Stack navigator in Expo Router.

使用 @react-navigation/stack 的 JavaScript 堆栈

¥JavaScript stack with @react-navigation/stack

你还可以使用 JavaScript 驱动的 @react-navigation/stack 库通过将此库与 withLayoutContext 封装在一起来创建自定义布局组件。

¥You can also use the JavaScript-powered @react-navigation/stack library to create a custom layout component by wrapping this library with the withLayoutContext.

在以下示例中，JsStack 组件是使用 @react-navigation/stack 库定义的：

¥In the following example, JsStack component is defined using @react-navigation/stack library:

layouts/js-stack.tsx

import { ParamListBase, StackNavigationState } from '@react-navigation/native';
import {
  createStackNavigator,
  StackNavigationEventMap,
  StackNavigationOptions,
} from '@react-navigation/stack';
import { withLayoutContext } from 'expo-router';

const { Navigator } = createStackNavigator();

export const JsStack = withLayoutContext<
  StackNavigationOptions,
  typeof Navigator,
  StackNavigationState<ParamListBase>,
  StackNavigationEventMap
>(Navigator);

定义 JsStack 组件后，你可以在应用中使用它：

¥After defining the JsStack component, you can use it in your app:

app/_layout.tsx

import { JsStack } from '../layouts/js-stack';

export default function Layout() {
  return (
    <JsStack
      screenOptions={
        {
          %%placeholder-start%%... %%placeholder-end%%
        }
      }
    />
  );
}

有关可用选项的更多信息，请参阅 @react-navigation/stack 文档。

¥For more information on available options, see @react-navigation/stack documentation.

堆

开始使用

屏幕选项和标题配置

静态配置路由选项

配置标题栏

可用的标头选项

动态设置屏幕选项

标题按钮

其他屏幕选项

自定义推送行为

删除堆栈屏幕

dismiss 行动

dismissTo 行动

dismissAll 行动

canDismiss 行动

与 Native Stack Navigator 的关系

使用 @react-navigation/stack 的 JavaScript 堆栈

`dismiss` 行动

`dismissTo` 行动

`dismissAll` 行动

`canDismiss` 行动