-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run prod error at 0.36.0rc3 #9450
Comments
I believe this is a duplicate of #9457 . Please check if downgrading to Node 12 fixes the problem. |
OS: win10 64 OS:win10 64 The same error,@villebro,Thanks! |
I have same error , too |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
superset version: 0.36.rc3
python version: 3.7.7
node.js version: 13.12.0
npm version: 6.14.4
F:\superset-dev\superset-frontend>npm run prod
Starting type checking service...
Using 1 worker with 2048MB memory limit
591 modules
ERROR in ./src/SqlLab/index.jsx 23:16
Module parse failed: Unexpected token (23:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import App from './App';
|
ERROR in ./src/welcome/index.jsx 23:16
Module parse failed: Unexpected token (23:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import App from './App';
|
ERROR in ./src/profile/index.jsx 23:16
Module parse failed: Unexpected token (23:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import App from './App';
|
ERROR in ./src/addSlice/index.jsx 23:16
Module parse failed: Unexpected token (23:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import App from './App';
|
ERROR in ./src/showSavedQuery/index.jsx 39:4
Module parse failed: Unexpected token (39:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| ReactDom.render(
| <Form
| schema={config.JSONSCHEMA}
ERROR in ./src/dashboard/index.jsx 42:16
Module parse failed: Unexpected token (42:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| );
|
ERROR in ./src/explore/index.jsx 44:16
Module parse failed: Unexpected token (44:16)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| );
|
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache_logs\2020-04-02T10_02_26_178Z-debug.log
The text was updated successfully, but these errors were encountered: