shakapacker 8.3.0 → 9.0.0.beta.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 85c3a527653e307cedc881f7879b245feaca4d79b47f7f7abac358f38a1e8305
-  data.tar.gz: eae6e26f151f0e6d346f9cef659854b91b7e0a4a3f388aa5cef016d6323f2c52
+  metadata.gz: 1d5eb8596c44c47d26f7d8954138ccff49880d0cfbbda9dd1669dd6d07e7c32f
+  data.tar.gz: 84aabd814e5ff1e723ff796ac4c02b37073c66f91695579dbdfe6850a44cfc6d
 SHA512:
-  metadata.gz: b04c921e57bb1fe74f9811d5e7cc9ba137600f9da55b906db3d51cc754533c7ed62f69bf9800172e07a2c4676a61bb13e0b939e12f25322c3065060a8c46d015
-  data.tar.gz: 870d7895ec05e62183f8958bae438b417b490df5c22d30f656a818d3e9c2747b8a16adb2f973bb0a6a36ac497ce4e725a7d2b139ece7ef1e96ac4171285673da
+  metadata.gz: c4158d767e170a0e18dcb1b9ad96558d2e13cd3ceed162c6e231d94cb1f99e8e62fe2da64be70fceeebf11ea1616af9c1da07c77469a9764e22ccaacb6c8da8d
+  data.tar.gz: aec89994b6c27b2109377959dd3ad1be1ca557bacadff21bf37df5c91760ac8f1e1e60eaf47f1be54997966c5b58090b70dd1154cba8431136836529bb8232ae

data/.github/STATUS.md

@@ -0,0 +1 @@
+# CI Status Update

data/.github/workflows/dummy.yml

@@ -21,7 +21,7 @@ jobs:
           persist-credentials: false
       - uses: actions/setup-node@v4
         with:
-          node-version: '16'
+          node-version: '20'
       - uses: ruby/setup-ruby@v1
         with:
           ruby-version: '3.1.2'

data/.github/workflows/generator.yml

@@ -20,8 +20,6 @@ jobs:
         os: [ubuntu-latest]
         ruby: ['2.7', '3.0', '3.1', '3.2', '3.3', '3.4']
         gemfile:
-          - gemfiles/Gemfile-rails.6.0.x
-          - gemfiles/Gemfile-rails.6.1.x
           - gemfiles/Gemfile-rails.7.0.x
           - gemfiles/Gemfile-rails.7.1.x
           - gemfiles/Gemfile-rails.7.2.x
@@ -38,20 +36,8 @@ jobs:
             gemfile: gemfiles/Gemfile-rails.7.2.x
           - ruby: '3.0'
             gemfile: gemfiles/Gemfile-rails.8.0.x
-          - ruby: '3.1'
-            gemfile: gemfiles/Gemfile-rails.6.0.x
           - ruby: '3.1'
             gemfile: gemfiles/Gemfile-rails.8.0.x
-          - ruby: '3.2'
-            gemfile: gemfiles/Gemfile-rails.6.0.x
-          - ruby: '3.3'
-            gemfile: gemfiles/Gemfile-rails.6.0.x
-          - ruby: '3.3'
-            gemfile: gemfiles/Gemfile-rails.6.1.x
-          - ruby: '3.4'
-            gemfile: gemfiles/Gemfile-rails.6.0.x
-          - ruby: '3.4'
-            gemfile: gemfiles/Gemfile-rails.6.1.x
           - ruby: '3.4'
             gemfile: gemfiles/Gemfile-rails.7.0.x
 
@@ -67,4 +53,8 @@ jobs:
           ruby-version: ${{ matrix.ruby }}
           rubygems: latest
           bundler-cache: true
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+          cache: yarn
       - run: bundle exec rake run_spec:generator

data/.github/workflows/node.yml

@@ -35,7 +35,7 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest]
-        node: [14.x, 16.x, 18.x, 20.x]
+        node: [18.x, 20.x, 22.x]
 
     runs-on: ${{ matrix.os }}
 

data/CHANGELOG.md

@@ -8,6 +8,21 @@
 ## [Unreleased]
 Changes since the last non-beta release.
 
