Rob Hogan

One thing to watch out for - casting to `Number` will lose precision because javascript's `Number` can't store a full S2 cell ID (hence the use of [`long`](https://www.npmjs.com/package/long) in this...

Sorry if this isn't clear. The default naming convention is lifted from the parent Java implementation, but every attribute name can be customised by setting public properties of your `GeoDataManagerConfiguration`...

Hi @FrederickEngelhardt - `extraNodeModules` isn't intended to override the module entry point, it's designed to allow metro to find modules located outside the usual places. For your use case, you...

Could someone who's experiencing this please post: - Output of `yarn list` or `npm list -a` - Contents of `metro.config.js` - Contents of `babel.config.js` This does look like we're trying...

Thanks @nabtron > npm list -a is huge, with only one possible warning in it I'm actually more interested in the package versions you have - my working theory is...

Yes, this is down to incompatibility of older versions of Metro with Node 17+. Contrary to the original issue report here, I haven't seen a reproduction for Node

*Note that this API changed in [0.68](https://github.com/facebook/metro/releases)* @VictorQueiroz - your use case sounds similar to the one mentioned in [the docs](https://facebook.github.io/metro/docs/configuration/#resolverequest) - the crucial point is to chain to the...

Hi @VictorQueiroz - glad you found a solution for your use case. I'm not exactly sure what problem you're seeing - are you saying `context.resolveRequest` isn't defined within your custom...

Ah I see - if you `init` a new React Native app today you'll get `[email protected]` (latest stable) which includes `[email protected]`, so the metro docs **prior to 0.68** apply. Unfortunately,...

Hi @swrobel, thanks for the report. This is probably not directly a Metro issue but we've seen something similar internally. Is this something that's just recently started occurring, as far...