✨ feat(extension): Add auto-restart for core changes in dev mode #351
Conversation
hassoncs
force-pushed
the
auto-restart-ext-host-watcher
branch
from
81a0f8d to
1be2eb0
Compare
|
hassoncs
force-pushed
the
auto-restart-ext-host-watcher
branch
from
1be2eb0 to
cff7fd7
Compare
janpaul123
left a comment
janpaul123
left a comment
There was a problem hiding this comment.
Seems good to me! Maybe make a PR to Roo as well?
- implement file system watcher for core files - automatically reload extension host on changes - enhance development experience by eliminating manual restarts 📝 docs(DEVELOPMENT.md): update hot reloading instructions - clarify auto-reload behavior for core extension changes - specify development mode requirements for auto-reloading
hassoncs
force-pushed
the
auto-restart-ext-host-watcher
branch
from
cff7fd7 to
d170fc8
Compare
kevinvandijk
left a comment
kevinvandijk
left a comment
There was a problem hiding this comment.
Awesome! Can we also provide this to Roo Code?
|
Haha jinx @kevinvandijk |
|
Opened a PR on Roo here: RooCodeInc/Roo-Code#3284 |
| if (enableCoreAutoReload) { | ||
| console.log(`♻️♻️♻️ Core auto-reloading is ENABLED!`) | ||
| const watcher = vscode.workspace.createFileSystemWatcher( | ||
| new vscode.RelativePattern(context.extensionPath, "src/**/*.ts"), |
There was a problem hiding this comment.
What happens if we change.a different file; e.g. one of the translation .json files?
|
I love it. @hassoncs Thanks for updating the docs!!! ❤️ |
|
Is there a chance we will want to have it more flexible? Like, keep the DEV environment but disable auto-reload? Just asking. |
I'd wait for someone tell us about an actual use case for that. As a workaround this is easy to find and comment out (bc of the console logs). |
Until now, it was necessary to halt the debugging process, terminate all tasks, and restart the extension host to see
corechanges. Now, with this change, we now monitor the files within the core directory. If any changes are detected, we trigger a reload command within the extension, effectively enabling hot reloading within the extensionDev notes
ENABLE_CORE_AUTO_RESTART, but instead just based it on the NODE_ENV. Let me know if you think the env var would be better! (or something else!)📝 docs(DEVELOPMENT.md): update hot reloading instructions