vitesse-webext: some problems about branch:refactor/mv3 until 2022/11/22
Describe the bug
some problems about branch:refactor/mv3 until 2022/11/22
I downloaded the latest source code:
❯ npx degit antfu/vitesse-webext#refactor/mv3 antfu@vitesse-webext_mv3_202211
problem 1
there is a ERR_PNPM_FETCH_404
error when using pnpm to install.
❯ pnpm i
Lockfile is up-to-date, resolution step is skipped
Packages: +893
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
WARN GET https://registry.npmjs.org/@nodelib/fs.scandir/-/@nodelib/fs.scandir-2.1.5.tgz error (ERR_PNPM_FETCH_404). Will retry in 10 seconds. 2 retries left.
WARN GET https://registry.npmjs.org/@nodelib/fs.scandir/-/@nodelib/fs.scandir-2.1.5.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.
ERR_PNPM_FETCH_404 GET https://registry.npmjs.org/@nodelib/fs.scandir/-/@nodelib/fs.scandir-2.1.5.tgz: Not Found - 404
No authorization header was set for the request.
Progress: resolved 893, reused 891, downloaded 0, added 0
but it’s normal if turn to yarn.
problem 2
scripts/client.ts
line:12
const socketHost = `localhost:3303`
the socket port is hardcoded, so If the port is set by env variables, the follwoing error would occur:
client.ts:26
WebSocket connection to 'ws://localhost:3303/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
problem3
HMR is not stable, sometimes the changed reflected immediately, but sometimes, the changes can’t be rendered in time. especially when continuously change the code. I haven’t found what’s the problem is. @tmkx
Reproduction
reproduction
System Info
System:
OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (8) x64 Intel Core Processor (Haswell, no TSX, IBRS)
Memory: 25.33 GB / 31.35 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.0/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
Browsers:
Chrome: 103.0.5060.53
Firefox: 105.0
Used Package Manager
yarn
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 24
Problem1. remove
pnpm-lock.yaml
and try install againProblem2. can be solved
Problem3. HMR is unstable in MV3 as expected because the implementation is a little tricky, and that’s why it’s still not merged into main branch. needs more investigation.