Glad you find it useful! The macro checks for an existing `module.exports` 
object, and if one exists, it appends its exports to the existing object 
without overriding previous exports. There could be collisions if two different 
files try to export an object with the same name, but for now I think the work 
around of named exports should be sufficient. If I'm misunderstanding your 
concerns, let me know! If you utilize the macro and run into any issues or need 
additional functionality, feel free to raise an issue or file a pull request :)

Reply via email to