bundling issues with solidjs #289

Activity

1. tsteckenborn commented on Dec 16, 2025

   

   tsteckenborn

   on Dec 16, 2025

   Last edited by tsteckenborn

   More actions

   Is this related to the issues still mentioned in #91?

   The one linked above for me is limited to the Tanstack Forms devtools, so query and router active works fine.
2. baldyeagle commented on Feb 23, 2026

   

   baldyeagle

   on Feb 23, 2026

   Last edited by baldyeagle

   More actions

   I hit some client-side solidjs errors when I added the @tanstack/ai devtools with @tanstack/react-start as my framework. The devtools were working fine with just the router and query plugins.

   This seems to be a valid workaround, tested in my vite config(irrelevant plugins removed from this example):

   // vite.config.ts
   import path from "node:path";
   import { devtools } from "@tanstack/devtools-vite";
   import { tanstackStart } from "@tanstack/react-start/plugin/vite";
   import viteReact from "@vitejs/plugin-react";
   import { defineConfig } from "vite";
   
   const config = defineConfig({
   	resolve: {
   		alias: {
   			"@": path.resolve(__dirname, "./src"),
   			"solid-js/web": path.resolve(
   				__dirname,
   				"../../node_modules/solid-js/web/dist/web.js",
   			),
   		},
   		conditions: ["import", "module", "browser", "default"],
   	},
   	plugins: [
   		devtools(),
   		tanstackStart(),
   		viteReact(),
   	],
   });
   
   export default config;

   Note this is in a monorepo, so the node_modules path may be different.

   I'm not familiar enough with vite's plugins to know whether this could be solved within @tanstack/devtools-vite to properly handle client vs. server bundles, but I imagine that'd be more eloquent than resolving the alias like this.

   ❤️React with ❤️1Reacted by Tom Radford