question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Having trouble running the webui

See original GitHub issue

I installed the most recent node.js 7.2 and webpack 2.1.0 beta 27 and after I install the dependencies, I get the following error. Any idea what I need to do to fix it? Thanks! It’s really great of you to open source this!

Webpack is watching the files…

Hash: 30c04c184e14f933f9c3 Version: webpack 2.1.0-beta.27 Time: 460ms Asset Size Chunks Chunk Names bundle.js 5.29 kB 0 [emitted] main + 1 hidden modules

ERROR in ./App/index.js Module build failed: ReferenceError: [BABEL] c:\wamp64\nodejs\javascript-obfuscator-ui-master\App\index.js: Unknown option: c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\react\react.js.Children. Check out http://babeljs.io/docs/usage/options/ for more information about options.

A common cause of this error is the presence of a configuration options object without the corresponding preset name. Example:

Invalid: { presets: [{option: value}] } Valid: { presets: [['presetName', {option: value}]] }

For more detailed information on preset configuration, please see http://babeljs.io/docs/plugins/#pluginpresets-options. (While processing preset: “c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\react\react.js”) at Logger.error (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\logger.js:41:11) at OptionManager.mergeOptions (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:221:20) at c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:260:14 at c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:329:22 at Array.map (native) at OptionManager.resolvePresets (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:270:20) at OptionManager.mergePresets (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:259:10) at OptionManager.mergeOptions (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:244:14) at OptionManager.init (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\options\option-manager.js:374:12) at File.initOptions (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\index.js:216:65) at new File (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\file\index.js:139:24) at Pipeline.transform (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-core\lib\transformation\pipeline.js:46:16) at transpile (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-loader\lib\index.js:41:20) at Object.module.exports (c:\wamp64\nodejs\javascript-obfuscator-ui-master\node_modules\babel-loader\lib\index.js:138:12)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:16

github_iconTop GitHub Comments

1reaction
milovantinecommented, Apr 17, 2017

Thanks Tiago, this is awesome!

By the way, if someone is looking for this error while running “npm run webpack:dev”:

0% compiling Webpack is watching the files…

69% building modules 850/851 modules 1 active …pt-obfuscator-ui/App/styles/main.lessKilled

The solution is: Increase or add a swapfile to your server!

Cheers.

1reaction
paul-dev8commented, Nov 29, 2016

So, quick summary for those wanting to follow in my footsteps…

Download the code from repo Unpack Install yarn if it doesn’t exist with npm install -g yarn Edit the package.json file and delete the line with fsevents Run yarn in the downloaded directory It should get through all the dependencies and when it errors out because of the missing copy and delete commands, go ahead and copy the files it’s referencing in the errors to the appropriate places. npm run webpack:run Open a new console and go to the ui directory and do “node server.js” Go to a browser and open 127.0.0.1:3000

Read more comments on GitHub >

github_iconTop Results From Across the Web

The Amlen WebUI is not working - Eclipse
There are several common reasons why the Amlen WebUI might not work. Is the Amlen WebUI container running in your Docker environment? If...
Read more >
Troubleshooting Web UI Issues - ADM Help Centers
The following issues might arise when first starting the Web UI ... This can happen if the AccuRev Server is not responding or...
Read more >
Trouble Running webui-user.bat (Not working) #391 - GitHub
I opened the "webui-user.bat" and it failed to run. I have an AMD Radeon RX 580 so for the "COMMANDLINE_ARGS=", I used the...
Read more >
WEBUI not found/running - Google Groups
Problem accessing /webui/. Reason: Server Error. Caused by: org.zkoss.zk.ui.UiException: Page not found: /theme/underpin_theme/preference.zul
Read more >
Webui not running? - Web-UI - MineOS Forum
First the background: Installed a fresh CentOS 7 box and after updates added MineOS. Installation seemed to go fine with the only issues...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found