getTerrainRgb returns Promise { <state>: "rejected" }

Problem:

the getTerrainRgb method returns a rejected Promise

I’m calling the following inside a useEffect() React hook:

const ioToken = <mytoken>
const tgeo = new ThreeGeo({
                    tokenMapbox: ioToken,
});

async function fetchGeo() {
    const terrain = await tgeo.getTerrainVector(
                        [0.0, 0.0], // [lat, lng]
                        1.0,               // radius of bounding circle (km)
                        13)               // zoom resolution
    fgRef.current.scene().add(terrain)
                    };               

fetchGeo();

what happens The getTerrainRgb method returns a rejected Promise

additional comments The fgRef.current.scene().add() method is from react-force-graph.

I’ve checked that the mapbox API token is valid.

Any ideas why it’s not working?

[JonThom]

@j-devel I can see in the console that the Promise is no longer rejected, so yes, I consider it solved! (I didn’t reply earlier because I encountered another issue - probably not from three-geo - preventing the addition of the terrain to the scene.) Thanks to @Cobertos for the pro debugging and to @j-devel for the fix!

[j-devel]

Thanks @Cobertos for feedback!

• Please don’t strip console.errors from your builds (looks like this is from drop_console in es-pack-js)

Addressed in https://github.com/w3reality/es-pack-js/commit/d93a7432a261712ed058540066d603ab06ea21df

• Don’t reject null, reject with the err so at least the external developer can catch it and act on it.
• Final error seems to be coming from resolveGetPixels. I’m building this with webpack for a browser with Nuxt, so maybe something about the build environment is triggering the wrong code path?

Fixed in cda26f3. The latest v1.4.3 build in dist should just work as far as you use them in browsers.

For NodeJS users, I’ve introduced a new flag option instead of implicitly relying on the crude isNodeJS() method.