Hi, I received this warning when installing sao using the release tgz into a working trytond installation. sao appears to be working correctly, although I have not tested it extensively. Ufortunately I’m barely familiar with Node, and less so with npm. Is this a real problem, and if so, what is the effect? Thanks.
npm WARN email@example.com requires a peer of grunt@~0.4.5 but none is installed. You must install peer dependencies yourself.
% cd ~/work % wget https://downloads.tryton.org/6.2/tryton-sao-6.2.3.tgz % npm install --production --legacy-peer-deps % tar -xf ~/work/tryton-sao-6.2.3.tgz % mv package sao % cd sao % npm install --production --legacy-peer-deps npm WARN deprecated firstname.lastname@example.org: Package no longer supported. Contact email@example.com for more info. npm WARN deprecated firstname.lastname@example.org: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated email@example.com: 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 firstname.lastname@example.org: this library is no longer supported > email@example.com postinstall /usr/home/dale/work/sao > npx bower install bower not-cached https://github.com/jquery/jquery-dist.git#^3 bower resolve https://github.com/jquery/jquery-dist.git#^3 ...snip... bootstrap#3.4.1 bower_components/bootstrap └── jquery#3.6.0 d3#5.16.0 bower_components/d3 npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN firstname.lastname@example.org requires a peer of grunt@~0.4.5 but none is installed. You must install peer dependencies yourself. npm WARN email@example.com requires a peer of grunt@~0.4.1 but none is installed. You must install peer dependencies yourself. audited 469 packages in 23.898s 11 packages are looking for funding run `npm fund` for details found 17 vulnerabilities (1 low, 9 moderate, 6 high, 1 critical) run `npm audit fix` to fix them, or `npm audit` for details %