vercel / next.js

The React Framework
https://nextjs.org
MIT License
126.93k stars 26.98k forks source link

next dev can not run on windows 10 #55096

Open lolieatapple opened 1 year ago

lolieatapple commented 1 year ago

Link to the code that reproduces this issue or a replay of the bug

https://github.com/lolieatapple/token-pair-manager.git

To Reproduce

$ yarn next dev yarn run v1.9.2 $ D:\Aaron\gopath\src\github.com\cross-config-manager\node_modules.bin\next dev

other version: $ yarn dev yarn run v1.9.2 $ next dev

It show Done and exit automatic. I can't use it anymore.

Current vs. Expected behavior

Not show done exit, just wait after:

Verify canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: ia32
      Version: Windows 10 Enterprise
    Binaries:
      Node: 16.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: 13.4.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A

Which area(s) are affected? (Select all that apply)

Not sure, CLI (create-next-app), Operating System (Windows, MacOS, Linux), SWC minifier (swcMinify: true), SWC transpilation

Additional context

No response

JesseKoldewijn commented 1 year ago

Must say, I'm trying to reproduce your issue by the use of the provided repo you mentioned in the issue but can't reproduce it unfortunatly. On my end (tested on win 10, win 11 and a win 10 vm) but the only thing I get is errors with regards to the ws package you're using. The server runs fine but the log gets flooded with errors due to this package.

It's trying to use a utf-8-validate and bufferutil package which is missing.

JesseKoldewijn commented 1 year ago

When adding these previously mentioned two packages the only thing I get is a error because I dont have the env vars required for your iwan-sdk usage. which is understandable.

rigobertoalag commented 1 year ago

I have the same problem when I run the npm run dev command it does not show the console.log and the onClick functions are not executed.

JesseKoldewijn commented 1 year ago

I have the same problem when I run the npm run dev command it does not show the console.log and the onClick functions are not executed.

When having installed those missing packages, you should get an error when running the dev command saying you're missing the env vars required. Other than that I didn't find anything being broken on any of the systems I've tested the mentioned repo on.

JesseKoldewijn commented 1 year ago

@lolieatapple did you get your pronect working when installing those missing packages? Or did you have those installed globally on your system?

lolieatapple commented 1 year ago

Hi, It's not a problem with missing packages. Even when I create a brand new project using create-next-app, it still doesn't run properly. Normally, after running "yarn dev", it should pause instead of exiting after displaying "Done".

lolieatapple commented 1 year ago

It was good on my MacOS, so I think it maybe some issue for windows OS.

JesseKoldewijn commented 1 year ago

If it wasn't a local issue it would also have happened on one of my systems tho. So I do think it might have something to do with your local setup.

kdy1 commented 1 year ago

I'm not sure why the WASM build is used for windows 10.

Also, removing swc minify label as it's not used for dev mode.