Move @tanstack/router-devtools to @tanstack/react-router-devtools

[birkskyum]

The current router-devtools package is specific to react.

This PR moves the react devtools to react-router-devtools, allowing for addition of e.g. solid-router-devtools, and for collection of shared functions in an agnostic core devtools package to the extend it makes sense in this context.

Since the @tanstack/react-router-devtools isn't published, this PR doesn't change the docs (.md files) or the examples/* folder which rely on specific published versions (rather than workspace packages)

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 95a6e02.

Command	Status	Duration	Result
nx affected --targets=test:eslint,test:unit,tes...	✅ Succeeded	4m 52s	View ↗
nx run-many --target=build --exclude=examples/*...	✅ Succeeded	1m 8s	View ↗

---

☁️ Nx Cloud last updated this comment at 2024-12-27 19:48:10 UTC

[schiller-manuel]

we would need to still have router-devtools package as an almost empty shell so people can continue to use it (and then deprecate it once we have react-router-devtools in place). we did the same for the router vite plugin

[pkg-pr-new]

Open in Stackblitz

More templates

• tanstack-router-react-example-basic
• tanstack-router-react-example-authenticated-routes
• tanstack-router-react-example-basic-default-search-params
• tanstack-router-react-example-basic-file-based
• tanstack-router-react-example-basic-file-based-codesplitting
• tanstack-router-react-example-basic-react-query-file-based
• tanstack-router-react-example-basic-ssr-file-based
• tanstack-router-react-example-basic-ssr-streaming-file-based
• tanstack-router-react-example-react-query
• tanstack-router-react-example-basic-virtual-file-based
• tanstack-router-react-example-basic-virtual-inside-file-based
• tanstack-router-react-example-deferred-data
• tanstack-router-react-example-kitchen-sink
• tanstack-router-react-example-kitchen-sink-file-based
• tanstack-router-react-example-kitchen-sink-react-query
• tanstack-router-react-example-kitchen-sink-react-query-file-based
• tanstack-router-react-example-large-file-based
• tanstack-router-react-example-location-masking
• tanstack-router-react-example-navigation-blocking
• tanstack-router-react-example-quickstart
• tanstack-router-react-example-quickstart-esbuild-file-based
• tanstack-router-react-example-quickstart-file-based
• tanstack-router-react-example-quickstart-rspack-file-based
• tanstack-router-react-example-quickstart-webpack-file-based
• router-monorepo-react-query
• router-mono-simple
• tanstack-router-react-example-scroll-restoration
• tanstack-search-validator-adapters
• tanstack-start-example-basic
• tanstack-start-example-basic-auth
• tanstack-start-example-basic-react-query
• tanstack-start-example-basic-rsc
• tanstack-start-example-clerk-basic
• tanstack-start-example-convex-trellaux
• tanstack-start-example-counter
• tanstack-start-example-large
• tanstack-start-example-supabase-basic
• tanstack-start-example-trellaux
• tanstack-router-react-example-with-framer-motion
• tanstack-router-react-example-with-trpc
• tanstack-router-react-example-with-trpc-react-query

@tanstack/arktype-adapter

npm i https://pkg.pr.new/@tanstack/arktype-adapter@3083

@tanstack/create-router

npm i https://pkg.pr.new/@tanstack/create-router@3083

@tanstack/create-start

npm i https://pkg.pr.new/@tanstack/create-start@3083

@tanstack/eslint-plugin-router

npm i https://pkg.pr.new/@tanstack/eslint-plugin-router@3083

@tanstack/history

npm i https://pkg.pr.new/@tanstack/history@3083

@tanstack/react-cross-context

npm i https://pkg.pr.new/@tanstack/react-cross-context@3083

@tanstack/react-router

npm i https://pkg.pr.new/@tanstack/react-router@3083

@tanstack/react-router-devtools

npm i https://pkg.pr.new/@tanstack/react-router-devtools@3083

@tanstack/react-router-with-query

npm i https://pkg.pr.new/@tanstack/react-router-with-query@3083

@tanstack/router-cli

npm i https://pkg.pr.new/@tanstack/router-cli@3083

@tanstack/router-generator

npm i https://pkg.pr.new/@tanstack/router-generator@3083

@tanstack/router-plugin

npm i https://pkg.pr.new/@tanstack/router-plugin@3083

@tanstack/router-vite-plugin

npm i https://pkg.pr.new/@tanstack/router-vite-plugin@3083

@tanstack/start

npm i https://pkg.pr.new/@tanstack/start@3083

@tanstack/start-vite-plugin

npm i https://pkg.pr.new/@tanstack/start-vite-plugin@3083

@tanstack/valibot-adapter

npm i https://pkg.pr.new/@tanstack/valibot-adapter@3083

@tanstack/virtual-file-routes

npm i https://pkg.pr.new/@tanstack/virtual-file-routes@3083

@tanstack/zod-adapter

npm i https://pkg.pr.new/@tanstack/zod-adapter@3083

commit: 95a6e02

[SeanCassiere]

This may not be the best approach here. At the moment, this would be a 'no-go' since it'd break people currently using the @tanstack/router-devtools package with no fallback.

---

As a whole, however, it'd be worth asking @ardeora on his thoughts here, since there's potential for following Query's approach for the devtools as a whole.

If done so, we could have the following package structure, which I believe would be the better approach here.

• router-devtools-core
• react-router-devtools
• router-devtools (proxies everything from react-router-devtools with a console warning asking them to switch packages and commitment that'd we'd drop this package in v2)

[schiller-manuel]

while we are at restructuring, we should also keep in mind start's devtools (hopefully coming soon @ardeora :) )

[birkskyum]

I have added a router-devtools package which is a re-export of react-router-devtools, and there's a console warning that suggests to move to the new package.

To make sure nothing is broken by this change, the router-devtools is kept in the /e2e and /examples