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.

(MacOS) "Failed to parse extension manifest" error on start

See original GitHub issue

NWJS Version : 0.38.4 Operating System : MacOS 10.14.5

Expected behavior

App should start without errors on the minimal configuration. (Alt: The Getting Started Guide should provide a stable configuration.)

Actual behavior

When following the steps on the Getting Started Guide and creating an app with the minimal configuration, the user is presented with this error as the app starts through the nw command.

$ nw .
[43133:775:0605/113822.785993:ERROR:component_loader.cc(167)] Failed to parse extension manifest.

Note: nw seems to start as intended except for the error.

How to reproduce

Create a new project folder with two files:

package.json:

{
  "name": "helloworld",
  "main": "index.html"
}

index.html:

<!DOCTYPE html>
<html>
  <head>
    <title>Hello World!</title>
  </head>
  <body>
    <h1>Hello World!</h1>
  </body>
</html>

Install NW.js through npm i -g nw or through downloading it from the website.
In the project dir run nw .
Notice how NW starts as usual.

The error appears in the terminal:

[43133:775:0605/113822.785993:ERROR:component_loader.cc(167)] Failed to parse extension manifest.

Issue Analytics

State:
Created 4 years ago
Reactions:24
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

vonEdfacommented, Sep 26, 2019

@AndikaTanpaH I still have it. I think you’re correct with the normal flavor as that seems to be the one npm gives me. I’m not sure as I’m still too new to nw to know how to check…

0reactions

rogerwangcommented, Oct 1, 2020

This is fixed in git and will be available in the next nightly build.