{"action":"closed","issue":{"url":"https://api.github.com/repos/requirejs/requirejs-npm/issues/7","labels_url":"https://api.github.com/repos/requirejs/requirejs-npm/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/requirejs/requirejs-npm/issues/7/comments","events_url":"https://api.github.com/repos/requirejs/requirejs-npm/issues/7/events","html_url":"https://github.com/requirejs/requirejs-npm/issues/7","id":97943037,"number":7,"title":"Move source files one level up","user":{"login":"shariffy","id":470106,"avatar_url":"https://avatars.githubusercontent.com/u/470106?v=3","gravatar_id":"","url":"https://api.github.com/users/shariffy","html_url":"https://github.com/shariffy","followers_url":"https://api.github.com/users/shariffy/followers","following_url":"https://api.github.com/users/shariffy/following{/other_user}","gists_url":"https://api.github.com/users/shariffy/gists{/gist_id}","starred_url":"https://api.github.com/users/shariffy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shariffy/subscriptions","organizations_url":"https://api.github.com/users/shariffy/orgs","repos_url":"https://api.github.com/users/shariffy/repos","events_url":"https://api.github.com/users/shariffy/events{/privacy}","received_events_url":"https://api.github.com/users/shariffy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-29T14:02:03Z","updated_at":"2015-08-20T18:40:51Z","closed_at":"2015-08-20T18:40:51Z","body":"`npm` has a great feature to point a dependency's location directly to a git repo and branch, which is really handy when forking and contributing to an npm package (i.e. to use the fixed up fork temporarily). But that `npm` feature cannot look into subdirectories [AFAIK](https://github.com/npm/npm/issues/2974).\r\n\r\nMy point is less about making life easier for forkers (one can easily fix this within the fork) but if `package.json` is expected to be at the root as a standard, following the convention can't be a bad thing.\r\n\r\nMost likely there are dependencies in the build workflow to land this change but if one can point to/list those, I'll be happy to help to make this happen."}}