Report filenames for syntax errors

[strongloop]

Report filenames for syntax errors

[frankcarey]

yeah, this is a real PITA at the moment. I added a try catch to output the filename, but I'm not getting any line numbers so it's still a trial and error process for me at the moment. Any better ideas to at least get tke line number?

function loadConfigFiles(files) {
  return files.map(function(f) {
    try {
      var config = require(f);
      Object.defineProperty(config, '_filename', {
        enumerable: false,
        value: f
      });
      return config;
    }
    catch(err) {
     console.log("Error loading config file %s: %s", f, err);
     throw err;
    }
  });
}

[raymondfeng]

Do you refer to JSON files?

[frankcarey]

Yes, I'm getting the error with the datasources file. It seems like it might be cached between server restarts.. is that possible?

[raymondfeng]

datasources.json is persistent. It will be reloaded upon server start.

[bajtos]

It would be also nice to include more details when a JSON file is malformed. Is there any widely-used replacement for JSON.parse? I found greatjson, but that project seems to be dead. jju seems to be more popular, but it implements JSON5.

[frankcarey]

I'm at a loss.. I can't seem to make sense of this syntax error :/

My local JSLint in vim has no issues or this online validator: http://jsonlint.com/

It all started when pasting in code from the loopback-connector-rest example, so I'm thinking maybe an odd character?

Error loading config file ../server/datasources.json: SyntaxError: ../server/datasources.json: Unexpected token

../node_modules/loopback-boot/lib/config-loader.js:100

[frankcarey]

Note that I just copied the text from the linter BACK into the file, and now I don't get the error.

[frankcarey]

@bajtos another side note about node-config is that it allows for comments in json files, which for config is really handy. That might be an easy feature to add as well and would help to debug by commenting out.

[dhmlau]

Since the last comment was from almost 4 years ago, Closing due to inactivity. Please create a new issue if you are still running into problems.