Does 'tilelive' belong to dependencies ?

Nobody has claimed this yet.

I've been trying to use tilelive-vector as a tilelive driver (with no much success so far, if there's any example it would be great to see it) and got confused by "tilelive" being included as a dependency of it on "npm install tilelive-vector".

The problem was that I was registering a "test:" protocol to my required tilelive while tilelive-vector uses its own instance of "tilelive" to load the source, thus not finding my own.

Should I register source/backend drivers into the tilelive-vector own instance ?

Note that removing node_modules/tilelive-vector/node_modules/tilelive fixed that issue for me, resulting in tilelive-vector using the tilelive instance in the upper levels.

... I'm sure I'm doing something completely wrong, but anyway decided to file the ticket because tilelive-mapnik (for comparison) does not require 'tilelive' as a dependency

Start by reproducing the separate tilelive instances after installing tilelive-vector, then compare its dependency declaration with tilelive-mapnik. Trace how tilelive-vector loads sources and how a registered test: protocol is discovered. Done means the expected dependency or registration behavior is established and the issue is fixed or clearly documented.

Written by the indexing model from the issue text.