msgbyte / msgbyte/tailchat

编译文件的时候报错了

Open
#278 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.6k
Forks
398
Avg merge
1h 14m
Merged PRs (30d)
2

Description

按照文档的内容进行编译

报错相关的日志
root@xxx /www/wwwroot/tailchat-1.11.10 $ pnpm install
Scope: all 76 workspace projects
 WARN  Ignoring broken lockfile at /www/wwwroot/tailchat-1.11.10: Lockfile /www/wwwroot/tailchat-1.11.10/pnpm-lock.yaml not compatible with current pnpm
.../plugin-declaration-generator         |  WARN  deprecated glob@7.2.3
packages/types                           |  WARN  deprecated rimraf@3.0.2
server/packages/sdk                      |  WARN  deprecated minio@7.1.4
apps/cli                                 |  WARN  deprecated glob@8.1.0
 WARN  deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
server                                   |  WARN  deprecated @types/minio@7.1.1
server                                   |  WARN  deprecated @types/mongoose@5.11.97
client/web                               |  WARN  deprecated @types/webpack-dev-server@4.7.2
client/web                               |  WARN  deprecated rollup-plugin-replace@2.2.0
client/web                               |  WARN  deprecated workbox-webpack-plugin@6.6.1
client/web                               |  WARN  deprecated workbox-build@6.6.1
/www/wwwroot/tailchat-1.11.10/client/web:
 ERR_PNPM_FETCH_404  GET https://registry.npmmirror.com/tailchat-shared: Not Found - 404

This error happened while installing a direct dependency of /www/wwwroot/tailchat-1.11.10/client/web

tailchat-shared is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
Progress: resolved 365, reused 333, downloaded 29, added 0
我的编译环境

系统版本:Debian 12_x86_64
nodejs版本:v22.14.0
pnpm版本:10.4.1

Windwos下编译也报此错误

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with pnpm install in client/web, using the documented manual-deployment steps and checking the reported pnpm-lock.yaml warning. Trace why the direct tailchat-shared dependency is fetched from the npm mirror; done means the documented installation succeeds on the reported environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.