Problem
Extractor probes are designed to run inside browsers, so they must not
import or rely on methods that require Node.js runtime APIs (e.g. node:fs,
node:path, etc.). Currently, there's no automated check
to catch such dependencies if they're accidentally introduced.
Goal
Add tests that verify extractors remain free of Node.js-specific
dependencies, so regressions are caught automatically (e.g. in CI) rather
than discovered at runtime in a browser environment.
Solution
Use esbuild like the front-end ?
Problem
Extractor probes are designed to run inside browsers, so they must not
import or rely on methods that require Node.js runtime APIs (e.g.
node:fs,node:path, etc.). Currently, there's no automated checkto catch such dependencies if they're accidentally introduced.
Goal
Add tests that verify extractors remain free of Node.js-specific
dependencies, so regressions are caught automatically (e.g. in CI) rather
than discovered at runtime in a browser environment.
Solution
Use esbuild like the front-end ?