feat: Dynamically load ngspice engine with CDN fallback #1402
+237
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces dynamic, on-demand loading for the ngspice engine and configures it as the default SPICE simulation engine.
The loading mechanism first attempts a local dynamic import(). If this fails (e.g., in a browser), it falls back to fetching the engine from the jsDelivr CDN. This ensures ngspice is available in both Node.js and browser environments without impacting initial load times.
A Playwright test has been added to verify the CDN fallback functionality in a browser.