wechat-miniprogram / wechat-miniprogram/miniprogram-demo
npm run init --legacy-peer-dep 出错
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.2k
- Forks
- 2.2k
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 2
Description
C:\Users\Administrator\Desktop\demoOfxiaochengxu\miniprogram-demo-master>npm run init --legacy-peer-deps
miniprogram-demo@1.0.0 init
npm run sync && cd cloudfunctions/ && npm i --production && cd ../miniprogram/ && npm i --production
miniprogram-demo@1.0.0 sync
git submodule update --init --recursive
npm WARN config production Use --omit=dev instead.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tencent%2feslint-config-wxapp - Not found
npm ERR! 404
npm ERR! 404 '@tencent/eslint-config-wxapp@^0.5.2' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! E:\npm\node_cache_logs\2023-03-11T16_25_11_349Z-debug-0.log
C:\Users\Administrator\Desktop\demoOfxiaochengxu\miniprogram-demo-master>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported npm run init --legacy-peer-deps command and inspect the initialization output. Trace the dependency request for @tencent/eslint-config-wxapp@^0.5.2 and determine why npm cannot find it in the registry. Done means initialization completes without the E404 failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100