Seeking Advice: Running npm run dev on Windows Environment #3341

kcherki · 2024-12-25T15:19:46Z

kcherki
Dec 25, 2024

Hello everyone,

I’m new to the DaisyUI community, and I’m excited to contribute for the first time! 😊

I’m currently working on a project using Windows as my development environment. I usually rely on WSL, which works fine but feels a bit heavy at times. I was wondering if anyone here develops directly on Windows?

When I try running npm run dev on my host environment (Windows), I encounter an error. However, it works perfectly under WSL. I’d really prefer to run this command directly on my Windows setup to test changes more quickly.

Has anyone experienced a similar issue or found a good workflow for this? Any advice would be greatly appreciated! 🙏

Thank you in advance for your help and for welcoming me to this amazing community!

saadeghi · 2024-12-26T09:53:04Z

saadeghi
Dec 26, 2024
Maintainer

Hey 👋
What's the error?

3 replies

kcherki Dec 26, 2024
Author

The specified file was not found.

On the other hand, it works fine under WSL; it's just a matter of the environment being heavy

saadeghi Dec 26, 2024
Maintainer

Can you run npm run init first?

See CONTRIBUTING.md for more info:
https://github.com/saadeghi/daisyui/blob/master/.github/CONTRIBUTING.md#to-build-the-daisyui-node-package-on-local

kcherki Dec 26, 2024
Author

I followed the exact same steps under WSL for the build. The documentation worked perfectly there, but I encountered issues on Windows.

npm run build 

> [email protected] build
> node src/build

