Bump postcss and expo

[dependabot]

Bumps postcss to 8.5.23 and updates ancestor dependency expo. These dependencies need to be updated together.

Updates postcss from 8.4.49 to 8.5.23

Release notes

Sourced from postcss's releases.

8.5.23

• Do not load source map without opts.from for security reasons.

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

8.5.15

• Fixed declaration parsing performance (by @​homanp).

8.5.14

• Fixed custom syntax regression (by @​43081j).

8.5.13

• Fixed postcss-scss commend regression.

8.5.12

• Fixed reading any file via user-generated CSS.
• Added opts.unsafeMap to disable checks.

8.5.11

• Fixed nested brackets parsing performance (by @​offset).

8.5.10

• Fixed XSS via unescaped </style> in non-bundler cases (by @​TharVid).

... (truncated)

Changelog

Sourced from postcss's changelog.

8.5.23

• Do not load source map without opts.from for security reasons.

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

8.5.15

• Fixed declaration parsing performance (by @​homanp).

8.5.14

• Fixed custom syntax regression (by @​43081j).

8.5.13

... (truncated)

Commits

• eb9e1fe Release 8.5.23 version
• 9d19c78 Update dependencies
• 7beca13 Does no load source map file without opts.from
• decea51 Typo
• c18e30d Update EM banner
• 98a39ad Update EM banner
• a3e48c4 Release 8.5.22 version
• f49d691 Fix custom property losing its semicolon before a comment (#2117)
• 28e0daf Release 8.5.21 version
• 3d2b4e4 Update dependencies
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for postcss since your current version.

Updates expo from 53.0.20 to 57.0.8

Changelog

Sourced from expo's changelog.

Changelog

Unpublished

🛠 Breaking changes

• Raise minimum Node.js version to ^22.13.0 (#47202 by @​kitten)

🎉 New features

🐛 Bug fixes

• [Android] Fixed expo-fetch race condition causing out-of-order delivery of initial chunks (#42161 by @​matthieugicquel)
• [iOS] Pass the React runtime scheduler to ExpoModulesCore through a weak handle, so dispatching onto the JS thread during a reload no longer risks calling into a scheduler the React instance already destroyed. (#47492 by @​tsapeta)
• Fix expo/fetch on Android sending a single 0x00 byte instead of an empty body for body-less POST/PUT/PATCH requests. (#46678 by @​zoontek)
• Fix iOS build against React Native 0.87+ by dropping the legacy architecture (bridge) RCTRootViewFactoryConfiguration setup. (#46641 by @​zoontek)
• Include JavaScript and React component stacks in web dev server error logs. (#46584 by @​krystofwoldrich)
• Decompress gzip / br / zstd expo/fetch responses on Android even when the caller sets their own Accept-Encoding header. (#46398 by @​zoontek)
• Fix bodyUsed leaking across siblings when fetch Response is cloned twice (#46397 by @​zoontek)
• Prevent fatal The stream is not in a state that permits close in expo/fetch when native delivers didComplete/didFailWithError after the consumer has already canceled the body stream. (#44909 by @​safaiyeh)
• Adopted the UIKit scene-based life cycle on iOS so apps built with the iOS 27 SDK launch correctly. (#46733 by @​alanjhughes)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in extensions. (#46799 by @​jakex7)
• Fix asyncRoutes failing on Android and iOS with Requiring unknown module (#46870 by @​hassankhan)
• Fix Response.blob() in expo/fetch throwing when the global Blob is react-native's implementation. (#47538 by @​kudo)
• [iOS] Fix Linking.getInitialURL() returning null and deep links being dropped when a URL cold-starts an app on the UIKit scene life cycle. (#47628 by @​tsapeta)
• Fix import.meta.url being null on web when read after the bundle's synchronous execution (from effects, async code, or dynamic imports). (#47802 by @​zoontek)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in iOSApplicationExtension for widgets. (#47894 by @​jakex7)
• [iOS] Add ExpoBundleConfiguration to derive RCTBundleConfiguration from the normalized bundle URL instead of default shared settings singleton (#48010 by @​kitten)
• [iOS] Resolve the dev server port from the RCTMetroPort Info.plist key at runtime so bare projects without expo-dev-client connect to their own Metro instance instead of defaulting to 8081. (#48098 by @​alanjhughes)

💡 Others

• [Android] ExpoReactHostFactory now passes host handlers' DevSupportManagerFactory to ReactHostImpl. (#47637 by @​alanjhughes)
• Restore RCTHostRuntimeDelegate conformance for react-native-macos (#46420 by @​gabrieldonadel)
• Add explicit react-native/Libraries/Core/InitializeCore import to native runtime entrypoint (#46344 by @​kitten)
• [Internal] Return thenable with sync-bailout for async require calls (#46539 by @​kitten)
• [Internal] Update logbox imports (#46640 by @​kitten)
• Re-export more expo-modules-core APIs (#45987 by @​Wenszel)
• Update URL and URLSearchParams implementation to support IDNA/TR-46 and improve performance. Spec-adherence has increased and few gaps should now be noticeable compared to browsers (#47813 by @​kitten)

56.0.5 — 2026-05-26

💡 Others

• [fetch] Refine CompressionInterceptor.kt code. (#46052 by @​kudo)

56.0.4 — 2026-05-23

This version does not introduce any user-facing changes.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo since your current version.

---

Note

High Risk
Major Expo SDK upgrade (53→57) with tooling targeting RN ~0.86 while the app still pins react-native 0.79.2, creating high risk of native/build breakage and runtime issues in a production wallet app.

Overview
Dependency-only change: bumps expo from SDK 53 to 57.0.8 in package.json, with a full package-lock.json refresh. No app source files are touched.

The lockfile moves the whole Expo toolchain to the v57 line—@expo/cli, @expo/metro-config, babel-preset-expo, expo-modules-core, and related expo-* packages (asset, constants, file-system, font, keep-awake, autolinking). Metro is aligned with 0.84.x via @expo/metro, and dev middleware shifts toward React Native 0.86-era packages (e.g. @react-native/dev-middleware, codegen in babel-preset-expo). postcss is updated to 8.5.23 (with nanoid), largely through the new Metro config stack; lightningcss also jumps to 1.33.x.

Several older Expo CLI transitive deps are dropped from the tree (e.g. dotenv/dotenv-expand, tar, @urql/*, react-native-edge-to-edge as an Expo dependency). babel-preset-expo is reworked around babel-plugin-react-compiler, Hermes parser 0.36, and @react-native/babel-plugin-codegen 0.86.0 instead of the previous @react-native/babel-preset 0.79.5 path.

Review focus: confirm React Native 0.79.2 (still pinned in package.json) is compatible with Expo 57’s expectations, and run full iOS pod install and Android release builds plus smoke tests on native modules used by the wallet.

^{Reviewed by Cursor Bugbot for commit db5a9e9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	expo@​53.0.20 ⏵ 57.0.8	-6		+23	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @react-native/debugger-frontend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/[email protected] → npm/@react-native/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/[email protected] → npm/@react-native/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm node-forge is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/[email protected] → npm/@walletconnect/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Low adoption: npm fetch-nodeshim Location: Package overview From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit db5a9e9. Configure here.}

[cursor]

Expo 57 mismatches React Native

High Severity

Raising expo to ^57.0.8 while react-native remains 0.79.2 pairs an SDK built for React Native 0.86 with an older runtime and Metro stack. Native modules, autolinking, and bundling can fail at build time or misbehave at runtime after this dependency-only bump.

 

^{Reviewed by Cursor Bugbot for commit db5a9e9. Configure here.}