{"action":"created","issue":{"url":"https://api.github.com/repos/jspm/jspm-cli/issues/907","labels_url":"https://api.github.com/repos/jspm/jspm-cli/issues/907/labels{/name}","comments_url":"https://api.github.com/repos/jspm/jspm-cli/issues/907/comments","events_url":"https://api.github.com/repos/jspm/jspm-cli/issues/907/events","html_url":"https://github.com/jspm/jspm-cli/issues/907","id":93032749,"number":907,"title":"Ways to manually configure JSPM around complex resolution issues?","user":{"login":"andremalkine","id":3652331,"avatar_url":"https://avatars.githubusercontent.com/u/3652331?v=3","gravatar_id":"","url":"https://api.github.com/users/andremalkine","html_url":"https://github.com/andremalkine","followers_url":"https://api.github.com/users/andremalkine/followers","following_url":"https://api.github.com/users/andremalkine/following{/other_user}","gists_url":"https://api.github.com/users/andremalkine/gists{/gist_id}","starred_url":"https://api.github.com/users/andremalkine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andremalkine/subscriptions","organizations_url":"https://api.github.com/users/andremalkine/orgs","repos_url":"https://api.github.com/users/andremalkine/repos","events_url":"https://api.github.com/users/andremalkine/events{/privacy}","received_events_url":"https://api.github.com/users/andremalkine/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-04T17:31:30Z","updated_at":"2015-07-08T15:05:25Z","closed_at":"2015-07-08T15:05:24Z","body":"I'm trying to use the newer [Famous/engine](https://github.com/famous/engine) in a jspm project. This may be related to known issues with the package and it's reliance on browserify, but I'm wondering if there's a way to configure around it.\r\n\r\nThe entry point for the package itself is `/index.js`, and it imports sub-modules via require statements like `require('./example');` where \"example\" is a sub-folder containing another `index.js` file. This pattern is used throughout the package. At the same time, many other internal require's will target `./example` in hopes of importing `./example.js`.\r\n\r\nHaving installed via jspm, I'm trying to mess with it's config so I can require it without all of the package's internal require's 404'ing because it's looking for `./example.js` instead of `./example/index.js`, but also not breaking when it's the other way around - or breaking resolution of the entry point.\r\n\r\nMaybe I'm trying to hack something that shouldn't be hacked or really just need to wait for Famous/engine to grow out of it's browserify dependency...but in the meantime, any thoughts?"},"comment":{"url":"https://api.github.com/repos/jspm/jspm-cli/issues/comments/119616456","html_url":"https://github.com/jspm/jspm-cli/issues/907#issuecomment-119616456","issue_url":"https://api.github.com/repos/jspm/jspm-cli/issues/907","id":119616456,"user":{"login":"guybedford","id":598730,"avatar_url":"https://avatars.githubusercontent.com/u/598730?v=3","gravatar_id":"","url":"https://api.github.com/users/guybedford","html_url":"https://github.com/guybedford","followers_url":"https://api.github.com/users/guybedford/followers","following_url":"https://api.github.com/users/guybedford/following{/other_user}","gists_url":"https://api.github.com/users/guybedford/gists{/gist_id}","starred_url":"https://api.github.com/users/guybedford/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guybedford/subscriptions","organizations_url":"https://api.github.com/users/guybedford/orgs","repos_url":"https://api.github.com/users/guybedford/repos","events_url":"https://api.github.com/users/guybedford/events{/privacy}","received_events_url":"https://api.github.com/users/guybedford/received_events","type":"User","site_admin":false},"created_at":"2015-07-08T15:05:24Z","updated_at":"2015-07-08T15:05:24Z","body":"@andremalkine this is an npm package, so you should install it from npm. Then jspm will apply all the Node resolution conventions and make them work on install. (`jspm install npm:famous` I assume?).\r\n\r\nIf you really must install from GitHub, you can enforce the npm conversions process via overriding the registry property which will apply the npm registry conversion operations - `jspm install github:Famous/engine -o \"{registry:'npm'}\"`. Just let me know if you need more tips here at all."}}