got VS turf

I've used got, and my initial approach to this would have been to add a beforeRequest hook to strip a leading slash. I like the idea of handling this at compile time, though my proposed solution below (particularly the error messages) aren't the prettiest.

Like Python, our Node.js SDK is using a well-known library axios. While it is not quite as ubiquitous as Python's requests, it is very commonly used. For instance, it is used by Auth0 (if you're looking for a different example, Shopify makes use of Got). You can find it configured here. The shared client code takes reqeust and response transform functions for each resource to convert the repsonses to objects.

The properties/methods are also purposely used as a convention to work with responses in libraries like got, so by knowing Request and Response you will have sort of a "shortcut" in the learning process of open sourced tools.

Ah, yes, my apologies. I think the cause is that the latest version of got is not compatible with anything below node v14. I do see the error that you do when I have node v12 selected in my function service, but with v14 I'm able to deploy just fine. Do you still see that error when you click "Deploy" with Node v14 and got@latest?

Is there support for timeouts? It's the main reason I use https://github.com/sindresorhus/got

Things were working fine, and then my Blazor app started making calls to the server using a library called "Got" (https://github.com/sindresorhus/got)

At the moment, axios does not support setting a connection timeout separately from a read timeout, which could be limiting in some scenarios. If you need this functionality, you can try the got library - it allows for separate read and connection timeout specifications.

One of the community plugins we found during that process was signcl/docusaurus-prince-pdf, an npm package leveraging sindresorhus/got to crawl all the documentation and generate a PDF version.

to measure distances and convert between our parameters I'm using TurfJS, for which binding is even more trivial:

Turf.js is an open-source geospatial analysis library that can process various location data, such as the center of gravity and distance calculations.

Isochrones are manually calculated using turf.js assuming 1.2m/s walking speed after the subway trip. These are simple buffers around each station/prior isochrone and do not take the street network into account.

Not to take away from you learning, which I think is awesome, I was wondering if you know about http://turfjs.org/ which provides a lot of simple modules … and is surprisingly hard to find. Their `distance` modules may be relevant in this case.

you can use client side libraries like Turfjs to do buffers https://github.com/Turfjs/turf/tree/master/packages/turf-buffer

Tools: custom Javascript (with heavy use of turf.js) for data processing and creating the 3D model, Blender, 3D printing, lost wax casting

I've integrated https://turfjs.org/ with mapbox before and it was pretty fun

References Amazon Location Service Turf.js MapLibre GL JS Leaflet OpenLayers Cesium Mapbox GL JS