Error executing commands: Error: Command failed: node_modules/.bin/postcss --config src/base src/base/*.css --base src --dir dist
'node_modules' n'est pas reconnu en tant que commande interne
ou externe, un programme ex�cutable ou un fichier de commandes.

    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:514:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'node_modules/.bin/postcss --config src/base src/base/*.css --base src --dir dist'        
}

npm run init

> [email protected] init
> npm install && npm run build && cd src/docs && npm install && npm run get-json --silent && cd src/experiments/playground && npm install

[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[##################] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode#######] \ reify:@biomejs/cli-darwin-arm64: timing reifyNode:node_modules/[#
63 packages are looking for funding
  run `npm fund` for details

7 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

> [email protected] build
> node src/build

Error executing commands: Error: Command failed: node_modules/.bin/postcss --config src/base src/base/*.css --base src --dir dist
'node_modules' n'est pas reconnu en tant que commande interne
ou externe, un programme ex�cutable ou un fichier de commandes.

    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:514:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'node_modules/.bin/postcss --config src/base src/base/*.css --base src --dir dist'        
}
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/svelte
npm WARN   dev svelte@"5.0.0-next.178" from the root project
npm WARN   5 more (@sveltejs/kit, @sveltejs/vite-plugin-svelte, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer svelte@"^3.19.0 || ^4.0.0" from [email protected]
npm WARN node_modules/svelte-hmr
npm WARN   svelte-hmr@"^0.16.0" from @sveltejs/[email protected]
npm WARN   node_modules/@sveltejs/vite-plugin-svelte
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/svelte
npm WARN   peer svelte@"^3.19.0 || ^4.0.0" from [email protected]
npm WARN   node_modules/svelte-hmr
npm WARN     svelte-hmr@"^0.16.0" from @sveltejs/[email protected]
npm WARN     node_modules/@sveltejs/vite-plugin-svelte
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/svelte
npm WARN   dev svelte@"5.0.0-next.178" from the root project
npm WARN   5 more (@sveltejs/kit, @sveltejs/vite-plugin-svelte, ...)
npm WARN peer svelte@"^3.0.0" from [email protected]
npm WARN node_modules/svelte-inview        
npm WARN   svelte-inview@"^3.0.0" from [email protected]
npm WARN   node_modules/svelte-countup     
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/svelte
npm WARN   peer svelte@"^3.0.0" from [email protected]
npm WARN   node_modules/svelte-inview      
npm WARN     svelte-inview@"^3.0.0" from [email protected]
npm WARN     node_modules/svelte-countup   
[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.o[##################] / reify:caniuse-lite: http fetch GET 200 https://registry.npmjs.onpm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     'C:\\\\daisyui\\src\\docs\\node_modules\\esbuild',
npm WARN cleanup     [Error: EBUSY: resource busy or locked, rmdir 'C:\\daisyui\src\docs\node_modules\esbuild'] {
npm WARN cleanup       errno: -4082,       
npm WARN cleanup       code: 'EBUSY',      
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'C\\daisyui\\src\\docs\\node_modules\\esbuild'      
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'C:\\Users\\\\Documents\\Projets\\opensource\\daisyui\\src\\docs\\node_modules\\esbuild',
npm WARN cleanup     [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\esbuild'] {
npm WARN cleanup       errno: -4082,       
npm WARN cleanup       code: 'EBUSY',      
npm WARN cleanup       syscall: 'rmdir',   
npm WARN cleanup       path: 'C:\\Users\\\\Documents\\Projets\\opensource\\daisyui\\src\\docs\\node_modules\\esbuild'      
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
[##################] \ reify:caniuse-lite: WARN cleanup Failed to remove some director[##################] \ reify:caniuse-lite: WARN cleanup Failed to remove some directornpm ERR! code 1
npm ERR! path C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\@sveltejs\kit
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node postinstall.js
npm ERR! Error: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
npm ERR!     at requireWithFriendlyError (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:59:9)
npm ERR!     at Object.<anonymous> (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:68:76)
npm ERR!     ... 3 lines matching cause stack trace ...
npm ERR!     at Module._load (node:internal/modules/cjs/loader:938:12)
npm ERR!     at cjsLoader (node:internal/modules/esm/translators:283:17)
npm ERR!     at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:233:7)  
npm ERR!     at ModuleJob.run (node:internal/modules/esm/module_job:217:25)
npm ERR!     at async ModuleLoader.import (node:internal/modules/esm/loader:308:24) { 
npm ERR!   [cause]: Error: Cannot find module '@rollup/rollup-win32-x64-msvc'
npm ERR!   Require stack:
npm ERR!   - C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js
npm ERR!       at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)  
npm ERR!       at Module._load (node:internal/modules/cjs/loader:901:27)
npm ERR!       at Module.require (node:internal/modules/cjs/loader:1115:19)
npm ERR!       at require (node:internal/modules/helpers:130:18)
npm ERR!       at requireWithFriendlyError (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:41:10)
npm ERR!       at Object.<anonymous> (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:68:76)
npm ERR!       at Module._compile (node:internal/modules/cjs/loader:1241:14)
npm ERR!       at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)   
npm ERR!       at Module.load (node:internal/modules/cjs/loader:1091:32)
npm ERR!       at Module._load (node:internal/modules/cjs/loader:938:12) {
npm ERR!     code: 'MODULE_NOT_FOUND',     
npm ERR!     requireStack: [
npm ERR!       'C:\\Users\\\\Documents\\Projets\\opensource\\daisyui\\src\\docs\\node_modules\\rollup\\dist\\native.js'    
npm ERR!     ]
npm ERR!   }
npm ERR! }
npm ERR! node:internal/process/promises:289
npm ERR!             triggerUncaughtException(err, true /* fromPromise */);
npm ERR!             ^
npm ERR!
npm ERR! Error: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
npm ERR!     at requireWithFriendlyError (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:59:9)
npm ERR!     at Object.<anonymous> (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:68:76)
npm ERR!     ... 3 lines matching cause stack trace ...
npm ERR!     at Module._load (node:internal/modules/cjs/loader:938:12)
npm ERR!     at cjsLoader (node:internal/modules/esm/translators:283:17)
npm ERR!     at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:233:7)  
npm ERR!     at ModuleJob.run (node:internal/modules/esm/module_job:217:25)
npm ERR!     at async ModuleLoader.import (node:internal/modules/esm/loader:308:24) { 
npm ERR!   [cause]: Error: Cannot find module '@rollup/rollup-win32-x64-msvc'
npm ERR!   Require stack:
npm ERR!   - C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js
npm ERR!       at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)  
npm ERR!       at Module._load (node:internal/modules/cjs/loader:901:27)
npm ERR!       at Module.require (node:internal/modules/cjs/loader:1115:19)
npm ERR!       at require (node:internal/modules/helpers:130:18)
npm ERR!       at requireWithFriendlyError (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:41:10)
npm ERR!       at Object.<anonymous> (C:\Users\\Documents\Projets\opensource\daisyui\src\docs\node_modules\rollup\dist\native.js:68:76)
npm ERR!     code: 'MODULE_NOT_FOUND',
npm ERR!     requireStack: [
npm ERR!       'C:\\Users\\\\Documents\\Projets\\opensource\\daisyui\\src\\docs\\node_modules\\rollup\\dist\\native.js'
npm ERR!     ]
npm ERR!   }
npm ERR! }
npm ERR!
npm ERR! Node.js v20.6.1

npm ERR! A complete log of this run can be found in: C:\Users\\AppData\Local\npm-cache\_logs\2024-12-26T14_56_36_433Z-debug-0.log

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Seeking Advice: Running npm run dev on Windows Environment #3341

{{title}}

Replies: 1 comment 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Seeking Advice: Running npm run dev on Windows Environment #3341

kcherki Dec 25, 2024

Replies: 1 comment · 3 replies

saadeghi Dec 26, 2024 Maintainer

kcherki Dec 26, 2024 Author

saadeghi Dec 26, 2024 Maintainer

kcherki Dec 26, 2024 Author

I followed the exact same steps under WSL for the build. The documentation worked perfectly there, but I encountered issues on Windows.

kcherki
Dec 25, 2024

Replies: 1 comment 3 replies

saadeghi
Dec 26, 2024
Maintainer

kcherki Dec 26, 2024
Author

saadeghi Dec 26, 2024
Maintainer

kcherki Dec 26, 2024
Author