[BUG] MODULE_NOT_FOUND: Cannot find module '.bin/vite' when running refine dev in npm/bun workspaces

[EldrikFind]

Describe the bug

When running refine dev inside a monorepo workspace (using npm workspaces, yarn workspaces, or Bun), the CLI crashes with a MODULE_NOT_FOUND error complaining that it Cannot find module '.bin/vite'.

Error output:

$ npm run dev
npm warn config ignoring workspace config at C:\Users\pc\Desktop\project\razrab\stepmagazine\apps\admin/.npmrc

> shiny-eyes-write@0.1.0 dev
> refine dev

╭─────────────────────────────────────────────────────────────────────╮│                                                                     ││   Generate Refine Core projects with our AI tool! Now with ShadCN   ││   and Supabase support. https://refine.dev                          ││                                                                     │╰─────────────────────────────────────────────────────────────────────╯
node:internal/modules/cjs/loader:1401
  const err = new Error(message);
              ^

Error: Cannot find module '.bin/vite'
Require stack:
- C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\@refinedev+cli@2.16.51+d5da596d6bbc3b07\node_modules\@refinedev\cli\dist\cli.cjs
    at Function._resolveFilename (node:internal/modules/cjs/loader:1401:15)
    at Function.resolve (node:internal/modules/helpers:145:19)
    at resolveBin (C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\@refinedev+cli@2.16.51+d5da596d6bbc3b07\node_modules\@refinedev\cli\dist\cli.cjs:1140:18)
    at Object.getBin (C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\@refinedev+cli@2.16.51+d5da596d6bbc3b07\node_modules\@refinedev\cli\dist\cli.cjs:1153:19)
    at Command.action5 (C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\@refinedev+cli@2.16.51+d5da596d6bbc3b07\node_modules\@refinedev\cli\dist\cli.cjs:1563:47)
    at Command.listener [as _actionHandler] (C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\commander@9.4.1\node_modules\commander\lib\command.js:482:17)
    at C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\commander@9.4.1\node_modules\commander\lib\command.js:1264:65     
    at C:\Users\pc\Desktop\project\razrab\stepmagazine\node_modules\.bun\commander@9.4.1\node_modules\commander\lib\command.js:1155:33     
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\Users\\pc\\Desktop\\project\\razrab\\stepmagazine\\node_modules\\.bun\\@refinedev+cli@2.16.51+d5da596d6bbc3b07\\node_modules\\@refinedev\\cli\\dist\\cli.cjs'
  ]
}

Node.js v22.17.0
npm error Lifecycle script `dev` failed with error:
npm error code 1
npm error path C:\Users\pc\Desktop\project\razrab\stepmagazine\apps\admin
npm error workspace shiny-eyes-write@0.1.0
npm error location C:\Users\pc\Desktop\project\razrab\stepmagazine\apps\admin
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c refine dev  

Steps To Reproduce

1. Create a root package.json configured as a workspace (e.g., "workspaces": ["apps/*"]).
2. Create a sub-project using Refine inside apps/admin.
3. Ensure vite and @refinedev/cli are listed in the dependencies/devDependencies of apps/admin/package.json.
4. Run npm install (or bun install) from the root directory to trigger workspace hoisting.
5. cd into apps/admin and try to run npm run dev.
6. Observe the crash.

Expected behavior

The refine dev command should successfully start the Vite development server even if we are using a monorepo.

Packages

@refinedev/cli: ^2.16.48
@refinedev/core: ^5.0.8
vite: ^7.3.1
Node: v22.17.0
Package Manager: npm / bun

Additional Context

No response

[Aaron3312]

Hey @EldrikFind! I ran into the same issue and submitted a fix.

The root cause is that resolveBin() was using require.resolve('.bin/<name>') which resolves relative to the CLI module's own location inside node_modules — not relative to your project. In a workspace setup the binary lives in a parent node_modules/.bin/, so it was never found.

The fix makes resolveBin() walk up from process.cwd() searching each node_modules/.bin/ until it finds the binary, which correctly handles hoisting in npm/bun/yarn workspaces.

PR: #7315

[YinHeaven]

import { exec } from 'child_process';
import path from 'path';
import { fileURLToPath } from 'url';

const __dirname = path.dirname(fileURLToPath(import.meta.url));
const rootDir = path.resolve(__dirname, '../../..');
const viteBin = path.join(rootDir, 'node_modules/.bin/vite');

exec(${viteBin}, { cwd: __dirname }, (error, stdout, stderr) => {
if (error) {
console.error(Error: ${error});
return;
}
console.log(stdout);
console.error(stderr);
});