require()'ing json from a relative path inside runSync

[bigblind]

I have a function that looks as follows:

getConfig: function(key){
    return atcompile.runSync(function(){
        return require("./../../config/settings.json")[key];
    });
}

but it keeps telling me that the module ./../../config/settings.json doesn't exist.

In the source of runSync, I see that you're passing a require wrapper into the context, but I don't know how to make it resolve relative paths correctly.

[brigand]

The require() problem is a temporary limitation (I still need to find a decent solution). You can work around it by using fs.readFileSync and JSON.parse.

Because it runs the function at compile time, there's no way for it to use runtime variables like the key argument.

What you can do, currently, is this:

var config = atcompile.runSync(function(){
  var read = require('fs').readFileSync;
  var settings = JSON.parse(read('config/settings.json', 'utf8'));

  // whitelist some keys, or you can just return the whole thing
  return {
    foo: settings.foo,
    bar: setting.bar
  };
});

// if you still want the getConfig api
exports.getConfig = function(key){
    return config[key];
}

And this ends up like this:

var config = {"foo": {"...":"..."}, "bar": 7};

---

If you prefer to not do this, you can create your own transform using static-module, which basically just lets you inline function calls (it's what atcompileify, brfs, etc. use).

[bigblind]

Cool, I'll take a look at static-module.