CharlesStover/use-react-router

Issues

• Allow to use within MemoryRouter

  #20 opened 5 years ago by RusinovAnton
  2

• Subscribing to location changes might be a no-op.

  #11 opened 5 years ago by mayconfsousa
  4

• Ask people to use 5.1 instead?

  #24 opened 5 years ago by mjackson
  2

• Perhaps add to the docs official implementation?

  #23 opened 5 years ago by expelledboy
  1

• does not read updated parameteres

  #18 opened 5 years ago by klaky
  1

• useReactRouter may only be called within a <Router /> context

  #21 opened 5 years ago by SaketSaxena
  5

• impossible to get params using typescript

  #22 opened 5 years ago by EvilSourcerer
  2

• Thank you!

  #19 opened 5 years ago by chiefGui
  1

• Typing errors with updated @types/react-router@5.0.0

  #15 opened 5 years ago by danielsogl
  2

• Incorrect error is thrown when react-router Provider is missing.

  #16 opened 5 years ago by mikecfisher
  11

• Pin peerDependency of react-router

  #17 opened 5 years ago by StringEpsilon
  1

• Any example in the docs?

  #10 opened 5 years ago by dy
  4

• Failed to compile

  #9 opened 5 years ago by martinduo
  2

• Types section is missing in package.json

  #13 opened 5 years ago by kirill-konshin
  0

• why do we need a force update?

  #12 opened 5 years ago by sibelius
  1

• Provide a more informative error message for react-router@4.3 or earlier.

  #5 opened 6 years ago by theduke
  4

• Cannot find SourceMap 'use-force-update.js.map'

  #6 opened 6 years ago by steveast
  1

• [QoL] Warn on missing react-router context

  #4 opened 6 years ago by jvhoven
  6

• Add Travis key

  #2 opened 6 years ago by quisido
  0