tsci dev: ngspice spiceEngine from tscircuit.config.ts fails three ways (package.json, top-level await, blob import)
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, react, typescript
Research direction
Start in loadTscircuitConfig, where tscircuit.config.ts is evaluated, and compare how importEvalPath resolves @tscircuit/ngspice-spice-engine against the tsci build path. The browser failure needs the analog simulation loader and the blob import resolution, which the payload does not show. Done means tsci dev loads the ngspice config, runs the analog simulation without the blob import error, and the top-level await case works or gives a clear message.
Written by the indexing model from the issue text.
Description
Problem
A project that registers ngspice in tscircuit.config.ts works with tsci build and tsci simulate, but not in tsci dev. There are three separate failures in a row. The first two have workarounds; the third doesn't.
Versions: tscircuit 0.0.3062 (CLI), @tscircuit/core 0.0.2259, @tscircuit/ngspice-spice-engine 0.0.22, @tscircuit/eval 0.0.1696, macOS arm64, Bun 1.3.14.
Repro
tsci init ngspice-dev-repro -y && cd ngspice-dev-repro
index.circuit.tsx:
export default () => (
<board width="20mm" height="15mm" routingDisabled>
<voltagesource name="V1" voltage="5V" />
<resistor name="R1" resistance="1k" connections={{ pin1: ".V1 > .pin1" }} />
<capacitor name="C1" capacitance="10uF" connections={{ pin1: ".R1 > .pin2", pin2: ".V1 > .pin2" }} />
<voltageprobe name="VCAP" connectsTo=".C1 > .pin1" />
<analogsimulation duration="50ms" timePerStep="0.5ms" spiceEngine="ngspice" />
</board>
)
Failure 1: package not in package.json
tscircuit.config.ts:
import createNgspiceSpiceEngine from "@tscircuit/ngspice-spice-engine"
export default {
platformConfig: { spiceEngineMap: { ngspice: await createNgspiceSpiceEngine() } },
}
tsci build index.circuit.tsx works (the package is installed as a transitive dependency of tscircuit). tsci dev → Errors:
Execution Error: Node module imported but not in package.json "@tscircuit/ngspice-spice-engine"
importEvalPath("./tscircuit.config.ts", ...) importLocalFile("tscircuit.config.ts")
importEvalPath("@tscircuit/ngspice-spice-engine", ...) importNodeModule("@tscircuit/ngspice-spice-engine")
at loadTscircuitConfig
Workaround: bun add -d @tscircuit/ngspice-spice-engine.
Failure 2: top-level await in tscircuit.config.ts
With the same config, tsci dev then shows:
Execution Error: Error evaluating "tscircuit.config.ts": Unexpected identifier '_ngspicespiceengine2'
at loadTscircuitConfig
The in-browser evaluator can't handle the top-level await, though the CLI can. Workaround: create the engine lazily.
let engine: ReturnType<typeof createNgspiceSpiceEngine> | undefined
export default {
platformConfig: {
spiceEngineMap: {
ngspice: {
simulate: async (spice: string) => {
engine ??= createNgspiceSpiceEngine()
return (await engine).simulate(spice)
},
},
},
},
}
Failure 3: the engine can't load in the dev browser (no workaround)
The config now loads, and the PCB view renders. ⋯ → Analog Simulation shows:
Error running analog simulation
Import "blob:http://localhost:3020/352059b6-0861-489a-8d1d-2f9bf2683551" not found in "node_modules/@tscircuit/ngspice-spice-engine/dist"
The same circuit with the default spicey engine (no spiceEngine prop) renders its graph in the Analog Simulation view.
Expected
Either ngspice works in tsci dev, or the docs say that spiceEngine="ngspice" is CLI-only. It would also help if failures 1 and 2 gave a hint, since the same config works in tsci build.
🤖 Generated with Claude Code
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 115
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 260
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tscircuit/cli
-
`tsci check` and `tsci check netlist` exit 0 when they report errorsPossibly taken @aswadi claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
@tscircuit/cli 0.1.2452 bundles brace-expansion 2.0.1 and minimatch 5.1.2 (via make-vfs), both with published advisoriesMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
tsci export -f glb can't load a relative cadModel stepUrl (404); build --glbs canPossibly taken @jeffrey-graham claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
The CLI needs Bun: under Node alone `tsci` fails and the Node entry can't load `.tsx`Possibly taken @cocvn157 claimed this 7 days ago. Open
Difficulty 4/5 1-2 days Newbie friendliness 35/100
tscircuit/cli#5449 · 1 comment ·
Maintainers usually reply within 1 day
-
`tsci check netlist` prints `undefined` after a resistor's value and labels resistor pins anode / cathodePossibly taken @cocvn157 claimed this 10 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
tscircuit/cli#5447 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
"code source" and "numerique.gouv" links: "new window" mention duplicated in the accessible nameOpenaccessibility
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
numerique-gouv/lasuite-landingpage#315 ·
Maintainers usually reply within 1 day
-
needs:triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
HyeokjaeChoi/vaultme#585 ·
Maintainers usually reply within 1 day
-
enhancement priority/P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
beettlle/pi-smart-router#200 ·