Closed paulvanharen closed 1 year ago
Hi @paulvanharen. Thank you for the report. Can you try running npm run build
?
Hi @eschutho, I've tried installing npm
to be able to run npm run build
as per your suggestion, but I think I need some more guidance to make this work.
Running npm run build
in the root of superset immediately returns, complaining that there is no 'package.json' file. Running in superset-frontend
first alerts that cross-env
is missing. After fixing this, npm
starts building, producing a lot of warnings. The most concerning one appears to be the following:
[webpack-cli] /home/paul/workspace/IoT2/superset2.1/superset-frontend/tools/eslint-plugin-theme-
colors/index.js:74
const rawValue = node?.value?.raw;
^
SyntaxError: Unexpected token '.'
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at ConfigArrayFactory._loadPlugin (/home/paul/workspace/IoT2/superset2.1/superset-frontend/node_modules/@eslint/eslintrc/lib/config-array-factory.js:1036:42)
at /home/paul/workspace/IoT2/superset2.1/superset-frontend/node_modules/@eslint/eslintrc/lib/config-array-factory.js:908:33
at Array.reduce (<anonymous>)
Unfortunately, at the end of this build and (re-) starting superset, the results remain the same. The superset page is broken and the static
directory is empty.
npm
has version 8.5.1.
cross-env
is in the npm dev dependencies. The error you're showing there looks like some JS is not compiling right with babel/webpack (the syntax is perfectly fine as far as I see). Can you cd
into superset-frontend
, and then run npm ci
followed by npm run build
? Also, what OS are you running, out of curiosity?
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.
The warnings are expected. As long as you don't see any errors you should be fine. Does this doc better help outline these steps? https://github.com/apache/superset/pull/23199
@paulvanharen Did you find any solution ? @eschutho Why close this without a resolution ? Errors are still there and docs are not pointing out any workaround as of now.
After a clean install of the release candidate 2.1.0RC01, superset doesn't launch correctly.
How to reproduce the bug
Expected results
No errors nor major warnings during installation. When launching the welcome page at http://localhost:8088/superset/welcome/, a clean formatted page.
Actual results
pip install .
is cleansuperset db upgrade
mentions that no PIL installation was found. This is easily fixed by addingpillow
to the install requirements.superset db upgrade
also warnsScreenshots
Environment