I needed this property, the doc may need an update?

/**
 * Then create your Firedux instance, passing it your database reference as `ref`.
 */
const firedux = new Firedux({
  ref,
  url: 'http://somethin....' <-- missing but needed?

  // Optional:
  omit: ['$localState'] // Properties to reserve for local use and not sync with Firebase.
})

import Firedux from 'firedux' gives me: Uncaught Error: Cannot find module "firedux"

which appears to be happening because your package.json says this: "main": "dist/index.js", which doesn't actually exist. So I tried pathing directly to it at firedux/dist/src, and I get returned an empty object: firedux: Object {}

Thought maybe it was console voodoo going on so I try the next step:

const firedux = new Firedux({ url: 'https://redux-firebase.firebaseio.com/' })

and I'm getting this error: Uncaught TypeError: _src2.default is not a function

Let me know what else I can do to help you fix this as I would love to start playing with this library.

When calling firedux.update( path/to/item, data) it updates the data correctly in Firebase by merging it with the current data.
However, the new Redux state for firedux.data.path.to.item is created in the same way as for the set() command. That leads to a state that has only the updated value not the ones it was merged with.

Example:
Redux state before:

item: {
    title: 'Before I was named this',
    content: 'Some text as the content',
    data: '2016-01-01'
}

Redux state after calling firedux.update('item', { title: 'Some new title', checked: true }):

item: {
    title: 'Some new title',
    checked: true
}

After looking at the source code of Firedux, I suppose the reason is that the reducer function calls makeFirebaseState(action, state, action.path, action.value) for both FIREBASE_SET and FIREBASE_UPDATE.
Instead for FIREBASE_UPDATE it should call makeFirebaseState(action, state, action.path, action.snapshot.val()) (the same as FIREBASE_WATCH).

Please correct me, if I am wrong here :)

@jonathandion mentioned in #7 (comment)

What's the best way to access the Firedux API from a component (ie. outside of the file where the store was created)? Even if a new Firebase ref is created in the component, Firedux still needs the store.dispatch method. And state.firedux is just the returned data, no access to the API from there.

Thanks for your help. Nice library!

Like https://github.com/elgerlambert/redux-localstorage.

There seems to be a problem with the currently used npm package [email protected] which requires an old peer of lodash (v3.0.0).
Using gulp with Browserify and a newer version of lodash creates a lot of "Cannot find module lodash/collection/......" errors for me. The latest version of updeep requires at least [email protected] so updating to the latest updeep version should fix that.

Installing the latest version 0.14.0 of updeep as a root dependency in my project fixed it for me.

https://www.firebase.com/docs/web/api/query/

Hello,

in the TodoMVC example, the actual Firebase url is fetched by matching the session key from window.location so that every time the page loads Firedux only gets access to the current session data in Firebase.

I have a React router param groupId accessible within the App as this.props.params.groupId and want to use that in the url e.g. url: FIREBASEURL + this.props.params.groupId. It just won't work.

The problem seems to be that Firedux is created first within the Redux store when calling firedux.dispatch = store.dispatch so way before the router params are even accessible and therefore no reference to the props.

The React App is Rendered as:

<Provider store={store}>
    <Router history={history}>
    <Route path="/" component={App}>
        <IndexRoute component={Home}/>
        <Route path="group/:groupId" component={Tool}/>
        <Route path="*" component={NotFound}/>
    </Route>
    </Router>
</Provider>

Any ideas how to solve this?

There are many libraries that provide functionality similar to this one.

Existing Libraries

• firedux - supports v3.0.4
• redux-react-firebase - Current defacto solution but owner is busy for a few months
• refire - easily configurable firebase bindings
• redux-firebase - best namespace
• react-firebase - Similar to react-redux, good docs

Though it is nice to have different libraries with different implementations, some of the library authors were thinking of combining the best of all of them into one defacto solution. Would you be interested in joining the group of us creating this firebase-redux integration? Your solution is beautiful, and we would love your input with creating a combined library.

Here are the issues posted for the other libraries:

redux-firebase
redux-react-firebase

Thoughts?

i'm trying out the snippet provided for logging in.

handleLogin (e) {
    e.preventDefault()
    const em = this.email.value
    const pw = this.pw.value

    console.log('em', em, 'pw', pw)
    firedux.login({em, pw})
}

and i got this error:
weird thing is that it's just email, password auth but the error log said it's related to FB auth

can someone provide a example repo using firedux for auth? would really appreciate it, thanks

I have a watch for a path. Like the docs said, it will only resolve once (the first time). Is their a good practice to handle all new entries from that watch path?

Ex: for each new entry that get added, fire an action creator.

Please excuse my ignorance :)

Something like https://github.com/yeldarby/offline-firebase, caching to localStorage. Might need configurability & some mechanism (e.g. LIFO) to manage size so we don't exceed browser data quota.

Hey,
there is a problem with your dependencies. Lodash is there in your node_modules but when you try to compile I have a lot of 'Cannot find module' errors.

Move verb Travis script into an external repo for re-use in other projects.

Localhost dev app is talking to the right Firebase backend and displaying new data in the database tree in the dashboard/console as it should--

The deployed app however is persisting data, but not the same place as the localhost. When I use $ firebase open database or whatever, it says it's pointing to the same address, but not displaying the same database tree as the localhost, which I would expect.

So the app is functional, but I have no idea where my data is, which is a little concerning :p

Anyone else run into this?

I'm getting a similar issue to the one reported in #3. I'm on "firedux": "^0.6.1", which I installed today.

The code example below errors out with a Uncaught TypeError: _firedux2.default is not a function error. _firedux2.default seems to be an empty object.

import Firedux from 'firedux'
const firedux = new Firedux({
  url: 'https://redux-firebase.firebaseio.com/',

  // Optional:
  omit: ['$localState'] // Properties to reserve for local use and not sync with Firebase.
})

Let me know if there's anything I can do to help. I'm excited to give this shot.

so i have array of keys for answers:

const arryKeys = ['answer1', 'answer2']

my data structure looks like this:

questions {
  name: 'test',
  answers: {
    answer1: true,
    answer2: true
  }
}

answers {
  answer1 {
    name: 'Yes'
  }
  answer2 {
    name: 'No'
  }
}

i tried to do this to get the actual answers value on answers

arryKeys.map((aK) => {
  firedux.get(`users/${aK}`)
})

i'm not sure what's the best way to do it, hope someone can help me, thanks

Hi, does this library support react-native? I am seeing the following error when I try to use it in my app:

TransformError: /Users/prabhaav/Development/betaApp/node_modules/firedux/dist/src/index.js: Couldn't find preset "es2015" relative to directory "/Users/prabhaav/Development/betaApp/node_modules/firedux"

I manually installed babel: npm install babel-cli babel-preset-es2015

Then I see the following error:

Anybody else facing this issue?

Exploring firebase integrations for redux atm and firedux seems to having an interesting approach. Do you have any example applications you can share?

Hard to picture how to use this at scale, any way to get a decent example explaining how to do so?

See #2 (comment).

In lieu of returning custom promises, consider a promise middleware:

• https://github.com/pburtchaell/redux-promise-middleware
• https://github.com/acdlite/redux-promise

The omit option should accept a function, not just an array, that would accept each property as argument at runtime and return true or false to determine whether or not the key should be omitted.