Skip to content
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

fix and test loading ESM providers in VS Code #54

Merged
merged 1 commit into from
May 18, 2024
Merged

Conversation

sqs
Copy link
Member

@sqs sqs commented May 18, 2024

  • Use a hacky pure-JS converter from ESM to CommonJS instead of the esbuild approach, which was very heavyweight due to its use of wasm and was hard for consumers of @openctx/vscode-lib to use.
  • Refactor how clients can override imports.

@sqs sqs force-pushed the sqs/file-provider branch 4 times, most recently from bac69dc to 4803a17 Compare May 18, 2024 07:54
- Use a hacky pure-JS converter from ESM to CommonJS instead of the esbuild approach, which was very heavyweight due to its use of wasm and was hard for consumers of @openctx/vscode-lib to use.
- Refactor how clients can override imports.
@sqs sqs force-pushed the sqs/file-provider branch from e58bd7e to 41c6f54 Compare May 18, 2024 08:08
@sqs sqs merged commit ca3b342 into main May 18, 2024
11 checks passed
@sqs sqs deleted the sqs/file-provider branch May 18, 2024 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant