Error while running typescript node using geo-tz in build file

I am using geo-tz in our typescript node application for getting the geolocation details. When i am running the node server locally, it’s working fine but when taken a node server build , i am getting an error like the below while calling geo-tz function like this:

import * as  geoTz from 'geo-tz';
const testGeotz= ()=>{
       try{
           const coords = [110,-20]
            let name = geoTz(coords[1], coords[0])[0];
           }catch (e) {
               console.log(e);
           }
}

Why is it happening like this ? My node version - 12.16.3 geo-tz version - 6.0.0

I even tried downgrading the geo-tz version and tried to upgrade to latest v6.0.1 .Still same response. Please tell me whether I have missed out any dependency . @evansiroky @greenkeeperio-bot

[evansiroky]

We are using nx workspace for running the app and building it . Building will transpile typeScript file into JavaScript (under the hood, its what tsc does)…

This is the issue. node-geo-tz lazy-loads the underlying data by default to attempt to not use so much memory. In whatever build process that is being used, all of the data files must still be able to be referenced as these include the precise data about the timezone boundaries. The reason the error occurs for only certain coordinates is that most coordinates will fall into areas that have the timezones pre-calculated and thus don’t require loading the underlying geographic data to perform an exact lookup near a boundary with the timezones.

I’m going to leave this issue open as I am not sure what the best way to provide guidance is for this use case. The README already states that this package cannot be used in the browser due to loading a lot of data, but it appears that users are trying to build/transpile/whatever on the server-side too. I am not exactly sure what build systems everybody is using and there might be many, but if there is a way to instruct the build process to include every file within the data folder of this project in a way that those files can be required as needed, that should work.

[miguelpfitscher]

This problem is happening here too.

When I use locally, It works. But, when it is build, that happen.