.yarnrc.yml

compressionLevel: mixed

enableGlobalCache: false

nodeLinker: node-modules

# Workaround for @signalwire/docusaurus-theme-llms-txt@1.0.0-alpha.9:
# the package declares `react`/`react-dom` ^18 as peerDependencies, but
# docs runs React 19. At runtime it works fine — the peer range is just
# stale in the published alpha. Yarn prints two YN0060 warnings on every
# install; the pattern below silences only those two lines, scoped to
# this package (not a global YN0060 mute).
#
# TODO: when a newer @signalwire/docusaurus-theme-llms-txt ships with
# a React 19-compatible peer range, bump it in docs/package.json and
# remove this filter — we'd rather follow upstream than carry a local
# suppression.
#
# The root workspace declares `expo-router` as a devDependency only to
# force Yarn to hoist it into the root node_modules alongside
# babel-preset-expo. babel-preset-expo calls require.resolve('expo-router')
# from its own location to decide whether to register the expo-router Babel
# plugin; if the two packages live in different node_modules folders (which
# happens when expo-router ends up per-app and babel-preset-expo is hoisted),
# process.env.EXPO_ROUTER_APP_ROOT never gets replaced and Metro fails to
# bundle expo-router/_ctx.ios.js. Because the root workspace doesn't actually
# execute expo-router code, it legitimately doesn't provide its peers — each
# app that consumes expo-router declares them directly. The pattern below
# silences the resulting YN0002 lines about the ROOT workspace only;
# unmet peer warnings from any other workspace still surface.
logFilters:
  - pattern: '*@signalwire/docusaurus-theme-llms-txt*'
    level: discard
  - pattern: "react-native-executorch-monorepo@workspace:. doesn't provide*requested by expo-router*"
    level: discard
  - code: YN0086
    level: discard

yarnPath: .yarn/releases/yarn-4.1.1.cjs