# refactor\(mobile\): drop the custom Metro resolveRequest for @/ · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/84cc687c1d3f9d73f2045ff0b6719dfdf6af81be)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 84cc687c1d3f9d73f2045ff0b6719dfdf6af81be

Requested commit: 84cc687c1d3f9d73f2045ff0b6719dfdf6af81be

Commit: 84cc687c1d3f9d73f2045ff0b6719dfdf6af81be

Tree: 3bb0bfc7d46eae765cf366a3ce9ed00b69e49bf7

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
refactor(mobile): drop the custom Metro resolveRequest for @/

Expo 57 resolves tsconfig compilerOptions.paths in Metro by default
(exp.experiments.tsconfigPaths defaults to true in @expo/cli's
instantiateMetro), and its resolver is importer-scoped: it skips
requests originating in node_modules, which the plain prefix hook was
not. Verified by exporting both platforms from apps/mobile: iOS Bundled
(3886 modules) and Android Bundled (4041 modules).

Co-authored-by: Apex <noreply@callstack.com>

```

## Parents

- [2efab1e0defdfd5c4de78fc718a3eb2dca21653c](https://git.cafe/pingdotgg/t3code/commit/2efab1e0defdfd5c4de78fc718a3eb2dca21653c?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/84cc687c1d3f9d73f2045ff0b6719dfdf6af81be?format=markdown)