Rafael de Oleza

Hey @Justin-JHG ! Thanks again for reporting this issue > the line before the new lines was somehow treated as removed line(as in red colour display) so not sure whether...

Thanks for reporting @j-f1 ! After some offline discussion with @j-f1 , he realized that the issue comes from the `lint-staged` npm package. These are the events that I think...

I've confirmed with @j-f1 that `git config stash.usebuiltin false` fixes the issue, so this can be used as a workaround. It's still unclear why does lint-staged executes the system git...

@karanjthakkar maybe we can create a second preset (or an option within the preset) to not transpile modern features, so it can be opt-in. @mjesun may provide some guidance here

Hi! Thanks for reporting! The metro resolution logic (which is powered by `jest-haste-map`) treats any folder with a `package.json` as a global module, so in this case it's mandatory to...

Unfortunately there's no way for plugins to modify the config object, what you can do is implement some util method in `nodejs-mobile-react` that can be used by users to automatically...

Thanks for the PR! ❤️ I'm not super familiar with the module resolution logic, so I will need some time to be able to review it properly. @jeanlauliac: you may...

In RN 0.57 the format of the Metro config options has changed slightly, now the `extraNodeModules` param is inside the `resolver` field (there's more information in [the metro docs](https://facebook.github.io/metro/docs/en/configuration)). @RomualdPercereau...

Hi! We added a util method in the `metro-config` package that should help migrating the old configuration format to the new one. You can call it by doing: ```js const...

Regarding the docs, I agree that having some quick migration guide will be helpful. @mmazzarolo , @brentvatne does any of you want to help creating such quick guide? It can...