raydium-io / raydium-ui-v3

Open-source user interface for Raydium programs
https://raydium-ui-v3-kappa.vercel.app
Apache License 2.0
19 stars 26 forks source link

How to fix EACCES error? #14

Closed Web3Knight closed 1 week ago

Web3Knight commented 1 week ago

yesterday, I clone this repo and tested it on my local and it works fine. Today, it shows error when I run "npm run dev"

$ next dev --port 3000 ready - started server on 0.0.0.0:3000, url: http://localhost:3000 warn - You have enabled experimental feature (instrumentationHook) in next.config.js. warn - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

event - compiled client and server successfully in 8.1s (6076 modules) wait - compiling /instrumentation (client and server)... event - compiled successfully in 214 ms (477 modules) wait - compiling /swap (client and server)... event - compiled client and server successfully in 1777 ms (6207 modules) wait - compiling /404 (client and server)... event - compiled client and server successfully in 426 ms (6210 modules) error - Error: connect EACCES ::1:49184 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { type: 'Error', errno: -4092, code: 'EACCES', syscall: 'connect', address: '::1', port: 49184 } wait - compiling /_error (client and server)... bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

how to fix "error - Error: connect EACCES ::1:49184" ?

cruzshia commented 1 week ago

this looks like isn't code error, might cause by your pc's environment issues, try restart computer or re-install packages and try again.

Web3Knight commented 1 week ago

Thanks for your answer, Cruzshia. Did you experience similar blocker before? I restarted and reinstalled again, but same error :(

cruzshia commented 1 week ago

nope, still works fine in my every local pc.