next-theme / next-theme/plugins

pnpm 无法安装吗?

Open
#279 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2
Forks
3
PR merge metrics
No merged PRs in 30d

Description

pnpm i @next-theme/plugins

 WARN  Issues with peer dependencies found
.
└─┬ @next-theme/plugins 8.19.1
  ├─┬ disqusjs 3.0.2
  │ ├── ✕ missing peer react@"^16.11.0 || ^17.0.0 || ^18.0.0"
  │ ├── ✕ unmet peer preact@^10.7.1: found 8.1.0
  │ └─┬ zustand 4.5.0
  │   ├── ✕ missing peer react@>=16.8
  │   └─┬ use-sync-external-store 1.2.0
  │     └── ✕ missing peer react@"^16.8.0 || ^17.0.0 || ^18.0.0"
  ├─┬ gitalk 1.8.0
  │ └─┬ react-flip-move 2.9.14
  │   ├── ✕ missing peer react@"0.13.x || 0.14.x || 15.x.x"
  │   └── ✕ missing peer react-dom@"0.13.x || 0.14.x || 15.x.x"
  └─┬ quicklink 2.3.0
    ├── ✕ missing peer react@^16.8.0
    └── ✕ missing peer react-dom@^16.8.0
✕ Conflicting peer dependencies:
  react
  react-dom

Done in 1.7s
Progress: resolved 556, reused 555, downloaded 0, added 0, done

pnpm hexo g

INFO  Validating config
NexT version 8.19.1
Documentation: https://theme-next.js.org
========================================
INFO  Start processing
WARN  The following packages are not found by `@next-theme/plugins`.
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/animejs'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/@fortawesome/fontawesome-free'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/mathjax'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/katex'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/@next-theme/pjax'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/@fancyapps/ui'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/medium-zoom'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/lozad'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/pangu'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/quicklink'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/disqusjs'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/gitalk'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/firebase'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/algoliasearch'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/instantsearch.js'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/hexo-generator-searchdb'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/pdfobject'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/mermaid'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/animate.css'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/pace-js'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/ribbon.js'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/@creativecommons/vocabulary'
WARN  ENOENT: no such file or directory, stat 'D:\learn\gitRep\blog\node_modules\/wavedrom'
WARN  Maybe you can find the solution here: https://github.com/next-theme/plugins#debug
INFO  Files loaded in 315 ms

package.json 的依赖

"dependencies": {
    "@next-theme/plugins": "^8.19.1",
    "hexo": "^7.1.0",
    "hexo-generator-archive": "^2.0.0",
    "hexo-generator-category": "^2.0.0",
    "hexo-generator-index": "^3.0.0",
    "hexo-generator-tag": "^2.0.0",
    "hexo-renderer-ejs": "^2.0.0",
    "hexo-renderer-marked": "^6.0.0",
    "hexo-renderer-stylus": "^3.0.0",
    "hexo-server": "^3.0.0",
    "hexo-theme-next": "^8.19.1"
  }

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

Reproduce the reported install and generation commands with the dependencies shown in package.json. Start by checking the peer-dependency warnings and the missing packages reported by @next-theme/plugins, then verify whether the issue is in installation or plugin discovery. Done means the supported setup is clear and generation completes without the reported missing-package warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.