Relative ids are not being resolved against module URL about requirejs

[jrburke]

This is fixed in this commit. I also opened a ticket on the "main relative to package root" issue.

[kriszyp]

This looks good, but I don't think it is quite right. Now I am seeing an issue where the module factory gets executed twice. In my test in https://github.com/kriszyp/has.js/blob/master/tests/requirejs-plugin.html the has.js is loaded once through a module id of "has" and then is later referenced by "./has" (from _plugin.js) which seems to correctly resolve to right URL since it doesn't trigger an additional script load, but it does seem to trigger an additional execution of the has.js factory function.

[jrburke]

I am actually seeing two requests: one for a module called "has" and one for "has/has". I think the disconnect is because "has" loads "./_plugin", which is inside the package, and it requires "./has", which since a relative module ID gets resolved as "has/has", and that is not tied back to being the "has" top-level package module name.

I was trying to avoid using urls for tracking cached module values, but that would be one way to solve it. Will think about it a bit more.

[jrburke]

I put in a fix for paths that resolve to the main module in a package config in this commit