Errors with npm install

[Natedude]

Here is what I got when I did "npm install" in the lobe browser extension repo folder. Note, I am on macOS Mojave 10.14.6. Might this have a min req of 10.15 macOS? I edited it slightly for readability.

I did have a weird thing with npm and node disappearing recently. I use Node Version Manager (nvm) to manage all my node related and npm installations. Before doing running this command though, I reinstalled and updated to (base) ~:nathanhildum$ node --version v16.13.0

(base) ~:nathanhildum$ npm --version 8.5.5

• just noticing this may be an extremely old version of npm so I will reinstall and update everything again and try again.

https://pastebin.com/AR0dzNzE (I posted it here because gh said it was too long for a post)

and the log file seemingly doesn't exist. Also I noticed my node and npm dissapeared again. but now I have the latest

(base) ~:nathanhildum$ nvm install node
v18.9.0 is already installed.
Now using node v18.9.0 (npm v8.19.1)

Any help is greatly appreciated!

[Natedude]

Ok. This is what I just got

(base) lobe-chrome-extension-main:nathanhildum$ npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated fsevents@2.1.3: "Please update to latest v2.3 or v2.2"
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
(##################) ⠸ reify:typescript: timing reifyNode:node_modules/lodash Completed in 3451ms

---

aaahhggg, that appeaared, then a moment later this appeared:

---

Then I got a nearly identical print out

https://pastebin.com/JkyGGZdM

[Natedude]

I'll give some of this a close read and see if the answer if staring me in the face.

[lemillermicrosoft]

Yeah sorry I don't have min versions and pre-reqs listed, would need to take a closer look. Just in case, reminder you can use the zipped built extension locally if you were just looking to use it, without needing to build it yourself.