8000
add plugins/vscode folder and update vsix package scripts by qdaxb · Pull Request #2596 · RooCodeInc/Roo-Code · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to the concept outlined in #2536, the initial implementation of steps 1 and 2 has been completed. The extension.js file and the packaging-related scripts have been moved to the plugins/vscode directory.
This is an initial attempt to explain the previous concept and to facilitate further discussion. Some commands may still require additional compatibility adjustments.
Implementation
Added a new plugins/vscode directory to manage all VSCode extension-related source code, configuration, and packaging scripts separately. Migrated the extension entry file and theme files into this directory.
Introduced and improved plugin-specific files such as package.json, package-lock.json, .gitignore, .vscodeignore, build.js, tsconfig.json, and scripts/postpack.js to support development, building, and packaging of the extension.
Updated .vscode/launch.json and .vscode/tasks.json to enable debugging and building the extension within the new directory, with relevant parameters and output paths pointing to plugins/vscode.
Removed the old esbuild.js from the project root, as the related build process has been migrated or is no longer needed.
use npm run build in root dir to build plugin, and the output will located in plugins/vscode/bin.
Screenshots
before
after
How to Test
Get in Touch
Important
Reorganize VSCode extension files into plugins/vscode, update build scripts, and remove obsolete files.
Directory Structure:
Added plugins/vscode directory for VSCode extension-related files.
Moved extension.ts and theme files to plugins/vscode/src.
Build Process:
Introduced build.js in plugins/vscode for building the extension.
Updated package.json scripts to use new build process.
Removed esbuild.js from the root directory.
Configuration Files:
Added package.json, .gitignore, .vscodeignore in plugins/vscode.
Updated .vscode/launch.json and .vscode/tasks.json for new directory.
Miscellaneous:
Added postpack.js script in plugins/vscode/scripts for cleanup after packaging.
This description was created by for fe8f7ce. It will automatically update as commits are pushed.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Is this ready for review? If so do you mind taking a look at the test failures?
@cte I’ve resolved the test failure issue. I think we can first review the overall approach—if it looks good, then I’ll proceed to update the package.json.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestio
2FD9
ns cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
According to the concept outlined in #2536, the initial implementation of steps 1 and 2 has been completed. The
extension.jsfile and the packaging-related scripts have been moved to theplugins/vscodedirectory.This is an initial attempt to explain the previous concept and to facilitate further discussion. Some commands may still require additional compatibility adjustments.
Implementation
use
npm run buildin root dir to build plugin, and the output will located inplugins/vscode/bin.Screenshots
How to Test
Get in Touch
Important
Reorganize VSCode extension files into
plugins/vscode, update build scripts, and remove obsolete files.plugins/vscodedirectory for VSCode extension-related files.extension.tsand theme files toplugins/vscode/src.build.jsinplugins/vscodefor building the extension.package.jsonscripts to use new build process.esbuild.jsfrom the root directory.package.json,.gitignore,.vscodeignoreinplugins/vscode..vscode/launch.jsonand.vscode/tasks.jsonfor new directory.postpack.jsscript inplugins/vscode/scriptsfor cleanup after packaging.This description was created by
for fe8f7ce. It will automatically update as commits are pushed.