support "map" and "paths" config

[millermedeiros]

would need to translate the dependency names

nodefy.config({
  paths : {
    "utils" : "amd-utils"
  },
  map : {
    "*" : {
      "lib/foo" : "foo"
    },
    "dolor/amet" : {
       "dolor/sit" : "sit-amet"
    }
  }
});


// INPUT: dolor/amet.js ===
define(['lib/foo', './sit', 'utils/math/clamp'], function(foo, sit, clamp){
    return foo.bar(sit, clamp);
});

// OUTPUT: dolor/amet.js ===
var foo = require('foo');
var sit = require('sit-amet');
var clamp = require('amd-utils/math/clamp');
module.exports = foo.bar(sit, clamp);

Reference:

• http://requirejs.org/docs/api.html#config-paths
• http://requirejs.org/docs/api.html#config-map

[millermedeiros]

try to reuse amd-resolve if possible.

[jaridmargolin]

Any plans to implement this feature? or am I better off looking at a tool like uRequire?

[millermedeiros]

I have no plans for now (it is working for my own needs, and I don't have that much free time), but contributions are highly appreciated!!

[jaridmargolin]

No promises but I will look into it.

[jaridmargolin]

I believe paths would be very simple to implement.

I'm trying to wrap my head around map and how amd-resolve would/could be used to assist. If you have any thoughts/ideas I would be happy to do the grunt work required to implement.

If I am unable to fully form my thoughts on implementing map, would you still be open to a PR for a simple implementation to resolve paths?

[millermedeiros]

sure! we can do as incremental commits/PRs!

amd-resolve does the map/paths magic, you pass the ID + configs and it should return the absolute path. I did not try it out tho..

[jaridmargolin]

I guess that is the issue I am having difficulty wrapping my head around.

Currently as I understand it, we will be moving in the opposite direction. We will have the absolute paths and we will need to create the ID.

I'll start with paths, maybe my brain just needs some time to digest :)

[jaridmargolin]

CLI

Couple of questions before I implement. How/will this be integrated with the CLI? Only two options I can think of are:

1. nodefy.json configuration file.
2. or to just not offer support via CL..

Standalone Lib

Curious of the benefits or adding a config method rather than passing and options object to the parse, convert, & batchConvert methods..

var nodefy = require('nodefy');

// nodefy.parse(string)
// returns node.js style module
var cjsModule = nodefy.parse(jsString, {
  paths : { "utils" : "amd-utils" }
});

// nodefy.convert(inputPath [, outputPath], callback)
// if outputPath is omitted it won't write the result
nodefy.convert('foo.js', {
  paths : { "utils" : "amd-utils" }
}, function(err, result){
    console.log(result);
});

// nodefy.batchConvert(glob [, outputFolder], callback)
// if outputFolder is omitted it won't write the result
nodefy.batchConvert('src/**.js', {
  outputDir: ''cjs",
  paths : { "utils" : "amd-utils" }
}, function(err, results){
    // results is an array of {sourcePath, outputPath, result}
});