The Night Before You Submit: Which Dependencies to Check First, in Five Steps Anyone Can Follow
Upgrading every library the night before submission is how crashes that only hit old devices slip into a release. Here is the order I settled on in my own wallpaper apps: check what the stores decide first, and write down what you chose not to upgrade.
I counted how many versions expo install starts recommending after one patch bump
What expo install recommends is tied to the patch version of expo itself. I measured the ledger diff against the npm registry, how far npm install drifts, and the one check worth adding to a generated project.
When an Expo UI drop-in swap actually removes a dependency
Expo UI went stable in SDK 56 with drop-in replacements for eight community packages. Swapping one import does not always shrink your dependency list. Here is how to decide which swaps actually pay off, straight from the dependency graph.
What Renovate may bump in an Expo app, and what it must never touch
Turning on automated dependency updates in a Rork-generated app also hands Renovate the 123 packages Expo SDK 57 pins. Measured on 2026-07-30, six of them sit a full major version behind npm latest. Here is how to generate the ignore list from the SDK instead of maintaining it by hand.
Auditing the Dependencies Rork Generates: A Supply-Chain Hygiene Routine
Even a four-screen Rork app pulls in 900+ transitive dependencies. Before a vulnerability lands and you cannot tell which app is affected, build an audit habit with npm ls, npm audit, overrides, and depcheck — framed for running several apps at once.
Fixing Expo Dependency Errors in Rork Apps
A practical guide to resolving Expo dependency conflicts and errors in Rork-generated applications. Learn to fix version mismatches, installation failures, and compatibility issues.