Rob Hogan

We've only seen this with multiple Metro installations (specifically, `metro@>=0.72.0` and `metro@ First: it wasn't an issue until I had to update metro to 0.72 This might hint at the...

Hi @SlyryD, thanks for the report and PR - this is a little surprising because afaik scoped packages have been fully supported for some time. I'll take a look tomorrow...

Hi @SlyryD - I just checked out the repro. `"browser": { "util": "./lib/polyfills/util.js" }` This isn't standard `node_modules` resolution, is it? It looks like https://github.com/defunctzombie/package-browser-field-spec#replace-specific-files---advanced , which Metro doesn't support...

> Does that mean a check needs to be reintroduced? Good question. My TLDR suggestion would be "no, leave this to Metro". Checking Watchman versions isn't trivial, both because new...

> @robhogan no problem, thanks for the suggestions, I've applied them! Is there some tooling that we could use to automate this? Kind of like prettier but for package.json? 😅...

Reopening as this was reverted due to an (apparently) missing internal dependency that previously worked transitively. Meta folks: See D40716713 before re-landing.

> @robhogan quick check, anything I can do to help get this in? do you want me to rebase it on top of main? Sorry about this, nothing you can...

This looks like an issue with the way `@expo/cli` is installed or being executed - the paths look like it's running from a global location and unfortunately as I'm no...

@renet - looks like you’ve done a great job updating this neglected library for newer AWS SDKs. Would you like maintainer access here?

1) You'll need the dev dependencies to build. Build tools (like Metro) themselves are typically dev dependencies. 2) That's fine, because Metro will only bundle files in use by your...