There are a few issues that have emerged from making a VS Code Debugging Extension that I figured are worth tracking. Some of these may warrant their own bug tracking but I'll start the process here:
[ ] board-as-function doesn’t work because of the fetch path; it seems to be set as a string rather than a URL, which then causes the fetch to fail in node. Maybe we should be making everything URLs rather than strings?
[ ] Most of the graphs that load other graphs have /graphs in their path, which works in the web case, but doesn't work in the node/process.cwd case. In some cases the paths are hard-coded (like simplest.json) and so the VS Code debugger UI doesn’t allow the user to update it.
[ ] There’s some kind of issue with running locally in node and streams; it always fails and points back to the structuredClone call in breadboard/harness/local.ts. Not sure exactly what's causing that one.
[ ] Pinecone Kit has a top-level await which can’t be transpiled by esbuild for node18.
[ ] Multipart inputs are tricky to support because VS Code only supports file inputs & text inputs. It's not clear yet how we can make use of VS Code's features to pick up multiple items at once.
[ ] Call stacks: we should support them, but I’m mindful of adding it when the paths stuff might be changing
There are a few issues that have emerged from making a VS Code Debugging Extension that I figured are worth tracking. Some of these may warrant their own bug tracking but I'll start the process here:
board-as-function
doesn’t work because of the fetch path; it seems to be set as a string rather than a URL, which then causes the fetch to fail in node. Maybe we should be making everything URLs rather than strings?/graphs
in their path, which works in the web case, but doesn't work in the node/process.cwd case. In some cases the paths are hard-coded (likesimplest.json
) and so the VS Code debugger UI doesn’t allow the user to update it.structuredClone
call inbreadboard/harness/local.ts
. Not sure exactly what's causing that one.FYI @dglazkov