Keep ignored relative imports beside their runtime entry

When a library excludes a relative dynamic import from bundling, the browser resolves it beside the emitted importing script. A successful application build does not mean that sibling module was emitted there. Inspect failed request URLs and the library's import directives. If the library requires native module loading, deploy its unchanged entry and runtime siblings together at a versioned same-origin path and preserve the entry's native import. Verify cold inference through the production artifact: a development harness can resolve the same dependency differently and hide the defect.

Applies when: a bundled browser library loads optional runtime modules using ignored relative imports. Keywords: browser bundler dynamic import relative module missing runtime deployment