Custom context provider working when debugging Continue fails otherwise

[frblondin]

Custom context provider working when debugging Continue fails otherwise

[sestinj]

oh wait! Actually I found a solution: const execSync = (await require("child_process")).execSync;

Using require instead of import worked for me.

Everything else I said above is still true, I hope to let you just use normal imports within the next couple of days

[frblondin]

I confirm that provided workaround (with require) works. Thanks for working on using NodeJS in all cases!

I suggest to keep this issue open until you complete this work.

[sestinj]

@frblondin The work in moving to NodeJS is now done and available in pre-release 0.9.47.

I've confirmed that I could use import { execSync } from "child_process"; at the top of the file, but I'll wait to close this issue until I know it's good for you as well

[frblondin]

I confirm. Brillant!

[sestinj]

@frblondin The console output in developer tools actually does show logs from NodeJS as well, so nothing wrong here.

As for the other errors I'm running myself and will update in a minute, but looks related to just some mismatch between environments in debug vs. extension modes

[sestinj]

Ok same things you said happened when I tried. Did a bit of digging around, and it looks like VS Code, or more likely Electron itself, is using node:vm and not setting this parameter. This is something out of our control.

Luckily I'm working on a fix so you don't have to do dynamic imports (config.ts will run only in NodeJS, not the browser). I plan to spend the rest of today on shipping our first version of tab-autocomplete, but if you're willing to give me another day or two this will be done and there shouldn't be any problems.

And one other thing, the LLM will only see the content that you specify, so I would change to content: commit in the objects you are returning from parseGitLog.