HuolalaTech / page-spy-web

Debug remotely and easily like chrome devtools.
https://www.pagespy.org
MIT License
4.55k stars 271 forks source link

After publishing my own version, I can't install it by pnpm #177

Closed hilinc closed 6 months ago

hilinc commented 6 months ago

Describe the bug

Refer to this issue, https://github.com/HuolalaTech/page-spy-web/issues/172

I clone page-spy-web adn rewrite vite config base option. Locally, verification is successful using yarn start:client, and the service can be accessed through a custom base path. It is built using yarn build:client. The yarn version is 1.22.19. It is published through npm at https://www.npmjs.com/package/p-page-spy-web.

I can't install it using npm 8.19.3 or pnpm 7.20.0, I got the following error:

npm ERR! code 1
npm ERR! path /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web
npm ERR! command failed
npm ERR! command sh -c -- bash scripts/public-files.sh
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/@huolala-tech/page-spy-browser/dist/iife/index.min.js: No such file or directory
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/@huolala-tech/page-spy-plugin-rrweb/dist/iife/index.min.js: No such file or directory
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/@huolala-tech/page-spy-plugin-data-harbor/dist/iife/index.min.js: No such file or directory
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/source-map/dist/source-map.js: No such file or directory
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/source-map/lib/mappings.wasm: No such file or directory
npm ERR! cp: /Users/workspace/tools-service/packages/page-spy/node_modules/p-page-spy-web/node_modules/shiki: No such file or directory

Steps to reproduce

No response

System Info

npm 8.19.3
yarn 1.22.19
pnpm 7.20.0
node 16.14.0

Logs

No response

Validations

gamefake588 commented 6 months ago

C:\Users\DELL>node -v v16.14.2

C:\Users\DELL>npm -v 8.5.0

wqcstrong commented 6 months ago

172 will be fixed in the next version.

I don't have a idea about what you want to do, so if you want to:

hilinc commented 6 months ago

172 will be fixed in the next version.

I don't have a idea about what you want to do, so if you want to:

No worries, I have just modified my nginx configuration, and now I can access it via a sub-path.