cannot find module './attachDirectiveResolvers

[sanshigongA]

Windows_NT 6.1.7601【Windows server 2008 R2】
PostgreSQL v11.2
nodejs v12.22.12
npm v6.14.16
wiki.js v2.5.304

[NGPixel]

Did you run any npm command?

[sanshigongA]

and open to the setup page in my browser，then error

[sanshigongA]

Did you run any npm command?
The log is:
……
10 silly lifecycle [email protected]start: Args: [ '/d /s /c', 'node server' ]
11 silly lifecycle [email protected]start: Returned: code: 1 signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: node server
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (D:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (D:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid [email protected]
15 verbose cwd D:\wiki-js-windows
16 verbose Windows_NT 6.1.7601
17 verbose argv "D:\Program Files\nodejs\node.exe" "D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v12.22.12
19 verbose npm v6.14.16
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: node server
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[sanshigongA]

Did you run any npm command?

D:\wiki-js-windows>npm list
……
npm ERR! peer dep missing: graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 || ^14.0.0, required by [email protected]
npm ERR! missing: graphql@^14.0.2, required by [email protected]
npm ERR! error in D:\wiki-js-windows\node_modules\@graphql-tools\graphql-tag-pluck\node_modules\@babel\traverse\node_modules\@babel\types: ENOENT: no
such file or directory, open 'D:\wiki-js-windows\node_modules\@graphql-tools\graphql-tag-pluck\node_modules\@babel\traverse\node_modules\@babel\types\
package.json'
npm ERR! invalid: @babel/types D:\wiki-js-windows\node_modules\@graphql-tools\graphql-tag-pluck\node_modules\@babel\traverse\node_modules\@babel\types

npm ERR! missing: @babel/types@^7.25.6, required by @babel/[email protected]
npm ERR! extraneous: @graphql-tools/[email protected] D:\wiki-js-windows\node_modules\@graphql-tools\merge\node_modules\@graphql-tools\merge
npm ERR! missing: @graphql-tools/[email protected], required by @graphql-tools/[email protected]
npm ERR! error in D:\wiki-js-windows\node_modules\@graphql-tools\merge\node_modules\@graphql-tools\schema\node_modules\tslib: ENOENT: no such file or
directory, open 'D:\wiki-js-windows\node_modules\@graphql-tools\merge\node_modules\@graphql-tools\schema\node_modules\tslib\package.json'
npm ERR! invalid: tslib D:\wiki-js-windows\node_modules\@graphql-tools\merge\node_modules\@graphql-tools\schema\node_modules\tslib
npm ERR! missing: tslib@^2.4.0, required by @graphql-tools/[email protected]
npm ERR! error in D:\wiki-js-windows\node_modules\@graphql-tools\relay-operation-optimizer\node_modules\@graphql-tools\utils: ENOENT: no such file or
directory, open 'D:\wiki-js-windows\node_modules\@graphql-tools\relay-operation-optimizer\node_modules\@graphql-tools\utils\package.json'
npm ERR! invalid: @graphql-tools/utils D:\wiki-js-windows\node_modules\@graphql-tools\relay-operation-optimizer\node_modules\@graphql-tools\utils
npm ERR! extraneous: [email protected] D:\wiki-js-windows\node_modules\isomorphic-ws\node_modules\ws

[BPowell76]

@sanshigongA are you not able to update your version of Node and, by extension, npm? You're using an outdated and no longer supported version for both. The current node LTS version is 20.18.0. The current npm version along with it is version 10.8.2.

The version of npm you are running is about 6 years old and some of the dependencies for the packages missing are newer than the version of npm you are running.