In Chapter 1, Meet NW.js, we saw how to fix the libudev.so.0 issue, but there are a few other common issues addressed in the NW.js Wiki page:
Audio issues: This might depend on using nonfree media formats, such as MP3; check Chapter 4, Data Persistence Solutions and Others Browser Web APIs, for more information on the subject.
Video issues: Your video card might be blacklisted; in that case, run NW.js by passing the
--ignore-gpu-blacklistattribute inside thechromium-argsobject in the manifest file. If it still does not work, it might be due to the lack of a DLL library; try copyingd3dx9_43.dllandd3dcompiler_43.dllfrom the Chrome installer.DevTools are not showing: As stated previously, DevTools are run on a local instanced server. Proxy settings or custom host configurations might interfere with their visualization.
JavaScript blocks CSS animations: JavaScript and CSS animations run inside the same thread. You can change this behavior by adding the
--enable...