In browserify context, if:

require('js-data')window.DSHttpAdapter = require('js-data-http')window.DSSqlAdapter = require('js-data-sql')require('js-data-angular')

There is a bug in adapter registration:

null "new data store created" Defaults {…} null nullnull "registerAdapter" "http" DSHttpAdapter {defaults: Defaults} Object {}null "default adapter is http" null null nullnull "registerAdapter" "sql" DSHttpAdapter {defaults: Defaults} Object {}null "default adapter is http" null null nullnull "registerAdapter" "http" DSHttpAdapter {defaults: Defaults} Object {default: true}null "default adapter is http" null null null

In adapter registration loop (https://github.com/js-data/js-data-angular/blob/master/src/index.js#L205-L214), if the first adapter is well registrated, it continue to loop over next adapter when with a wrong object.
Adding a break fix the issue. (in846c4c0)

(I added a commit to current PR, if separate PR is preferable, just tell me)

Wow, I didn't even realize js-sql-adapter would be useful in the browser. And thanks for the fix!

@jmdobry Yeah. I thought I was crazy to dig into it but it works!
Seems to fail in CircleCI tests. Bower issue... Perhaps resolution ?https://circleci.com/gh/js-data/js-data-angular/44
CircleCI does not test PR ?