-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: add missing bundle and watch:bundle tasks to root turbo.json #6433
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
Conversation
Fixes #6432 - Windows debugging issue where VSCode debug configuration failed because the root turbo.json was missing the bundle and watch:bundle task definitions that are required by the debug tasks. The issue occurred because: - VSCode debug configuration runs the default build task (watch) - The watch task depends on watch:bundle via turbo - Root turbo.json was missing bundle and watch:bundle task definitions - This caused "Cannot find module extension.js" error on Windows Changes: - Added bundle task with outputs configuration - Added watch:bundle task with cache disabled - Both tasks now properly delegate to workspace-specific implementations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this fix! This correctly addresses the Windows debugging issue by adding the missing turbo task definitions. I've reviewed the changes and have some suggestions to improve consistency and robustness.
| "inputs": ["src/**", "package.json", "tsconfig.json", "tsup.config.ts", "vite.config.ts"] | ||
| }, | ||
| "bundle": { | ||
| "outputs": ["dist/**", "src/dist/**"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bundle task is missing inputs configuration. Should this include the same inputs as the build task (src/**, package.json, tsconfig.json, etc.) to ensure proper cache invalidation when source files change?
| }, | ||
| "bundle": { | ||
| "outputs": ["dist/**", "src/dist/**"] | ||
| }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentional that the bundle task configuration is minimal compared to other tasks? For consistency, could it follow the same pattern as the build task with comprehensive inputs configuration?
|
Closing, can't repro |
Fixes #6432 - Windows debugging issue where VSCode debug configuration failed because the root turbo.json was missing the bundle and watch:bundle task definitions.
Problem
Users on Windows were unable to debug the extension in VSCode because:
Solution
Added the missing task definitions to root turbo.json:
bundletask with proper outputs configurationwatch:bundletask with cache disabledTesting
npx turbo bundleworks correctlynpx turbo watch:bundle --dry-runrecognizes the taskThis fix ensures that the VSCode debug configuration will work properly on Windows by making sure all required turbo tasks are defined at the root level.
Important
Adds missing
bundleandwatch:bundletasks toturbo.jsonto fix Windows VSCode debugging issue.bundleandwatch:bundletasks toturbo.jsonto fix Windows VSCode debugging issue.bundletask includes outputs configuration fordist/**andsrc/dist/**.watch:bundletask has caching disabled.npx turbo bundleandnpx turbo watch:bundle --dry-runwork correctly.extension.jsis generated insrc/dist/.This description was created by
for fe87e25. You can customize this summary. It will automatically update as commits are pushed.