supporting eyeglass modules that already have their own main. about eyeglass HOT 2 CLOSED

I think I might prefer an eyeglass / eyeglass-exports property in package.json which we will resolve and read in. Using our resolve function does properly resolve my_npm_module/package.json. This can override a main property for npm modules that intend main to be something else but still want to integrate with eyeglass.

This pattern has been used in other libraries that want to know more about npm modules without necessarily forcing main adoption or alterations.

For true, the change would then be to add an eyeglass / eyeglass-exports property to package.json, along with the corresponding eyeglass-exports.js (which can also include settings & directory info from a common location, because DRY). This also makes sense because package.json is where they will be tagging the item as eyeglass-module anyway.

from eyeglass.

Fixed by 7f978df

from eyeglass.