Closed WesselvanGils closed 1 year ago
We no longer use that dependency, and haven't in quite some time (the NPM package was last updated in 2021). Unfortunately, we are unable to update the package at this time, so I would recommend running npm install
on the repository URL (you'll get a much more up to date installation without this issue).
NPM installs seem to work fine, however I am using yarn. I tried installing from the repository with the latest commit. This however seems to have a different failing point for some reason.
# This file contains the result of Yarn building a package (pokemon-showdown@https://github.com/smogon/pokemon-showdown.git#commit=ba6fdee2608e7b06bbd13beb2cc11f8730763314)
# Script name: postinstall
> pokemon-showdown@0.11.7 build
> node build
config.js does not exist. Creating one with default settings...
node:fs:584
handleErrorFromBinding(ctx);
^
Error: ENOENT: no such file or directory, open 'config/config-example.js'
at Object.openSync (node:fs:584:3)
at NodeFS.openSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:4242:24)
at makeCallSync.subPath.subPath (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:6298:26)
at ZipOpenFS.makeCallSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:6929:14)
at ZipOpenFS.openSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:6297:17)
at VirtualFS.openSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:5885:24)
at PosixFS.openSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:5885:24)
at NodePathFS.openSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:5885:24)
at Object.readFileSync (node:fs:452:35)
at NodeFS.readFileSync (\Documents\Documents\Coding\pokemon-project\.pnp.cjs:4537:24) {
errno: -4058,
syscall: 'open',
code: 'ENOENT',
path: 'config/config-example.js'
}
Node.js v19.3.0
I am unsure as to why it states version 0.11.7 when building from the latest commit though.
When installing the pokemon-showdown package with
yarn add pokemon-showdown
yarn
it creates the following erros:
When running the explain peer requirements command it results in:
From what I could gather online, this has to be solved by the developers of the package.