[build-tools] use frozen lockfile for node modules install for SDK 52+ and RN 0.76+

[szdziedzic]

Why

https://exponent-internal.slack.com/archives/C02123T524U/p1731420965266849?thread_ts=1731420501.834709&cid=C02123T524U
https://exponent-internal.slack.com/archives/C02123T524U/p1731421835879399

We want to use frozen lockfile when installing node_modules on our CI.

How

Enable using frozen lockfile for SDK 52+ and RN 0.76+ in the install node modules phase.

Check for EAS_NO_FROZEN_LOCKFILE env var to skip using frozen lockfile if set.

Don't use frozen lockfile after prebuild as prebuild can sometimes modify the package.json.

Test Plan

Test locally

[szdziedzic]

• [build-tools] use frozen lockfile for node modules install for SDK 52+ and RN 0.76+ #463 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Kudo]

question: do we need add frozen-lockfile in this installNodeModules.ts?

[Kudo]

the logic looks complicated. maybe refactor some logic out to a function

  const shouldUseFrozenLockfile = Boolean(
    !withoutFrozenLockfile &&
    !ctx.env.EAS_NO_FROZEN_LOCKFILE) ?? useDefaultFrozenLockfile(packageJson);
    
  function useDefaultFrozenLockfile(packageJson: string): boolean {
    const sdkVersion = semver.coerce(packageJson?.dependencies?.expo)?.version;
    const reactNativeVersion = semver.coerce(
      packageJson?.dependencies?.['react-native']
    )?.version;
    if (!sdkVersion || sdkVersion.major < 52) {
      return false;
    }
    if (!reactNativeVersion || reactNativeVersion.major < 76) {
      return false;
    }
    return true;
  }

passing packageJson to the function and we can also save a little time without doing semver parsing when EAS_NO_FROZEN_LOCKFILE=true.