# X_SIDE_EFFECTS_UNANCHORED

## Means

a module on `SIDE_EFFECTS_ANCHORS` that no entry imports for effect

## Typical cause

the module registers something on behalf of a module that never imports it, so nothing puts it in the graph when none of its own bindings is used. The `sideEffects` array alone is not the enforcement: Bun before 1.4.1 read any array as `false` and shook the named module out ([oven-sh/bun#40650](https://github.com/oven-sh/bun/issues/40650)) — measured then, `@ultimat3/core`'s `schema-error-codes.ts` flapped 12 builds in 60 on Bun 1.4.0 and 28 in 60 on 1.3.14 in `examples/dummy`'s feed island, and every `X_VALIDATION_FAILED` rendered untitled in the browser. Fixed upstream in 1.4.1; the bare import is what holds on every bundler

## Fix

add `import './<module>';` to that package's `src/index.ts` and keep the module in the package's `"sideEffects"` array — a bare import is a statement rather than a binding, and a bundler that honours the array keeps a bare-imported module only if the array lists it

[CLI and verify](/error-codes#cli-and-verify)