code does not build any more, many errors

[frudman]

From a clean clone (git clone https://github.com/ulfsri/neris-nodejs-client) I did as follows:

cd neris-nodejs-client
npm install

There were errors and warnings right away (unlike a few weeks/months ago when I successfully built this client):

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated stringify-package@1.0.1: This module is not used anymore, and has been replaced by @npmcli/package-json
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)

> @ulfsri/neris-nodejs-client@1.0.15 prepare
> npm run generate && npm run build


> @ulfsri/neris-nodejs-client@1.0.15 generate
> openapi-typescript https://api.neris.fsri.org/openapi.json --default-non-nullable false --enum-values=true --output src/neris-api.d.ts

✨ openapi-typescript 7.9.1
 ✘  Can't resolve $ref at #/components/schemas/_PatchRemovalActionProperties/properties/room_type/anyOf/0/discriminator/mapping/set
 ✘  Can't resolve $ref at #/components/schemas/_PatchRemovalActionProperties/properties/room_type/anyOf/0/discriminator/mapping/set
file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/dist/lib/redoc.mjs:74
      throw new Error(errorMessage);
            ^

Error: Can't resolve $ref at #/components/schemas/_PatchRemovalActionProperties/properties/room_type/anyOf/0/discriminator/mapping/set
    at _processProblems (file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/dist/lib/redoc.mjs:74:13)
    at validateAndBundle (file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/dist/lib/redoc.mjs:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async openapiTS (file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/dist/index.mjs:40:18)
    at async generateSchema (file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/bin/cli.js:132:5)
    at async main (file:///Users/freddy/devx/RRVFC/neris-nodejs-client/node_modules/openapi-typescript/bin/cli.js:249:20)

Node.js v23.7.0
npm error code 1
npm error path /Users/freddy/devx/RRVFC/neris-nodejs-client
npm error command failed
npm error command sh -c npm run generate && npm run build
npm error A complete log of this run can be found in: /Users/freddy/.npm/_logs/2025-12-13T13_41_41_683Z-debug-0.log

The most important one being the $ref one (Can't resolve $ref at #/components/schemas/_PatchRemovalActionProperties/properties/room_type/anyOf/0/discriminator/mapping/set) since that blocks moving forward at all.

Is this a new problem?

[frudman]

(meant to add: no further steps worked, obviously (e.g. tried to node build.mjs and npm run generate_test) and that did not work, similar errors (with openapi-typescript 7.9.1)

[frudman]

UPDATE: was able to get past the error by downloading the schema directly, removing the offending bit (discriminator in "_PatchRemovalActionProperties", around line 33443 when json-formatted with vscode) then it worked.
Guessing the source schema was changed recently (since it worked fine a few weeks ago)? Else not clear why it references $ref (that part seems to be good, verified that all refs were there) as an error.

MAYBE consider using an explicit copy of the schema directly in this repo so you can control the build process. Then reference the actual location for production code/schema (e.g. https://api.neris.fsri.org/openapi.json) to prevent issues like this where an error can creep in from a different place