error at 0.36.rc2 npm run prod
See original GitHub issue- superset version: 0.36.rc2
- python version: 3.7.7
- node.js version: 12.16.1
- npm version: 6.11.3
npm run prod or build error:
superset@0.36.0 prod F:\superset-dev\superset-frontend node --max_old_space_size=4096 ./node_modules/webpack/bin/webpack.js --mode=production --colors --progress
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';
|
> ReactDOM.render(<App />, document.getElementById('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';
|
> ReactDOM.render(<App />, document.getElementById('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';
|
> ReactDOM.render(<App />, document.getElementById('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';
|
> ReactDOM.render(<App />, document.getElementById('js-add-slice-container'));
|
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(
> <div>
| <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
| );
|
> ReactDOM.render(<App store={store} />, document.getElementById('app'));
|
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
| );
|
> ReactDOM.render(<App store={store} />, document.getElementById('app'));
|
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! superset@0.36.0 prod: `node --max_old_space_size=4096 ./node_modules/webpack/bin/webpack.js --mode=production --colors --progress`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the superset@0.36.0 prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2020-04-01T07_24_19_026Z-debug.log
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
error at 0.36.rc2 npm run prod #9431 - apache/superset
Starting type checking service... Using 1 worker with 2048MB memory limit 591 modules ERROR in ./src/SqlLab/index.jsx 23:16 Module parse ...
Read more >npm run prod generates an error even though ...
I am creating website with laravel and vue.js. When I run 'npm run dev', there is no error shown in the console. However,...
Read more >node-forge
Start using node-forge in your project by running `npm i node-forge`. ... error: function(connection, error) { console.log('[tls] error', ...
Read more >npm-run-script
Description. This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
Read more >npm-audit
Run a security audit. ... This option does not filter the report output, it simply changes the command's failure threshold. ... npm audit...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
same here any solution for this These issue occurs in the windows environment and present in 0.36.0 build also
It worked on ubuntu。