paulvanharen commented on issue #23181:
URL: https://github.com/apache/superset/issues/23181#issuecomment-1448129504
Hi @rusackas, running `npm ci` followed by `npm run build` produces
similar / the same results. From the output, I would guess that `npm ci` is
embedded in `npm run build`.
A few things might be noteworthy:
I see tons of warnings like
71 warn EBADENGINE Unsupported engine {
71 warn EBADENGINE package: '@lerna/add@6.1.0',
71 warn EBADENGINE required: { node: '^14.15.0 || >=16.0.0' },
71 warn EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
71 warn EBADENGINE }
There are about 70 in total.
I've about 30 depreciation warnings including
debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a
low-severity ReDos regression when used in a Node.js environment. It is
recommended you upgrade to 3.2.7 or 4.3.1.
(https://github.com/visionmedia/debug/issues/797)
querystring@0.2.0: The querystring API is considered Legacy. new code
should use the URLSearchParams API instead.
mathfn@1.2.0: Use cephes instead, for a more complete and well-tested
module
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.
request@2.88.2: request has been deprecated, see
https://github.com/request/request/issues/3142
@babel/polyfill@7.12.1: 🚨 This package has been deprecated in favor of
separate inclusion of a polyfill and regenerator-runtime (when needed). See the
@babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more
information.
topojson@1.6.27: Use topojson-client, topojson-server or
topojson-simplify directly.
svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
fontsource-fira-code@4.0.0: Package relocated. Please install and
migrate to @fontsource/fira-code.
puppeteer@10.2.0: < 18.1.0 is no longer supported
deprecated core-js@1.2.7: core-js@<3.3 is no longer maintained and not
recommended for usage due to the number of issues. Because of the V8 engine
whims, feature detection in old core-js versions could cause a slowdown up to
100x even if nothing is polyfilled. Please, upgrade your dependencies to the
actual version of core-js.
I also see the recommendation to run `npm audit fix`, which I did and which
resulted in another series of issues.
My computer is running Ubuntu 22.04 LTS.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