+- Rspack support as an alternative bundler to webpack. Configure `bundler: 'rspack'` in `shakapacker.yml` to use Rspack's faster Rust-based bundling with webpack-compatible
+  APIs, built-in SWC loader, and CSS extraction. Automatic bundler detection in `bin/shakapacker` with fallback support for webpack configurations.
+
+## [v8.4.0] - September 8, 2025
+### Added
+
+* Support for subresource integrity. [PR 570](https://github.com/shakacode/shakapacker/pull/570) by [panagiotisplytas](https://github.com/panagiotisplytas)
+
+### Fixed
+
+- Install the latest major version of peer dependencies [PR 576](https://github.com/shakacode/shakapacker/pull/576) by [G-Rath](https://github.com/g-rath).
+- Remove duplicate word in comment from generated `shakapacker.yml` config [PR 572](https://github.com/shakacode/shakapacker/pull/572) by [G-Rath](https://github.com/g-rath).
+- fix: update webpack-dev-server to secure versions (^4.15.2 || ^5.2.2) [PR 585](https://github.com/shakacode/shakapacker/pull/585) by [justin808](https://github.com/justin808)
+
+
 ## [v8.3.0] - April 25, 2025
 ### Added
 
@@ -419,7 +434,8 @@ Note: [Rubygem is 6.3.0.pre.rc.1](https://rubygems.org/gems/shakapacker/versions
 ## v5.4.3 and prior changes from rails/webpacker
 See [CHANGELOG.md in rails/webpacker (up to v5.4.3)](https://github.com/rails/webpacker/blob/master/CHANGELOG.md)
 
-[Unreleased]: https://github.com/shakacode/shakapacker/compare/v8.3.0...main
+[Unreleased]: https://github.com/shakacode/shakapacker/compare/v8.4.0...main
+[v8.4.0]: https://github.com/shakacode/shakapacker/compare/v8.3.0...v8.4.0
 [v8.3.0]: https://github.com/shakacode/shakapacker/compare/v8.2.0...v8.3.0
 [v8.2.0]: https://github.com/shakacode/shakapacker/compare/v8.1.0...v8.2.0
 [v8.1.0]: https://github.com/shakacode/shakapacker/compare/v8.0.2...v8.1.0

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    shakapacker (8.3.0)
+    shakapacker (9.0.0.beta.0)
       activesupport (>= 5.2)
       package_json
       rack-proxy (>= 0.6.1)
@@ -217,7 +217,7 @@ GEM
       rubocop-ast (>= 1.31.1, < 2.0)
     ruby-progressbar (1.13.0)
     securerandom (0.3.1)
-    semantic_range (3.0.0)
+    semantic_range (3.1.0)
     stringio (3.1.1)
     thor (1.3.2)
     timeout (0.4.1)
@@ -248,4 +248,4 @@ DEPENDENCIES
   shakapacker!
 
 BUNDLED WITH
-   2.5.18
+   2.5.23

data/README.md

@@ -625,7 +625,7 @@ By default, you will find the Shakapacker preset in your `package.json`. Note, y
   ]
 },
 ```
-Optionally, you can change your Babel configuration by removing these lines in your `package.json` and adding [a Babel](https://babeljs.io/docs/en/config-files) configuration file](https://babeljs.io/docs/en/config-files) to your project. For an example of customization based on the original, see [Customizing Babel Config](./docs/customizing_babel_config.md).
+Optionally, you can change your Babel configuration by removing these lines in your `package.json` and adding [a Babel configuration file](https://babeljs.io/docs/en/config-files) to your project. For an example of customization based on the original, see [Customizing Babel Config](./docs/customizing_babel_config.md).
 
 
 ### SWC configuration
@@ -1018,8 +1018,8 @@ The following companies support our Open Source projects, and ShakaCode uses the
 <br />
 <br />
 
-<a href="https://www.jetbrains.com">
-  <img src="https://user-images.githubusercontent.com/4244251/184881139-42e4076b-024b-4b30-8c60-c3cd0e758c0a.png" alt="JetBrains" height="120px">
+<a href="https://jb.gg/OpenSource" style="margin-right: 20px;">
+  <img src="https://resources.jetbrains.com/storage/products/company/brand/logos/jetbrains.png" alt="JetBrains" height="120px">
 </a>
 <a href="https://scoutapp.com">
   <picture>

data/docs/css-modules-export-mode.md

@@ -0,0 +1,288 @@
+# CSS Modules Export Mode
+
+Most React guides and tutorials expect to import CSS Modules using a **default export object**:
+
+```js
+import styles from './Foo.module.css';
+<button className={styles.bright} />
+```
+
+However, depending on configuration, `css-loader` may instead emit **named exports**:
+
+```js
+import { bright } from './Foo.module.css';
+<button className={bright} />
+```
+
+By default, Shakapacker currently leaves `css-loader`'s `modules.namedExport` option unset, which leads to **named exports** being used in many cases. This can surprise developers expecting the `import styles ...` pattern.
+
+---
+
+## How to Configure Shakapacker for Default Exports
+
+To force the more familiar `import styles ...` behavior (i.e. `namedExport: false`), update your webpack configuration as follows.
+
+### Option 1: Update `config/webpack/commonWebpackConfig.js` (Recommended)
+
+This approach modifies the common webpack configuration that applies to all environments:
+
+```js
+// config/webpack/commonWebpackConfig.js
+const { generateWebpackConfig, merge } = require('shakapacker');
+
+const baseClientWebpackConfig = generateWebpackConfig();
+
+// Override CSS Modules configuration to use default exports instead of named exports
+const overrideCssModulesConfig = (config) => {
+  // Find the CSS rule in the module rules
+  const cssRule = config.module.rules.find(rule =>
+    rule.test && rule.test.toString().includes('css')
+  );
+
+  if (cssRule && cssRule.use) {
+    const cssLoaderUse = cssRule.use.find(use =>
+      use.loader && use.loader.includes('css-loader')
+    );
+
+    if (cssLoaderUse && cssLoaderUse.options && cssLoaderUse.options.modules) {
+      // Set namedExport to false for default export behavior
+      cssLoaderUse.options.modules.namedExport = false;
+      cssLoaderUse.options.modules.exportLocalsConvention = 'asIs';
+    }
+  }
+
+  return config;
+};
+
+const commonOptions = {
+  resolve: {
+    extensions: ['.css', '.ts', '.tsx'],
+  },
+};
+
+const commonWebpackConfig = () => {
+  const config = merge({}, baseClientWebpackConfig, commonOptions);
+  return overrideCssModulesConfig(config);
+};
+
+module.exports = commonWebpackConfig;
+```
+
+### Option 2: Create `config/webpack/environment.js` (Alternative)
+
+If you prefer using a separate environment file:
+
+```js
+// config/webpack/environment.js
+const { environment } = require('@shakacode/shakapacker');
+const getStyleRule = require('@shakacode/shakapacker/package/utils/getStyleRule');
+
+// CSS Modules rule for *.module.css with default export enabled
+const cssModulesRule = getStyleRule(/\.module\.css$/i, [], {
+  sourceMap: true,
+  importLoaders: 2,
+  modules: {
+    auto: true,
+    namedExport: false,            // <-- key: enable default export object
+    exportLocalsConvention: 'asIs' // keep your class names as-is
+  }
+});
+
+// Ensure this rule wins for *.module.css
+if (cssModulesRule) {
+  environment.loaders.prepend('css-modules', cssModulesRule);
+}
+
+// Plain CSS rule for non-modules
+const plainCssRule = getStyleRule(/(?<!\.module)\.css$/i, [], {
+  sourceMap: true,
+  importLoaders: 2,
+  modules: false
+});
+
+if (plainCssRule) {
+  environment.loaders.append('css', plainCssRule);
+}
+
+module.exports = environment;
+```
+
+Then reference this in your environment-specific configs (development.js, production.js, etc.).
+
+### Option 3: (Optional) Sass Modules
+
+If you also use Sass modules, add similar configuration for SCSS files:
+
+```js
+// For Option 1 approach, extend the overrideCssModulesConfig function:
+const overrideCssModulesConfig = (config) => {
+  // Handle both CSS and SCSS rules
+  const styleRules = config.module.rules.filter(rule =>
+    rule.test && (rule.test.toString().includes('css') || rule.test.toString().includes('scss'))
+  );
+
+  styleRules.forEach(rule => {
+    if (rule.use) {
+      const cssLoaderUse = rule.use.find(use =>
+        use.loader && use.loader.includes('css-loader')
+      );
+
+      if (cssLoaderUse && cssLoaderUse.options && cssLoaderUse.options.modules) {
+        cssLoaderUse.options.modules.namedExport = false;
+        cssLoaderUse.options.modules.exportLocalsConvention = 'asIs';
+      }
+    }
+  });
+
+  return config;
+};
+```
+
+---
+
+## Verifying the Configuration
+
+### 1. Rebuild Your Packs
+
+After making the configuration changes, rebuild your webpack bundles:
+
+```bash
+# For development
+NODE_ENV=development bin/shakapacker
+
+# Or with the dev server
+bin/shakapacker-dev-server
+```
+
+### 2. Test in Your React Component
+
+Update your component to use default imports:
+
+```js
+// Before (named exports)
+import { bright } from './Foo.module.css';
+
+// After (default export)
+import styles from './Foo.module.css';
+console.log(styles); // { bright: 'Foo_bright__hash' }
+```
+
+### 3. Debug Webpack Configuration (Optional)
+
+To inspect the final webpack configuration:
+
+```bash
+NODE_ENV=development bin/shakapacker --profile --json > /tmp/webpack-stats.json
+```
+
+Then search for `css-loader` options in the generated JSON file.
+
+---
+
+## Benefits of Default Export Approach
+
+1. **Better Developer Experience**: Matches most React tutorials and documentation
+2. **IDE Support**: Better autocomplete and IntelliSense for CSS class names
+3. **Type Safety**: Easier to add TypeScript definitions for CSS modules
+4. **Consistency**: Aligns with common React ecosystem practices
+
+---
+
+## Migration Guide
+
+If you're migrating from named exports to default exports:
+
+### 1. Update Import Statements
+
+```js
+// Old (named exports)
+import { bright, container, button } from './Component.module.css';
+
+// New (default export)
+import styles from './Component.module.css';
+```
+
+### 2. Update Class References
+
+```js
+// Old
+<div className={container}>
+  <button className={button}>Click me</button>
+  <span className={bright}>Highlighted text</span>
+</div>
+
+// New
+<div className={styles.container}>
+  <button className={styles.button}>Click me</button>
+  <span className={styles.bright}>Highlighted text</span>
+</div>
+```
+
+### 3. Consider Using a Codemod
+
+For large codebases, consider writing a codemod to automate the migration:
+
+```bash
+# Example using jscodeshift (pseudocode)
+npx jscodeshift -t css-modules-migration.js src/
+```
+
+---
+
+## Future Shakapacker Configuration
+
+In future versions of Shakapacker, this configuration may be exposed via `config/shakapacker.yml`:
+
+```yml
+# Future configuration (not yet implemented)
+css_modules:
+  # true  -> named exports (import { bright } ...)
+  # false -> default export (import styles ...)
+  named_export: false
+```
+
+- **Current behavior:** Uses named exports when unset
+- **Future behavior:** New app templates will default to `false`
+- **Next major release:** The default will change to `false` when unset
+
+---
+
+## Troubleshooting
+
+### CSS Classes Not Applying
+
+If your CSS classes aren't applying after the change:
+
+1. **Check import syntax**: Ensure you're using `import styles from ...`
+2. **Verify class names**: Use `console.log(styles)` to see available classes
+3. **Rebuild webpack**: Clear cache and rebuild: `rm -rf tmp/cache && bin/shakapacker`
+
+### TypeScript Support
+
+For TypeScript projects, create type definitions for your CSS modules:
+
+```typescript
+// src/types/css-modules.d.ts
+declare module '*.module.css' {
+  const classes: { [key: string]: string };
+  export default classes;
+}
+```
+
+### Build Performance
+
+The configuration changes should not impact build performance significantly. If you experience issues:
+
+1. Check webpack stats: `bin/shakapacker --profile`
+2. Verify only necessary rules are being modified
+3. Consider using webpack bundle analyzer for deeper insights
+
+---
+
+## Summary
+
+- **Current default**: Named exports (`import { bright } ...`)
+- **Recommended for DX**: Default export (`import styles ...`)
+- **Implementation**: Override CSS loader configuration in `commonWebpackConfig.js`
+- **Migration**: Update imports and class references systematically
+- **Future**: Shakapacker will provide native configuration options

data/docs/peer-dependencies.md

@@ -0,0 +1,40 @@
+# Shakapacker's Peer Dependencies
+#### last updated for our 8.4.0 version
+#### see lib/install/peerDependencies.json
+
+To simplify peer dependencies while supporting both webpack & rspack, we decided to document the dependencies here instead of creating two separate npm packages.
+
+## Essential for Rspack
+```
+    "@rspack/cli": "^1.0.0",
+    "@rspack/core": "^1.0.0",
+    "rspack-manifest-plugin": "^5.0.0",
+```
+## Essential for Webpack
+```
+    "mini-css-extract-plugin": "^2.0.0",
+    "terser-webpack-plugin": "^5.3.1",
+    "webpack": "^5.76.0",
+    "webpack-assets-manifest": "^5.0.6 || ^6.0.0",
+    "webpack-cli": "^4.9.2 || ^5.0.0 || ^6.0.0",
+    "webpack-dev-server": "^4.15.2 || ^5.2.2",
+    "webpack-merge": "^5.8.0 || ^6.0.0",
+    "webpack-subresource-integrity": "^5.1.0"
+```
+
+## Highly recommended
+```
+    "compression-webpack-plugin": "^9.0.0 || ^10.0.0|| ^11.0.0",
+    "css-loader": "^6.0.0 || ^7.0.0",
+    "sass-loader": "^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0",
+    "style-loader": "^3.0.0 || ^4.0.0",
+```
+
+## Babel (avoid if at all possible)
+```
+    "@babel/core": "^7.17.9",
+    "@babel/plugin-transform-runtime": "^7.17.0",
+    "@babel/preset-env": "^7.16.11",
+    "@babel/runtime": "^7.17.9",
+    "babel-loader": "^8.2.4 || ^9.0.0 || ^10.0.0",
+```

data/docs/react.md

@@ -61,11 +61,7 @@ const webpackConfig = generateWebpackConfig();
 
 if (isDevelopment && inliningCss) {
   webpackConfig.plugins.push(
-    new ReactRefreshWebpackPlugin({
-      overlay: {
-        sockPort: webpackConfig.devServer.port,
-      },
-    })
+    new ReactRefreshWebpackPlugin()
   );
 }
 
@@ -201,11 +197,7 @@ const webpackConfig = generateWebpackConfig();
 
 if (isDevelopment && inliningCss) {
   webpackConfig.plugins.push(
-    new ReactRefreshWebpackPlugin({
-      overlay: {
-        sockPort: webpackConfig.devServer.port,
-      },
-    })
+    new ReactRefreshWebpackPlugin()
   );
 }
 

data/docs/rspack.md

@@ -0,0 +1,190 @@
+# Rspack Integration
+
+Shakapacker supports [Rspack](https://rspack.rs) as an alternative bundler to Webpack. Rspack is a fast Rust-based web bundler with webpack-compatible API that can significantly speed up your build times.
+
+## Installation
+
+First, install the required Rspack dependencies:
+
+```bash
+npm install @rspack/core @rspack/cli -D
+# or
+yarn add @rspack/core @rspack/cli -D
+# or  
+pnpm add @rspack/core @rspack/cli -D
+# or
+bun add @rspack/core @rspack/cli -D
+```
+
+Note: These packages are already listed as optional peer dependencies in Shakapacker, so you may see warnings if they're not installed.
+
+## Configuration
+
+To enable Rspack, update your `config/shakapacker.yml`:
+
+```yaml
+default: &default
+  # ... other config options
+  bundler: 'rspack'  # Change from 'webpack' to 'rspack'
+```
+
+## Configuration
+
+Rspack uses its own configuration directory to keep things organized. Create your Rspack configuration file at `config/rspack/rspack.config.js`:
+
+```javascript
+const { generateRspackConfig } = require('shakapacker/rspack')
+
+module.exports = generateRspackConfig()
+```
+
+### Custom Configuration
+
+If you need to customize your Rspack configuration:
+
+```javascript
+const { generateRspackConfig } = require('shakapacker/rspack')
+
+const rspackConfig = generateRspackConfig({
+  plugins: [
+    new SomeRspackCompatiblePlugin()
+  ],
+  resolve: {
+    extensions: ['.ts', '.tsx', '.js', '.jsx']
+  }
+})
+
+module.exports = rspackConfig
+```
+
+### Migration from Webpack Config
+
+If you have an existing `config/webpack/webpack.config.js`, you can migrate it to `config/rspack/rspack.config.js`:
+
+**Old (webpack.config.js):**
+```javascript
+const { generateWebpackConfig } = require('shakapacker')
+module.exports = generateWebpackConfig()
+```
+
+**New (rspack.config.js):**
+```javascript
+const { generateRspackConfig } = require('shakapacker/rspack')
+module.exports = generateRspackConfig()
+```
+
+> **Note:** Shakapacker will show a deprecation warning if you use `config/webpack/webpack.config.js` with `bundler: 'rspack'`. Please migrate to `config/rspack/rspack.config.js`.
+
+## Key Differences from Webpack
+
+### Built-in Loaders
+
+Rspack has built-in loaders that are faster than their webpack counterparts:
+
+- **JavaScript/TypeScript**: Uses `builtin:swc-loader` instead of `babel-loader`
+- **CSS Extraction**: Uses `rspack.CssExtractRspackPlugin` instead of `mini-css-extract-plugin`
+- **Asset Handling**: Uses built-in asset modules instead of `file-loader`/`url-loader`
+
+### Plugin Compatibility
+
+Most webpack plugins work with Rspack, but some have Rspack-specific alternatives:
+
+| Webpack Plugin | Rspack Alternative | Status |
+|---|---|---|
+| `mini-css-extract-plugin` | `rspack.CssExtractRspackPlugin` | Built-in |
+| `copy-webpack-plugin` | `rspack.CopyRspackPlugin` | Built-in |
+| `terser-webpack-plugin` | `rspack.SwcJsMinimizerRspackPlugin` | Built-in |
+
+### Minification
+
+Rspack uses SWC for minification by default, which is significantly faster than Terser:
+
+```javascript
+optimization: {
+  minimize: true,
+  minimizer: [
+    new rspack.SwcJsMinimizerRspackPlugin(),
+    new rspack.SwcCssMinimizerRspackPlugin()
+  ]
+}
+```
+
+## Limitations
+
+- **CoffeeScript**: Not supported with Rspack
+- **Some Webpack Plugins**: May not be compatible; check Rspack documentation
+
+## Commands
+
+All existing Shakapacker commands work the same way and automatically use Rspack when configured:
+
+```bash
+# Build (automatically uses rspack when bundler: 'rspack')
+./bin/shakapacker
+
+# Development server (automatically uses rspack when bundler: 'rspack')  
+./bin/shakapacker-dev-server
+
+# Watch mode
+./bin/shakapacker --watch
+```
+
+The same dev server configuration in `shakapacker.yml` applies to both webpack and rspack.
+
+## Performance Benefits
+
+Rspack typically provides:
+
+- **2-10x faster** cold builds
+- **5-20x faster** incremental builds  
+- **Faster HMR** (Hot Module Replacement)
+- **Lower memory usage**
+
+## Migration Checklist
+
+1. **Install Rspack dependencies:**
+   ```bash
+   npm install @rspack/core @rspack/cli -D
+   ```
+
+2. **Update configuration:**
+   ```yaml
+   # config/shakapacker.yml
+   default: &default
+     bundler: 'rspack'
+   ```
+
+3. **Create Rspack config:**
+   ```javascript
+   // config/rspack/rspack.config.js
+   const { generateRspackConfig } = require('shakapacker/rspack')
+   module.exports = generateRspackConfig()
+   ```
+
+4. **Remove CoffeeScript files** (if any) - not supported by Rspack
+
+5. **Test your application** - same commands work automatically
+
+## Troubleshooting
+
+### Configuration Issues
+
+If you encounter configuration issues:
+
+1. Check that all plugins are Rspack-compatible
+2. Verify custom loaders work with Rspack
+3. Review the [Rspack migration guide](https://rspack.rs/guide/migration/webpack)
+
+### Performance Issues
+
+If builds are unexpectedly slow:
+
+1. Ensure you're using built-in Rspack loaders
+2. Check for webpack-specific plugins that should be replaced
+3. Review your asset optimization settings
+
+## Further Reading
+
+- [Rspack Official Documentation](https://rspack.rs)
+- [Rspack Migration Guide](https://rspack.rs/guide/migration/webpack)
+- [Rspack Plugins](https://rspack.rs/plugins/webpack/)