Migrated from next to tanstack im unable to deploy to cloudflare workers
✘ [ERROR] Build failed with 3 errors:
✘ [ERROR] Could not resolve "unenv/node/console"
node_modules/@cloudflare/unenv-preset/dist/runtime/node/console.mjs:9:7: 9 │ } from "unenv/node/console"; ╵~~~~.
✘ [ERROR] Could not resolve "unenv/node/internal/process/hrtime"
node_modules/@cloudflare/unenv-preset/dist/runtime/node/process.mjs:1:38: 1 │ ... hrtime as UnenvHrTime } from "unenv/node/
✘ [ERROR] Could not resolve "unenv/node/internal/process/process"
node_modules/@cloudflare/unenv-preset/dist/runtime/node/process.mjs:2:40: 2 │ ...ocess as UnenvProcess } from "unenv/node/internal/process/process"; ╵
Above is the error I’m getting when I run npm run deploy The build finish fine without errors but the error shows up when it tries to deploy to workers my wrangler.json { "$schema": "node_modules/wrangler/config-schema.json", "name": "autotok", "compatibility_date": "2025-09-02", "compatibility_flags": ["nodejs_compat"], "main": "./dist/server/server.js" } Yes I have deleted node modules package lock try again still the same issue Here my vite.config.ts // vite.config.ts import { defineConfig } from 'vite' import { tanstackStart } from '@tanstack/react-start/plugin/vite' import viteReact from '@vitejs/plugin-react' import tsconfigPaths from 'vite-tsconfig-paths' import tailwindcss from '@tailwindcss/vite' export default defineConfig({ server: { port: 3000, }, plugins: [ tailwindcss(), // Enables Vite to resolve imports using path aliases. tsconfigPaths(), tanstackStart({ srcDirectory: 'src', // This is the default router: { // Specifies the directory TanStack Router uses for your routes. routesDirectory: 'app', // Defaults to "routes", relative to srcDirectory }, }), viteReact(), ], }) Help please
node_modules/@cloudflare/unenv-preset/dist/runtime/node/console.mjs:9:7: 9 │ } from "unenv/node/console"; ╵
✘ [ERROR] Could not resolve "unenv/node/internal/process/hrtime"
node_modules/@cloudflare/unenv-preset/dist/runtime/node/process.mjs:1:38: 1 │ ... hrtime as UnenvHrTime } from "unenv/node/
✘ [ERROR] Could not resolve "unenv/node/internal/process/process"
node_modules/@cloudflare/unenv-preset/dist/runtime/node/process.mjs:2:40: 2 │ ...ocess as UnenvProcess } from "unenv/node/internal/process/process"; ╵
Above is the error I’m getting when I run npm run deploy The build finish fine without errors but the error shows up when it tries to deploy to workers my wrangler.json { "$schema": "node_modules/wrangler/config-schema.json", "name": "autotok", "compatibility_date": "2025-09-02", "compatibility_flags": ["nodejs_compat"], "main": "./dist/server/server.js" } Yes I have deleted node modules package lock try again still the same issue Here my vite.config.ts // vite.config.ts import { defineConfig } from 'vite' import { tanstackStart } from '@tanstack/react-start/plugin/vite' import viteReact from '@vitejs/plugin-react' import tsconfigPaths from 'vite-tsconfig-paths' import tailwindcss from '@tailwindcss/vite' export default defineConfig({ server: { port: 3000, }, plugins: [ tailwindcss(), // Enables Vite to resolve imports using path aliases. tsconfigPaths(), tanstackStart({ srcDirectory: 'src', // This is the default router: { // Specifies the directory TanStack Router uses for your routes. routesDirectory: 'app', // Defaults to "routes", relative to srcDirectory }, }), viteReact(), ], }) Help please
7 Replies
jolly-crimsonOP•2mo ago
someone please guys
ambitious-aqua•2mo ago
have you tried to get some help by an AI ?
jolly-crimsonOP•2mo ago
yes i have tried bunch of things before coming here
noble-gold•2mo ago
i dont see the cloudflare vite plugin being used
noble-gold•2mo ago
Hosting | TanStack Start React Docs
Hosting is the process of deploying your application to the internet so that users can access it. This is a critical part of any web development project, ensuring your application is available to the...
jolly-crimsonOP•4w ago
it was actully there at the time ill try again but i moved on at the time i was trying to test something
noble-gold•4w ago
so? is it working now?