cli-tools: Use resolver alongside resolveNodeModuleDir

[Downchuck]

Describe the Feature

The CLI can use resolvers to find node module folders for dependencies in addition to the current search heuristic.

Node.js whether using ESM or CJS has require.resolve or import.meta.resolve -- this technique is already being used in the CLI, just not for the node modules resolution on dependencies. The method simply resolves packageName/package.json then gets the directory name.

Possible Implementations

While ESM may not be relevant, if it is used, the path returned by a resolver is a url,

import {fileURLToPath} from "node:url";

const resolvedUrl = import.meta.resolve("packageName/package.json");
console.log(fileURLToPath(resolvedUrl));

With CJS, and this is code already in the code base:

path.dirname(
      require.resolve('@react-native-community/example/package.json'),
),

A little simpler - as there are packages that define exports and an entry point (such as @react-navigation/bottom-tabs) - using import.meta.resolve("@react-navigation/bottom-tabs") will give the entry point, and one can still traverse up to the nearest package.json file (e.g. package-up).

Context

The find-up usage in findPackageDependencyDir is fine, but the resolver also makes sense, either as the first lookup option or as a fallback.

[szymonrybczak]

@Downchuck what's the issue that you're trying to resolve with this one? Usage with other package manager e.g. pnpm?