{"action":"created","issue":{"url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/1","labels_url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/1/comments","events_url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/1/events","html_url":"https://github.com/HaxeFoundation/hxnodelibs/issues/1","id":116013415,"number":1,"title":"package naming and file placing","user":{"login":"nadako","id":49749,"avatar_url":"https://avatars.githubusercontent.com/u/49749?v=3","gravatar_id":"","url":"https://api.github.com/users/nadako","html_url":"https://github.com/nadako","followers_url":"https://api.github.com/users/nadako/followers","following_url":"https://api.github.com/users/nadako/following{/other_user}","gists_url":"https://api.github.com/users/nadako/gists{/gist_id}","starred_url":"https://api.github.com/users/nadako/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nadako/subscriptions","organizations_url":"https://api.github.com/users/nadako/orgs","repos_url":"https://api.github.com/users/nadako/repos","events_url":"https://api.github.com/users/nadako/events{/privacy}","received_events_url":"https://api.github.com/users/nadako/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-11-10T02:41:22Z","updated_at":"2015-11-10T08:52:52Z","closed_at":null,"body":"Now when hxnodejs is finally released, we can discuss a bit about this extern collection.\r\n\r\nI don't like how it's currently done here using `js.node` as a prefix package since it may introduce conflicts with core node modules added at some time, also I don't like the fact that one can't easily say which is node API and which is a npm module.\r\n\r\n@clemos uses `js.npm` prefix which I think is better, but I don't quite like that different externs (of different quaility and by different authors) are placed in one root - it gets messy when there are lots of them, IMO.\r\n\r\nI wonder if we can/should use separate source paths for different npm externs and somehow still be able to just do `-lib hxnodelibs` and then simply `import js.npm.Whatever`. Maybe with macro that adds class paths and is executed in `extraParams.hxml`?\r\n\r\nThat way extern authors can also provide README's, tests, examples, etc.\r\n\r\nThoughts? @clemos @ncannasse @andyli @dionjwa @fponticelli @eduardo-costa @tong @back2dos (please cc anyone i forgot)"},"comment":{"url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/comments/155360790","html_url":"https://github.com/HaxeFoundation/hxnodelibs/issues/1#issuecomment-155360790","issue_url":"https://api.github.com/repos/HaxeFoundation/hxnodelibs/issues/1","id":155360790,"user":{"login":"clemos","id":32961,"avatar_url":"https://avatars.githubusercontent.com/u/32961?v=3","gravatar_id":"","url":"https://api.github.com/users/clemos","html_url":"https://github.com/clemos","followers_url":"https://api.github.com/users/clemos/followers","following_url":"https://api.github.com/users/clemos/following{/other_user}","gists_url":"https://api.github.com/users/clemos/gists{/gist_id}","starred_url":"https://api.github.com/users/clemos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/clemos/subscriptions","organizations_url":"https://api.github.com/users/clemos/orgs","repos_url":"https://api.github.com/users/clemos/repos","events_url":"https://api.github.com/users/clemos/events{/privacy}","received_events_url":"https://api.github.com/users/clemos/received_events","type":"User","site_admin":false},"created_at":"2015-11-10T08:52:52Z","updated_at":"2015-11-10T08:52:52Z","body":"Obviously I'd vote for `js.npm.*`.\r\n\r\nAbout extern \"mess\", the variable quality is pretty much that of the npm public repo itself.\r\nI've been trying to somehow \"curate\" the npm package in haxe-js-kit, though, which IMHO is easier / safer to do in one place.\r\nThen anyone is free to add their own in their own repos / haxelib on top of that, with hxnodelibs as a dependency.\r\n\r\nThis being said, I believe it might be cleaner to always have `js.npm.express.Express` rather than `js.npm.Express`. This will avoid the `js.npm` namespace to be too dirty, like it is in haxe-js-kit right now..."}}