{"action":"created","issue":{"url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/27","labels_url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/27/comments","events_url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/27/events","html_url":"https://github.com/ParsePlatform/Parse-SDK-JS/issues/27","id":108763000,"number":27,"title":"JSPM registry entry for Parse","user":{"login":"typhonrt","id":311473,"avatar_url":"https://avatars.githubusercontent.com/u/311473?v=3","gravatar_id":"","url":"https://api.github.com/users/typhonrt","html_url":"https://github.com/typhonrt","followers_url":"https://api.github.com/users/typhonrt/followers","following_url":"https://api.github.com/users/typhonrt/following{/other_user}","gists_url":"https://api.github.com/users/typhonrt/gists{/gist_id}","starred_url":"https://api.github.com/users/typhonrt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/typhonrt/subscriptions","organizations_url":"https://api.github.com/users/typhonrt/orgs","repos_url":"https://api.github.com/users/typhonrt/repos","events_url":"https://api.github.com/users/typhonrt/events{/privacy}","received_events_url":"https://api.github.com/users/typhonrt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/labels/discussion","name":"discussion","color":"eeeeee"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-09-28T22:57:32Z","updated_at":"2015-10-06T18:13:54Z","closed_at":null,"body":"Hi Andrew et al, I have a similar use case as Issue #26 \r\n\r\nThis is to support the Parse+Backbone distribution I'm open sourcing to continue support for Backbone. I'm distributing it in two ways:\r\n\r\nFirst, I will be creating a standalone bundle by modifying the current build process w/ Browserify combining Parse browser SDK w/ my Backbone fork. This will handle the folks that just need to import one ES5 bundle with Parse+Backbone. \r\n\r\nHowever, it would be really handy to have a separate Git repo that just contains the latest built browser bundle. The reasoning for this is supporting SystemJS / JSPM as it would be great to be able to pull in just the Parse browser SDK bundle from a git repo as a dependency. When installing the NPM package via JSPM it pulls in everything and the kitchen sink of course including node and react-native runtimes and really muddies up the SystemJS config.js file with all the unneeded dependencies to run the Parse browser SDK. In regard to Issue #26 even if you added the lib / dist directories and content JSPM will still pull it all in which is undesirable. Therefore having a separate Git repo with the latest built browser SDK is really handy. This will allow folks to install the official Parse browser bundle repo and my Backbone fork as raw source into SystemJS via JSPM via Git. \r\n\r\nEither you guys do it or I do it and I'd prefer Parse does it so that things stay up to date w/ timely updates. \r\n\r\nFYI, I have converted Backbone 1.2.3 to ES6, modularized it and have made it extendable through constructor injection. This makes it easy to provide just the modifications for Parse support in addition to any further modifications to Backbone as desired in a clean / ES6 manner. This is why it's desirable to pull in the ES6 Backbone source and link it against the Parse browser bundle.\r\n\r\nThanks for considering this request... "},"comment":{"url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/comments/145951207","html_url":"https://github.com/ParsePlatform/Parse-SDK-JS/issues/27#issuecomment-145951207","issue_url":"https://api.github.com/repos/ParsePlatform/Parse-SDK-JS/issues/27","id":145951207,"user":{"login":"andrewimm","id":494043,"avatar_url":"https://avatars.githubusercontent.com/u/494043?v=3","gravatar_id":"","url":"https://api.github.com/users/andrewimm","html_url":"https://github.com/andrewimm","followers_url":"https://api.github.com/users/andrewimm/followers","following_url":"https://api.github.com/users/andrewimm/following{/other_user}","gists_url":"https://api.github.com/users/andrewimm/gists{/gist_id}","starred_url":"https://api.github.com/users/andrewimm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrewimm/subscriptions","organizations_url":"https://api.github.com/users/andrewimm/orgs","repos_url":"https://api.github.com/users/andrewimm/repos","events_url":"https://api.github.com/users/andrewimm/events{/privacy}","received_events_url":"https://api.github.com/users/andrewimm/received_events","type":"User","site_admin":false},"created_at":"2015-10-06T18:13:54Z","updated_at":"2015-10-06T18:13:54Z","body":"Agreed, I think that's the only step necessary. I'll try to get that PR into their registry when we release 1.6.5 in the next day or so (no point in doing it for a version that will immediately be outdated)"}}