Closed paulmenzel closed 4 days ago
What branch are you running? I have removed the package-lock on Sep 25.
Sorry, I guess git log --no-decorate --oneline -1
was buried in the output.
$ git log --no-decorate --oneline -1
7c5094c feat/make-transcription-configurable (#195)
$ git branch --contains 7c5094c
* main
Sorry my bad, i will check it soon.
Since package-lock.json has been removed i am closing this issue.
It looks like npm install yarn
creates package-lock.json
.
$ date && npm install yarn
Mon Nov 18 14:21:30 CET 2024
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 @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
added 672 packages, and audited 673 packages in 19m
196 packages are looking for funding
run `npm fund` for details
8 high severity vulnerabilities
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
$ ls -l --full-time package-lock.json
-rw-rw---- 1 pmenzel pmenzel 309158 2024-11-18 14:40:43.035570399 +0100 package-lock.json
By running a global install of yarn it will not generate a package lock file : npm install -g yarn This is not an issue with edumeet, but rather the method you use install yarn.
(Alternatively you can just remove tha lock file after you installed yarn.)
yarn prints the warning below: