continuedev / continuedev/continue

Can't package the continue extension to contribute to add a new model provider

Open
#3,826 4 comments 0 reactions 1 assignee View on GitHub

@bdougie is already working on this.

Since Oct 22, 2025.

area:build needs-triage os:mac
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
- OS:macOS
- Continue version: v0.8.67
- IDE version: Cursor
Description

Hello everyone,

  • I'm trying to add a new model provider (namely Infomaniak, which is a Swiss IT actor hosting LLama models on Swiss servers) in Continue.
  • I've added the Infomaniak.ts in llm/llms
  • Added Infomaniak in index.ts
  • Changed the config_schema.json accordingly
  • Each time I'm trying to run npm run package to package the extension and see if the new LLM provider works, I'm getting the following error.
  • I've also tried using Run and Debug, but I can't find where to change the config.json file to update the available model list

Thanks.

To reproduce

No response

Log output
(base) X@X-MBP vscode % npm run package

> continue@0.9.254 prepackage
> node scripts/prepackage.js

[info] Using target:  darwin-x64
[info] Packaging extension for target  darwin-x64
[info] npm install in extensions/vscode completed
[info] npm install in gui completed
node:fs:3029
  binding.copyFile(
          ^

Error: ENOENT: no such file or directory, copyfile '../extensions/vscode/gui/onigasm.wasm' -> '../extensions/intellij/src/main/resources/webview/onigasm.wasm'
    at Object.copyFileSync (node:fs:3029:11)
    at /Users/elliot/Documents/continue/extensions/vscode/scripts/prepackage.js:110:6
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '../extensions/vscode/gui/onigasm.wasm',
  dest: '../extensions/intellij/src/main/resources/webview/onigasm.wasm'
}

Node.js v20.11.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.