maloguertin/msw-trpc

Issues

• Support for V11

  #37 opened a year ago by PupoSDC
  8

• Support different mutation input types

  #43 opened 5 months ago by maloguertin
  0

• Is it possible to reproduce the case where the server side throws a TRPCError?

  #13 opened 8 months ago by haga-triple1
  6

• Issues throwing errors in 2.0.0-beta.0

  #33 opened 8 months ago by danilofuchs
  1

• Cannot trigger useQuery `error` or `isError` response in test

  #35 opened 8 months ago by jchiversTRG
  2

• Bug: `output` is used inside `getMutationInput`

  #38 opened 8 months ago by Tomomi-K1
  0

• bug: TRPCClientError: Invalid URL

  #23 opened a year ago by michealroberts
  10

• Merged routes not working with latest trpc and msw-trpc

  #29 opened a year ago by madi-tracksuit
  2

• Issue running with react hooks with tRPC 10.33.1+

  #28 opened a year ago by tarehart
  3

• `req.getInput` incorrectly typed for `query`

  #25 opened a year ago by DavidAmmeraal
  2

• trpc query firing before service worker is started

  #20 opened a year ago by RL-adaptive
  2

• Compatibility with msw 2.0

  #27 opened a year ago by danilofuchs
  0

• Support for createTRPCReact (react query)

  #9 opened 2 years ago by nterraza
  2

• Request: Example integration with Next and RTL

  #24 opened a year ago by PupoSDC
  0

• When output parser is used in the procedure, `ctx.data` argument type is unknown (invalid type)

  #22 opened a year ago by swallowtail62
  1

• `req.getInput()` should indicate that its return type is a promise for mutations

  #17 opened 2 years ago by jack-michaud
  2

• Support tRPC subscriptions (WebSockets)

  #19 opened 2 years ago by ben-xD
  1

• Cannot run msw-trpc with vitest

  #15 opened 2 years ago by Q16solver
  4

• Serialization of request input with e.g., superjson

  #8 opened 2 years ago by michealroberts
  5

• ctx is untyped..

  #2 opened 2 years ago by kristiandupont
  23

• @typescript-eslint/no-unsafe-argument

  #6 opened 2 years ago by CUexter
  1

• Integrate with ladle

  #12 opened 2 years ago by twiddler
  1

• Call to GET http://127.0.0.1:49475/ not handled

  #14 opened 2 years ago by libasoles
  1

• Question: is this compatible with msw v1.0.1 ?

  #4 opened 2 years ago by CUexter
  3