@fictjs/webpack-plugin

Webpack 5 integration for the Fict compiler. The plugin and loader cooperate so local hook metadata is available before importers receive their final transform, including cold builds and circular module graphs.

This is the supported Rust replacement for @fictjs/babel-preset. Version 0.30.1 is the final release of the preset and in-tree legacy compiler; Fict 1.0.0 removes them. Do not configure the preset alongside this loader.

const { FictWebpackPlugin } = require('@fictjs/webpack-plugin')

module.exports = {
  module: {
    rules: [
      {
        test: /\.[cm]?[jt]sx?$/,
        exclude: /node_modules/,
        use: [{ loader: require.resolve('@fictjs/webpack-plugin/loader') }],
      },
    ],
  },
  plugins: [new FictWebpackPlugin()],
}

Resumability

The Webpack integration currently supports compiler transforms and reactive metadata, but it does not yet emit split handler chunks, assign public resumable module identities, or generate a resumability manifest. The loader therefore rejects resumable: true and user-provided publicModuleId values instead of emitting source-machine file:// QRLs that cannot be loaded from a Webpack deployment. Use @fictjs/vite-plugin for resumable builds.

If another Babel transform is needed, place its loader to the left of the Fict loader so it runs after Fict compilation. Do not also configure @fictjs/babel-preset in that Babel loader. This is also the required handoff for decorators: Fict accepts and preserves current standard decorators and legacy parameter decorators, while the downstream Babel or TypeScript loader owns their runtime lowering.

Local reactive metadata and importer dependency fingerprints are persisted in Webpack module build information, so watch rebuilds and filesystem-cache restores keep unchanged importers correct. Bare package imports can consume published fict.metadata / fict.exports declarations; every consulted package manifest and metadata sidecar is registered as a Webpack dependency and included in the importer fingerprint. See Third-party library metadata. For legacy packages without exports, entry proof follows Webpack's effective mainFields, mainFiles, and extensions order and accepts only a uniquely matched file contained by the package. Active package aliasFields, directory targets, and ambiguous public spellings fail closed when Fict metadata is declared. Active extensionAlias, non-default exportsFields, custom description manifests, and malformed export maps also fail closed because they cannot be proven as the documented package contract; publishing a canonical package.json exports map is recommended. Renamed externals can use package metadata only for an unambiguous plain Node target, a CommonJS module external (commonjs* / node-commonjs), and one canonical bare package request. The output must disable output.module, use the CommonJS chunk format, and have a static flat .cjs entry filename directly under output.path, including every entry filename override. output.clean must also be disabled. Resolution follows Node require semantics from that runtime directory; Webpack aliases, custom module directories, main fields, resolver plugins, and TypeScript path mappings do not redirect it. ESM/browser/host-provided externals, global or expression externals, request arrays or property access, output paths with a symlinked existing ancestor, dynamic, nested, or non-.cjs entry filenames, and non-canonical targets remain authoritatively unresolved. The plugin does not copy or manage an external package under output.path. Package metadata paths must currently be readable through Node's filesystem APIs. Yarn PnP zip archives and other virtual filesystems are not yet supported by this integration. Webpack library metadata publishing remains a separate capability.