-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Where is vscode.proposed.d.ts
?
#136964
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@jrieken will it still be possible for extensions to pass |
Yes, it will still be possible to use the |
@jrieken, is there any CLI option for the new |
The "old", existing CLI option works for the new property. When passed it enables all proposals for an extension. However, it isn't backwards compatible, e.g when users have an old version of VS Code with a new version of your extension than it won't enable the "old world". Tho, I would argue that's a corner-case as the CLI option is intended for special cases. |
Thanks for the details @jrieken, that makes sense 👍 We do have user reporting that Code OSS 1.63.2 have problems with the latest Copilot (using |
Yes, this should work with 1.63.2 |
Closing as we have shipped with the split up |
The
vscode.proposed.d.ts
-file has been split up into separate files, each representing one proposal. This enables scoped access to proposals (see #131165 for details and discussion)Extensions need to opt into specific proposals via the new
package.json#enabledApiProposals
-property. TheenableProposedApi
-property will stop working soon.Migration Guide
First, validate that you still need proposed API access. Often proposals have been finalized and using proposed API isn't needed anymore. Try this:
vscode.d.ts
via@types/vscode
or>npx vscode-dts main
vscode.proposed.d.ts
-filepackage.json#enableProposedApi
-property.You have validated that your extension still depends on proposed API. Do the following:
package.json#enabledApiProposals
. It's this property that enables proposals!vscode.proposed.d.ts
-filevscode-dts
and runnpx vscode-dts dev
to fetch the proposal-definitions you need.More tricky is proposed API usage that isn't TypeScript, namely proposed contribution points or properties of
package.json
. This is fortunately rare and but some manual labor and diligence is needed. Check thevscode.proposed.contribXYZ.d.ts
files forpackage.json
-properties you are using and add the proposal names to thepackage.json#enabledApiProposals
-propertyFAQ
Sample
This is a sample commit microsoft/vscode-anycode@cf73d4d that migrates anycode onto a specific API proposal.
Is this a breaking change?
Not yet. For now we are breaking up
vscode.proposed.d.ts
but we still honor theenableProposedApi
-property for a bit. So, you likely see TypeScript compile errors but the runtime behavior isn't changed yet.Are changes to
package.json
and tovscode.proposed.XYZ.d.ts
needed?The changes to
package.json#enabledApiProposals
are absolutely needed, they are the truth whiledts
files are "only" needed for the TypeScript compiler.What about
package.json#enableProposedApi
When your extension is enabled via our
product.json
-file you can safely remove the property. VS Code will enable your extension, also older version which don't supportenabledApiProposals
yet.The text was updated successfully, but these errors were encountered: