v5.0.0

Routes tab complete overhaul

• Routes tab now shows all the routes in the fog of war
• Routes tab now shows if clientAction and clientLoader are present on the module
• Routes tab now highlights the discovered routes and grays out undiscovered ones

Server logging

react-router-devtools is now smart enough to know where your routes are, allowing it to wrap your exports anywhere in your app whatever routing convention you use. This means if you're using a custom convention outside the routes folder you still get server logs and all the other goodies.

Also various bug fixes and improvements

What's Changed

• Make routes tab great again by @AlemTuzlak in #204

Full Changelog: v1.1.10...v5.0.0

v1.1.10

What's Changed

• Added additional support to wrapping the default export specifier by @AlemTuzlak in #201

Full Changelog: v1.1.9...v1.1.10

v1.1.9

What's Changed

• fix: babel security advisory GHSA-968p-4wvh-cqc8 by @bravo-kernel in #200

New Contributors

• @bravo-kernel made their first contribution in #200

Full Changelog: v1.1.8...v1.1.9

v1.1.8

What's Changed

• Transformation bug fix by @AlemTuzlak in #199

Full Changelog: v1.1.7...v1.1.8

v1.1.7

Bug fix

Fixed a bug where the wrong response object was used for parsing server-side information which lead to:

• server logs not showing up when they should've
• client side not showing the data recieved from the backend properly

What's Changed

• Update git organizations to forge-42 by @beeman in #197

New Contributors

• @beeman made their first contribution in #197

Full Changelog: v1.1.6...v1.1.7

v1.1.6

React component inspector disabled

Due to some issues caused by the underlying package the react-component inspector is disabled until bippy becomes a bit more stable

Full Changelog: v1.1.5...v1.1.6

v1.1.5

Cloudflare support

Better cloudflare support OOTB by optimizing problematic deps in dev mode for you

Better startup optimization

Before you could run into cases where the rdt would cause an error durring vite dev server warmup by getting errors like useContext is not undefined, this version resolved the issue

BigInt support

Now the rdt doesn't cause issues if you're returning BigInt from the server

What's Changed

• changed workflows by @thomasfr in #191
• Update bippy by @AlemTuzlak in #195
• feat: can handle bigint data by @kesoji in #186
• Fix tests and remove logs from output by @AlemTuzlak in #196

New Contributors

• @kesoji made their first contribution in #186

Full Changelog: v1.1.4...v1.1.5

v1.1.4

Full Changelog: v1.1.3...v1.1.4

v1.1.3

Full Changelog: v1.1.2...v1.1.3

v1.1.2

Full Changelog: v1.1.1...v1.1.2