Member Junction
    Preparing search index...
    • Load-prevention export.

      Modern bundlers (ESBuild, Vite) tree-shake classes that are only ever instantiated dynamically through MJ's ClassFactory — which is exactly how segmenters and cleaners are resolved. If a built-in is dropped from the bundle, Resolve() returns null and the resolver silently degrades to its fallback: content still gets cleaned and chunked, just by the wrong strategy, with no error to show for it.

      Call this no-op from the consuming application's bootstrap to force a static reference so the @RegisterClass-decorated segmenters are retained.

      Returns void