Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Does 'tilelive' belong to dependencies ?

未关闭
#68 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
backend

调研方向

先安装 tilelive-vector,然后复现彼此独立的 tilelive 实例,再将其依赖声明与 tilelive-mapnik 进行比较。跟踪 tilelive-vector 如何加载 sources,以及如何发现已注册的 test: 协议。确定预期的依赖或注册行为,并修复 issue 或将其清楚地记录下来,即表示完成。

由索引模型根据 Issue 内容生成。

描述

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

主要语言
JavaScript
星标
72
派生
42
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

mapbox/tilelive-vector 的其他 Issue

查看 mapbox/tilelive-vector 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。