AutoHotkey Community

I intend to make use of Helgef's work, with some (as yet not clearly defined) changes.

Interesting notes and features: https://docs.npmjs.com/cli/v6/configuring-npm/package-json

@Chunjee
I'm a bit confused by what you are wanting to point out on that page. It is quite large and frankly, I don't think package.json has anything to do with namespaces/modules. That is for declaring dependencies and managing them which I see as a totally separate topic.

If package.json could specify downloading to ScriptDir/Lib it would work a lot more seamlessly but I guess that isn't an option and I was just marveling at some of the features. For example I never knew about "bundledDependencies" which may align closer to how ahk thinks of includes.

Again, I think that is a completely different topic than what this thread (your thread) is about. Package manager vs. Module/Namespaces

Not sure if I'm conflating or not but Module Export does need to be capable of communicating some metadata I think.


Github calls this metadata communication "manifest files" or I guess in this case it would be one file. The development world is adopting this model I feel.

2.1 has this. Thank you

https://www.autohotkey.com/docs/alpha/Modules.htm