Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: listen EADDRINUSE: address already in use :::35729 #592

Closed
yuis-ice opened this issue Feb 18, 2022 · 1 comment
Closed

Error: listen EADDRINUSE: address already in use :::35729 #592

yuis-ice opened this issue Feb 18, 2022 · 1 comment
Assignees
Milestone

Comments

@yuis-ice
Copy link

Expected Behavior

No error.
Or I'd like to know how to set a port instead of the default port.

Current Behavior

Error: listen EADDRINUSE: address already in use :::35729

Steps to Reproduce (for bugs)

git clone https://github.com/mikecrittenden/shortkeys
cd shortkeys
node -v # v16.13.2
npm i 
npm run dev chrome 
Error: listen EADDRINUSE: address already in use :::35729

The almost full error log:

> npm run dev chrome

> shortkeys@4.0.2 dev
> webextension-toolbox dev "chrome"


           ╔════════╗
╔══════════════════════════════╗
║     WEBEXTENSION-TOOLBOX     ║
╚══════════════════════════════╝
clean-webpack-plugin: C:\pg\_chrome_dev\shortkeys\dist\chrome has been removed.
Error: listen EADDRINUSE: address already in use :::35729
    at Server.setupListenHandle [as _listen2] (node:net:1334:16)
    at listenInCluster (node:net:1382:12)
    at Server.listen (node:net:1469:7)
    at new WebSocketServer (C:\pg\_chrome_dev\shortkeys\node_modules\ws\lib\websocket-server.js:68:20)
    at C:\pg\_chrome_dev\shortkeys\node_modules\webpack-webextension-plugin\index.js:109:21
    at new Promise (<anonymous>)
    at WebextensionPlugin.startServer (C:\pg\_chrome_dev\shortkeys\node_modules\webpack-webextension-plugin\index.js:106:12)
    at WebextensionPlugin.watchRun (C:\pg\_chrome_dev\shortkeys\node_modules\webpack-webextension-plugin\index.js:55:17)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\pg\_chrome_dev\shortkeys\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:21:17)
    at AsyncSeriesHook.lazyCompileHook (C:\pg\_chrome_dev\shortkeys\node_modules\tapable\lib\Hook.js:154:20)
    at Watching._go (C:\pg\_chrome_dev\shortkeys\node_modules\webpack\lib\Watching.js:41:32)
    at C:\pg\_chrome_dev\shortkeys\node_modules\webpack\lib\Watching.js:33:9
    at Compiler.readRecords (C:\pg\_chrome_dev\shortkeys\node_modules\webpack\lib\Compiler.js:529:11)
    at new Watching (C:\pg\_chrome_dev\shortkeys\node_modules\webpack\lib\Watching.js:30:17)
    at Compiler.watch (C:\pg\_chrome_dev\shortkeys\node_modules\webpack\lib\Compiler.js:244:10)
    at Command.watch (C:\pg\_chrome_dev\shortkeys\node_modules\webextension-toolbox\bin\webextension-toolbox:27:8) {
  code: 'EADDRINUSE',
  errno: -4091,
  syscall: 'listen',
  address: '::',
  port: 35729
}
C:\pg\_chrome_dev\shortkeys\node_modules\webextension-toolbox\bin\webextension-toolbox:57  console.log(stats.toString({
                    ^

TypeError: Cannot read properties of null (reading 'toString')

Context

I'd like to know how to set a port instead of the default port.

Your Environment

Tech Version
webextension-toolbox 3.0.0
node v16.13.2
OS windows 10
browser chrome
etc
@tm1000
Copy link
Member

tm1000 commented Mar 7, 2022

Hi There

Currently there is no way to change the port. It's something I will address in the future.

@tm1000 tm1000 added this to the 5.0.0 milestone Mar 7, 2022
@tm1000 tm1000 self-assigned this Mar 7, 2022
@tm1000 tm1000 closed this as completed in 16bf47d Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants