Proposal: Official @rsbuild/plugin-block-imports - A General Utility to Control/Filter Imports and File Resolution

[malekabdelkader]

1. 🛑 The Core Problem: Next.js Artifact Leakage

I've experienced a critical, repeatable bug across multiple companies using Module Federation and R2WC with Rsbuild/Rspack.

When components originating from a Next.js environment are shared, unresolvable imports like next/link, next/image, etc., leak into the consumer bundle. This causes hard-to-debug runtime errors in the final application, stalling micro-frontend adoption.

2. ✅ The Solution: Import Filtering Utility

I have created rsbuild-plugin-block-imports to address this with a clean, declarative API.

This plugin is a general utility that allows users to define modules or regex patterns that must be detected , Logged and forced a build error (Optional) , acting as an essential architectural guardrail.

Key API Example

The plugin immediately solves the interoperability issue:

// rsbuild.config.ts
import { defineConfig } from '@rsbuild/core';
import { pluginBlockImports, NEXTJS_FORBIDDEN_IMPORTS } from 'rsbuild-plugin-block-imports';
// to be adopted as @rsbuild/plugin-block-imports

export default defineConfig({
  plugins: [
    pluginBlockImports({
      forbiddenImports: [
        ...NEXTJS_FORBIDDEN_IMPORTS,
        { pattern: 'my-custom-import', alternative: 'Use X instead' },
        failOnError: true //Whether to fail the build on errors
      ],
    }),
  ],
});

3. ➡️ Request for Official Adoption

Given that this resolves a critical, recurring pain point in large-scale component sharing, I believe it should be an official Rsbuild utility.

• Current implementation:
  https://github.com/malekabdelkader/rsbuild-plugin-block-imports
  https://www.npmjs.com/package/rsbuild-plugin-block-imports
• Action Request: Are the core maintainers open to adopting this as an official plugin, @rsbuild/plugin-block-imports? If so, please advise on the correct repository for a Pull Request.

[chenjiahan]

Thanks for the suggestion and for sharing this plugin. It addresses a real problem in practice.

Given the limited maintenance capacity of the core team, I prefer to keep this plugin maintained in the community rather than moving it into the official Rsbuild plugins.

I have added it to awesome-rstack so that more people who need it can easily find it.

[malekabdelkader]

Thanks for the suggestion and for sharing this plugin. It addresses a real problem in practice.

Given the limited maintenance capacity of the core team, I prefer to keep this plugin maintained in the community rather than moving it into the official Rsbuild plugins.

I have added it to awesome-rstack so that more people who need it can easily find it.

Fair enough , i appreciate that