Is your feature request related to a problem? Please describe.
We primarily use geoblaze in a node environment and it always produces the following warning when we import it.
> const geoblaze = require('geoblaze')
Node worker_threads not available. Trying to fall back to tiny-worker polyfill...
undefined
>
It also seems to output an extra undefined message that I don't remember in the past. I don't know if that's something in a new version of the library, or if it has to do with my now use of node v16.16.0
Describe the solution you'd like
I would like to request that these messages be turned off or silenced by default Perhaps it could be removed altogether or put behind a debug/loglevel flag, etc. What happens is this message ends up in our server logs. In addition, we publish a library that uses geoglaze and when users of our library import our library they also get this message.
the undefined seems to only appear when importing directly in the node REPL. Doesn't seem to appear otherwise so can possibly be ignored, and would just disappear if the first message did
Is your feature request related to a problem? Please describe. We primarily use geoblaze in a node environment and it always produces the following warning when we import it.
It also seems to output an extra
undefined
message that I don't remember in the past. I don't know if that's something in a new version of the library, or if it has to do with my now use of node v16.16.0Describe the solution you'd like I would like to request that these messages be turned off or silenced by default Perhaps it could be removed altogether or put behind a debug/loglevel flag, etc. What happens is this message ends up in our server logs. In addition, we publish a library that uses geoglaze and when users of our library import our library they also get this message.
cc @DanielJDufour