Expo strategy extend to use app.config.js(ts) file in addition to app.json

[dmi3y]

Latest version of Expo allows to use dynamic config file such as app.config.js(ts) instead of app.json. Here is documentation link https://docs.expo.dev/versions/latest/config/app/

In essence this is superset of app.json and has very similar structure for versioning e.g.

.....
export default {
  expo: {
    name: NAME,
    slug: SLUG,
    privacy: "unlisted",
    platforms: ["ios"],
    version: "1.0.0", // x-release-please-version
    orientation: "portrait",
    scheme: SCHEME,
    icon: "./assets/icon.png",
    updates: {
      fallbackToCacheTimeout: 30000,
      url: URL
    },
    assetBundlePatterns: ["**/*"],
    ios: {
      bundleIdentifier: IDENTIFIER
      supportsTablet: true,
      buildNumber: "1.0.0", // x-release-please-version
      runtimeVersion: {
        policy: "sdkVersion",
      },
    },
    description: DESCRIPTION
    extra: {
      eas: {
        projectId: PROJECT_ID,
      },
    },
    owner: "OWNER",
  },
};

Is your feature request related to a problem? Please describe.
When using dynamic config file app.config.js(ts) version is not being updated, unless tagging lines with version using x-release-please-version and adding app.config.js(ts) as an extra file.

Describe the solution you'd like
No need to use extra configuration with extra file.

Describe alternatives you've considered
Adding extra file with target lines works just fine.

Additional context
If you are using release please github action v4 and it's not picking up extra file, consider this undocumented behavior.

[dmi3y]

Though, now I'm thinking, for the dynamic files it might be more efficient to get version from imported package.json. Might be just worth mentioning in the docs.

Will test it on my side and report if that will not work.