bmealhouse/next-redux-saga

Issues

• outdated read.me & questions

  #76 opened 4 years ago by BernardA
  2

• store.sagaTask incompatible with typescript?

  #64 opened 4 years ago by tunesmith
  9

• Readme. Project Description

  #74 opened 4 years ago by deresegetachew
  1

• dependency upgrades (peers?) and release a new version

  #70 opened 4 years ago by bbortt
  0

• STOP MAINTAINING THIS REPOSITORY

  #79 opened 4 years ago by bbortt
  1

• Next 9.3+ Compatibility

  #75 opened 4 years ago by tkstang
  4

• takeLatest doesn't execute the generator function on server

  #73 opened 5 years ago by dxit
  5

• Image and css not working

  #72 opened 5 years ago by sivakumarjsl
  1

• After dispatching an action the saga returns prematurely

  #71 opened 5 years ago by myasul
  6

• Kea-saga

  #45 opened 5 years ago by etiennemtl
  11

• Redux State is not updated when store.dispatch() is called from getInitialProps in _app.js

  #66 opened 5 years ago by rehan-sattar
  5

• Running the root saga only once

  #62 opened 5 years ago by bjoluc
  5

• Sagas are not fired not even once.

  #65 opened 5 years ago by zurez
  2

• Sagas finishing too early

  #57 opened 5 years ago by Cretezy
  9

• Async dispatch in getInitialProps

  #60 opened 5 years ago by JoaoFGuiomar
  6

• Infinite loop when you use watcher

  #53 opened 5 years ago by agustin107
  15

• Root saga run multiple times server-side

  #59 opened 5 years ago by dhovart
  15

• Error: It looks like you are passing several store enhancers to createStore(). This is not supported. Instead, compose them together to a single function.

  #58 opened 5 years ago by ElijahKaftanov
  3

• TypeError: Cannot call a class as a function after upgraded to 4.0.1

  #50 opened 5 years ago by fangqiao
  6

• wait for async data on server

  #51 opened 5 years ago by makarov-foot
  6

• Data fetched using Saga not showing

  #56 opened 5 years ago by Arjun-Aggarwal
  2

• Cannot read property 'toPromise' of undefined

  #55 opened 5 years ago by Arjun-Aggarwal
  1

• page is rendered before sagas are done on client side

  #54 opened 5 years ago by pavel06081991
  5

• Accessing state after dispatching an action inside getInitialProps

  #20 opened 6 years ago by ussuritiger
  39

• considerations on stopping saga tasks on server side

  #48 opened 6 years ago by bbortt
  9

• Complete example of calling API on backend with multiple sagas?

  #18 opened 6 years ago by jd327
  11

• Using NextJS router.push from within saga stops working with next-redux-saga

  #26 opened 6 years ago by jbox5
  6

• Problems with Next.js redux-saga sample code when redux-saga version is changed to ^1.0.0

  #27 opened 6 years ago by robert-barcelona
  27

• Inconsistent behaviour with redux-saga 1.0.0 and next-redux-saga patched for this version

  #31 opened 6 years ago by robert-barcelona
  1

• How does server wait for async dispatches?

  #19 opened 6 years ago by jd327
  4

• Actions are lost after END is dispatched

  #6 opened 7 years ago by crizant
  17

• Typescript definitions

  #5 opened 6 years ago by virzak
  7

• state lost on the client side

  #15 opened 6 years ago by arfa
  3

• TypeError: Converting circular structure to JSON

  #10 opened 6 years ago by shenburak
  2

• Saga argument must be a Generator function

  #16 opened 6 years ago by leadhkr
  4

• Has this issue: https://github.com/zeit/next.js/issues/3108

  #7 opened 7 years ago by gl2748
  3

• Next.js v6 compatibility

  #8 opened 7 years ago by RobbinHabermehl
  4

• page renders before sagaTask is done

  #3 opened 7 years ago by JerryCauser
  6

• saga can't get action's result on server

  #1 opened 7 years ago by Mantak
  6

• How run saga background task in server?

  #2 opened 7 years ago by nghiepdev
  5