Jest moduleNameMapper Resolution with Environment-Specific Path Aliases

Context

A project uses moduleNameMapper to alias internal packages with absolute paths that resolve on developer machines. The same configuration fails in the production CI pipeline because the mapped paths do not exist in the container filesystem.

Goal

Define a single moduleNameMapper configuration that resolves correctly in both local development and the production build environment without maintaining duplicate config files.

Constraints

• Local paths use /Users/<user>/project/packages/* while CI uses /workspace/packages/*.
• The alias pattern ^@internal/(.*)$ must map to the correct physical location in each environment.
• Jest version is 29.x; roots and moduleDirectories are already set.

Open Questions

1. Can moduleNameMapper accept a function or environment variable interpolation to compute the target path at runtime?
2. Does Jest provide a built-in mechanism to resolve aliases relative to rootDir instead of absolute paths?
3. If neither is supported, what is the recommended pattern for sharing a single jest.config across heterogeneous filesystems?