Open flazouh opened 6 months ago
Yeah, the port should save on change. Not sure what caused the problem. I haven't used esbuild myself.
it's not really about esbuild, anything should work since you're calling method on the listener class, but now it works, thanks for the extension, it's actually the best i've found among many ones I tried.
It doesn't work again. I don't know why. port 6000 on both the extension settings and in the
const reloader = new Reloader({
port: 6000,
})
i get :
Error: No process running on port
in offscreen.js
Port 6000 is restricted in Chrome. Use a different port, make sure it's not on this list.
In your the offscreen screenshot Advanced Extension Reloader tries to connect to a server with port 6060 not 6000. See GET http://localhost:6060/socket.io/... in your screenshot. Are you sure port 6000 is in the settings, or do you use 6060 alongside with 6000?
When and where do you get the "Error: No process running on port" error?
Here is my settings
const reloader = new Reloader({
port: 6223,
})
Error: No process running on port
at node_modules/advanced-extension-reloader-watch-2/umd/reloader.js:9:618699
I tested it and was not able to reproduce this bug. Need more info. I'm reopening this issue, maybe someone else knows the cause of this.
Btw, I tried again and had to do
import Reloader from 'advanced-extension-reloader-watch-2/es/reloader'
// @ts-ignore
const reloader = new Reloader.default({
port: 6223,
})
with this tsconfig:
{
"compilerOptions": {
"noUncheckedIndexedAccess": true,
"strict": true,
"allowJs": true,
"allowSyntheticDefaultImports": true,
"baseUrl": "./",
"esModuleInterop": true,
"experimentalDecorators": true,
"jsx": "react-jsx",
"module": "esnext",
"moduleResolution": "node",
"noImplicitAny": true,
"resolveJsonModule": true,
"paths": {
"common": [
"./common"
]
},
"sourceMap": true,
"target": "esnext",
"types": [
"chrome",
"node",
"react",
"react-dom"
]
},
"include": [
"esbuild.prod",
"esbuild.dev",
"chrome-webstore-manager",
"environment.d.ts",
"src/**/*",
"common/**/*",
"background/**/*",
"resources/**/*",
"popup/**/*",
"_locales/**/*",
"scripts/*",
]
}
I don't know why this problem arose.
But regarding the port problem, it seems resolved.
I managed to reproduce this issue on Linux. The advanced-extension-reloader-watch-2 didn't actually work there at all for me (tested on Ubuntu).
I released an update to advanced-extension-reloader-watch-2 some time ago that may have fixed the issue on macOS too. If you're still interested in using the extension you can test it now.
Also, fixed another issue with Chrome stealing focus on an extension reload.
Привет, I have an issue using the reloading with the Reloader from advanced-extension-reloader-watch-2 with esbuild.
My esbuild config:
my config in chrome:
Do you have any idea why this is happening?
Cпасибо тебе.
EDIT: It works, i don't know what I changed, does editing the port in the settings saves on change ? 🤔