Open lolieatapple opened 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.
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.
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.
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.
@lolieatapple did you get your pronect working when installing those missing packages? Or did you have those installed globally on your system?
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".
It was good on my MacOS, so I think it maybe some issue for windows OS.
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.
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.
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
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