[RFC] Support VSCode extension

[louisgv]

How do you envision this feature/change to look/work like?

• Provides a vscode.ts OR vscode/index.ts

• Specifies target as vscode OR vscode-{vscode-verson}

• Dev can also export a config variable with all the typing needed for vscode (that has all the missing pieces of extension coming from the vscode extension manifest: https://code.visualstudio.com/api/references/extension-manifest )

• A VSCode extension is created under the build directory, under vscode-dev or vscode-prod

What is the purpose of this change/feature? Why?

To boldly go where no one has gone before.

(OPTIONAL) Example implementations

No response

(OPTIONAL) Contact Details

No response

Verify canary release

• [X] I verified that the issue exists in plasmo canary release

Code of Conduct

• [X] I agree to follow this project's Code of Conduct
• [X] I checked the current issues for duplicate problems.

[louisgv]

Likely will use esbuild - this will be the first step to integrate it into the plasmo sdk

[hijiangtao]

Can we consider WebStorm plugin likewise with same functionalities? 🤔

[louisgv]

Can we consider WebStorm plugin likewise with same functionalities? 🤔

Mhmm, does WebStorm also uses js for their core logic?

[ColdSauce]

Yeah that'd be great @hijiangtao. If you could make a GitHub issue for that, and spearhead it, it'd be greatly appreciated!

[hijiangtao]

Can we consider WebStorm plugin likewise with same functionalities? 🤔

Mhmm, does WebStorm also uses js for their core logic?

Well, WebStorm is a IDE for JavaScript development, but to develop a plugin for it, I think the program language is not JavaScript instead.

[hijiangtao]

Yeah that'd be great @hijiangtao. If you could make a GitHub issue for that, and spearhead it, it'd be greatly appreciated!

I read the description about the RFC again, and I think it may be hard to get a WebStorm plugin with same functionalities, since developers may need to be familiar with other program languages (other than JS)?