Can't get metro-resolver-symlinks to work

[donaldkwong]

I'm having trouble getting metro-resolver-symlinks to work with importing modules in my monorepo with symlinks. My RN app is currently in /apps/app1 and I want to import a module in /modules/module1. I ran npm i ../../modules/module1 in the app directory and the package.json and package-lock.json files have been updated with the new dependency. I also see a symlink created in the node_modules directory. I can even add an import statement in my .tsx file and pull in some symbols to use in my code. I followed the directions and made the corresponding changes to metro.config.js. However, when I try to run the app (with npm run ios), metro complains that the module can't be resolved. Am I doing something wrong?

[tido64]

Hi @donaldkwong, do you have a repro we can have a look at? What does your metro.config.js look like? Did you add an entry for the modules folder in your config, under watchFolders?

[donaldkwong]

Hey, thanks for the quick response. I don't have an easy repro, unfortunately. However, adding the folders to watchFolders did work. I was under the assumption that I wouldn't have to keep that updated if I used metro-resolver-symlinks. Is that not the case?

[tido64]

Metro only interfaces with an internal mapping of the file system. This mapping is provided by a file watcher, like Watchman. For a package to be correctly resolved, it must also be watched. This is a Metro implementation detail that we cannot get around (yet).

[donaldkwong]

FWIW, the documentation here implies that watchFolders doesn't need to be specified anymore: