shakapacker 8.4.0 → 9.0.0.beta.2

data/docs/rspack.md

@@ -0,0 +1,190 @@
+# Rspack Integration
+
+Shakapacker supports [Rspack](https://rspack.rs) as an alternative assets 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
+  assets_bundler: 'rspack'  # Change from 'webpack' to 'rspack'
+```
+
+### Configuration Files
+
+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 `assets_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 assets_bundler: 'rspack')
+./bin/shakapacker
+
+# Development server (automatically uses rspack when assets_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
+     assets_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/)

data/docs/rspack_migration_guide.md

@@ -0,0 +1,202 @@
+# Rspack Migration Guide for Shakapacker
+
+## Overview
+This guide documents the differences between webpack and Rspack configurations in Shakapacker, and provides migration guidance for users switching to Rspack.
+
+## Key Differences from Webpack
+
+### 1. Built-in Loaders
+Rspack provides built-in loaders for better performance:
+
+**JavaScript/TypeScript:**
+- Use `builtin:swc-loader` instead of `babel-loader` or `ts-loader`
+- 20x faster than Babel on single thread, 70x on multiple cores
+- Configuration example:
+```javascript
+{
+  test: /\.(js|jsx|ts|tsx)$/,
+  loader: 'builtin:swc-loader',
+  options: {
+    jsc: {
+      parser: {
+        syntax: 'typescript', // or 'ecmascript'
+        tsx: true, // for TSX files
+        jsx: true  // for JSX files
+      },
+      transform: {
+        react: {
+          runtime: 'automatic'
+        }
+      }
+    }
+  }
+}
+```
+
+### 2. Plugin Replacements
+
+#### Built-in Rspack Alternatives
+| Webpack Plugin | Rspack Alternative | Status |
+|---------------|-------------------|---------|
+| `copy-webpack-plugin` | `rspack.CopyRspackPlugin` | ✅ Built-in |
+| `mini-css-extract-plugin` | `rspack.CssExtractRspackPlugin` | ✅ Built-in |
+| `terser-webpack-plugin` | `rspack.SwcJsMinimizerRspackPlugin` | ✅ Built-in |
+| `css-minimizer-webpack-plugin` | `rspack.LightningCssMinimizerRspackPlugin` | ✅ Built-in |
+
+#### Community Alternatives
+| Webpack Plugin | Rspack Alternative | Package |
+|---------------|-------------------|----------|
+| `fork-ts-checker-webpack-plugin` | `ts-checker-rspack-plugin` | `npm i -D ts-checker-rspack-plugin` |
+| `@pmmmwh/react-refresh-webpack-plugin` | `@rspack/plugin-react-refresh` | `npm i -D @rspack/plugin-react-refresh` |
+| `eslint-webpack-plugin` | `eslint-rspack-plugin` | `npm i -D eslint-rspack-plugin` |
+
+#### Incompatible Plugins
+The following webpack plugins are NOT compatible with Rspack:
+- `webpack.optimize.LimitChunkCountPlugin` - Use `optimization.splitChunks` configuration instead
+- `webpack-manifest-plugin` - Use `rspack-manifest-plugin` instead
+- Git revision plugins - Use alternative approaches
+
+### 3. Asset Module Types
+Replace file loaders with asset modules:
+- `file-loader` → `type: 'asset/resource'`
+- `url-loader` → `type: 'asset/inline'`
+- `raw-loader` → `type: 'asset/source'`
+
+### 4. Configuration Differences
+
+#### TypeScript Configuration
+**Required:** Add `isolatedModules: true` to your `tsconfig.json`:
+```json
+{
+  "compilerOptions": {
+    "isolatedModules": true
+  }
+}
+```
+
+#### React Fast Refresh
+```javascript
+// Development configuration
+const ReactRefreshPlugin = require('@rspack/plugin-react-refresh');
+
+module.exports = {
+  plugins: [
+    new ReactRefreshPlugin(),
+    new rspack.HotModuleReplacementPlugin()
+  ]
+};
+```
+
+### 5. Optimization Differences
+
+#### Code Splitting
+Rspack's `splitChunks` configuration is similar to webpack but with some differences:
+```javascript
+optimization: {
+  splitChunks: {
+    chunks: 'all',
+    cacheGroups: {
+      vendor: {
+        test: /[\\/]node_modules[\\/]/,
+        priority: -10,
+        reuseExistingChunk: true
+      }
+    }
+  }
+}
+```
+
+#### Minimization
+```javascript
+optimization: {
+  minimize: true,
+  minimizer: [
+    new rspack.SwcJsMinimizerRspackPlugin(),
+    new rspack.LightningCssMinimizerRspackPlugin()
+  ]
+}
+```
+
+### 6. Development Server
+Rspack uses its own dev server with some configuration differences:
+```javascript
+devServer: {
+  // Rspack-specific: Force writing assets to disk
+  devMiddleware: {
+    writeToDisk: true
+  }
+}
+```
+
+## Migration Checklist
+
+### Step 1: Update Dependencies
+```bash
+# Remove webpack dependencies
+npm uninstall webpack webpack-cli webpack-dev-server
+
+# Install Rspack
+npm install --save-dev @rspack/core @rspack/cli
+```
+
+### Step 2: Update Configuration Files
+1. Create `config/rspack/rspack.config.js` based on your webpack config
+2. Update `config/shakapacker.yml`:
+```yaml
+assets_bundler: 'rspack'
+```
+
+### Step 3: Replace Loaders
+- Replace `babel-loader` with `builtin:swc-loader`
+- Remove `file-loader`, `url-loader`, `raw-loader` - use asset modules
+- Update CSS loaders to use Rspack's built-in support
+
+### Step 4: Update Plugins
+- Replace plugins with Rspack alternatives (see table above)
+- Remove incompatible plugins
+- Add Rspack-specific plugins as needed
+
+### Step 5: TypeScript Setup
+1. Add `isolatedModules: true` to `tsconfig.json`
+2. Optional: Add `ts-checker-rspack-plugin` for type checking
+
+### Step 6: Test Your Build
+```bash
+# Development build
+bin/shakapacker
+
+# Production build
+bin/shakapacker --mode production
+```
+
+## Common Issues and Solutions
+
+### Issue: LimitChunkCountPlugin Error
+**Error:** `Cannot read properties of undefined (reading 'tap')`
+**Solution:** Remove `webpack.optimize.LimitChunkCountPlugin` and use `splitChunks` configuration instead.
+
+### Issue: Missing Loaders
+**Error:** Module parse errors
+**Solution:** Check console logs for skipped loaders and install missing dependencies.
+
+### Issue: CSS Extraction
+**Error:** CSS not being extracted properly
+**Solution:** Use `rspack.CssExtractRspackPlugin` instead of `mini-css-extract-plugin`.
+
+### Issue: TypeScript Errors
+**Error:** TypeScript compilation errors
+**Solution:** Ensure `isolatedModules: true` is set in `tsconfig.json`.
+
+## Performance Tips
+
+1. **Use Built-in Loaders:** Always prefer Rspack's built-in loaders for better performance
+2. **Minimize Plugins:** Use only necessary plugins as each adds overhead
+3. **Enable Caching:** Rspack has built-in persistent caching
+4. **Use SWC:** The built-in SWC loader is significantly faster than Babel
+
+## Resources
+
+- [Rspack Documentation](https://rspack.rs)
+- [Rspack Examples](https://github.com/rspack-contrib/rspack-examples)
+- [Awesome Rspack](https://github.com/rspack-contrib/awesome-rspack)
+- [Migration Guide](https://rspack.rs/guide/migration/webpack)

data/docs/troubleshooting.md

@@ -17,6 +17,11 @@
 
 4. You can also pass additional options to the command to run the webpack-dev-server and start the webpack-dev-server with the option `--debug-shakapacker`
 
+5. ChatGPT and other AI tools can consume this output file. Change the NODE_ENV per your needs. Then upload the file to your favorite AI tool.
+   ```
+   NODE_ENV=development bin/shakapacker --profile --json > /tmp/webpack-stats.json
+   ```
+
 ## Incorrect peer dependencies
 Shakapacker uses peer dependencies to make it easier to manage what versions are being used for your app, which is especially
 useful for patching security vulnerabilities. However, not all package managers will actually enforce these versions - notably,

data/docs/using_esbuild_loader.md

@@ -27,7 +27,7 @@ To use esbuild as your transpiler today. You need to do two things:
 npm install esbuild esbuild-loader
 ```
 
-2. Add or change `webpack_loader` value in your default `shakapacker.yml` config to `esbuild`
+2. Add or change `javascript_transpiler` value in your default `shakapacker.yml` config to `esbuild`
 The default configuration of babel is done by using `package.json` to use the file within the `shakapacker` package.
 
 ```yml
@@ -46,8 +46,8 @@ default: &default
   # Reload manifest.json on all requests so we reload latest compiled packs
   cache_manifest: false
 
-  # Select loader to use, available options are 'babel' (default), 'swc' or 'esbuild'
-  webpack_loader: 'esbuild'
+  # Select JavaScript transpiler to use, available options are 'babel' (default), 'swc' or 'esbuild'
+  javascript_transpiler: 'esbuild'
 ```
 
 ### (Optional) Replace minification with esbuild

data/docs/using_swc_loader.md

@@ -12,6 +12,8 @@ It supports all ECMAScript features and it's designed to be a drop-in replacemen
 
 For comparison between SWC and Babel, see the docs at https://swc.rs/docs/migrating-from-babel.
 
+> **Note:** SWC is also natively built into RSpack bundler, providing even faster compilation speeds. When using RSpack (`assets_bundler: 'rspack'`), SWC is used automatically regardless of the `javascript_transpiler` setting.
+
 ## Switching your Shakapacker project to SWC
 
 In order to use SWC as your compiler today. You need to do two things:
@@ -22,7 +24,7 @@ In order to use SWC as your compiler today. You need to do two things:
 npm install @swc/core swc-loader
 ```
 
-2. Add or change `webpack_loader` value in your default `shakapacker.yml` config to `swc`
+2. Add or change `javascript_transpiler` value in your default `shakapacker.yml` config to `swc`
 The default configuration of babel is done by using `package.json` to use the file within the `shakapacker` package.
 
 ```yml
@@ -41,8 +43,8 @@ default: &default
   # Reload manifest.json on all requests so we reload latest compiled packs
   cache_manifest: false
 
-  # Select loader to use, available options are 'babel' (default) or 'swc'
-  webpack_loader: 'swc'
+  # Select JavaScript transpiler to use, available options are 'babel' (default) or 'swc'
+  javascript_transpiler: 'swc'
 ```
 
 ## Usage

data/lib/install/bin/shakapacker

@@ -2,12 +2,10 @@
 
 ENV["RAILS_ENV"] ||= "development"
 ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile", __FILE__)
+ENV["APP_ROOT"] ||= File.expand_path("..", __dir__)
 
 require "bundler/setup"
 require "shakapacker"
-require "shakapacker/webpack_runner"
+require "shakapacker/runner"
 
-APP_ROOT = File.expand_path("..", __dir__)
-Dir.chdir(APP_ROOT) do
-  Shakapacker::WebpackRunner.run(ARGV)
-end
+Shakapacker::Runner.run(ARGV)

data/lib/install/config/rspack/rspack.config.js

@@ -0,0 +1,6 @@
+// See the shakacode/shakapacker README and docs directory for advice on customizing your rspackConfig.
+const { generateRspackConfig } = require('shakapacker/rspack')
+
+const rspackConfig = generateRspackConfig()
+
+module.exports = rspackConfig

data/lib/install/config/shakapacker.yml

@@ -36,8 +36,12 @@ default: &default
   # Reload manifest.json on all requests so we reload latest compiled packs
   cache_manifest: false
 
-  # Select loader to use, available options are 'babel' (default), 'swc' or 'esbuild'
-  webpack_loader: 'babel'
+  # Select JavaScript transpiler to use, available options are 'babel' (default), 'swc' or 'esbuild'
+  javascript_transpiler: 'babel'
+
+  # Select assets bundler to use
+  # Available options: 'webpack' (default) or 'rspack'
+  assets_bundler: 'webpack'
 
   # Raises an error if there is a mismatch in the shakapacker gem and npm package being used
   ensure_consistent_versioning: true

data/lib/install/package.json

@@ -0,0 +1,30 @@
+{
+  "rspack": {
+    "@rspack/cli": "^1.0.0",
+    "@rspack/core": "^1.0.0",
+    "rspack-manifest-plugin": "^5.0.0"
+  },
+  "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"
+  },
+  "common": {
+    "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": {
+    "@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/lib/install/template.rb

@@ -8,7 +8,6 @@ require "package_json"
 force_option = ENV["FORCE"] ? { force: true } : {}
 
 copy_file "#{__dir__}/config/shakapacker.yml", "config/shakapacker.yml", force_option
-remove_file "#{__dir__}/package.json" if force_option[:force]
 
 say "Copying webpack core config"
 directory "#{__dir__}/config/webpack", "config/webpack", force_option
@@ -112,7 +111,15 @@ rescue PackageJson::Error
 end
 
 def fetch_peer_dependencies
-  PackageJson.read("#{__dir__}/../../").fetch("peerDependencies")
+  PackageJson.read("#{__dir__}").fetch(ENV["SHAKAPACKER_BUNDLER"] || "webpack")
+end
+
+def fetch_common_dependencies
+  ENV["SKIP_COMMON_LOADERS"] ? {} : PackageJson.read("#{__dir__}").fetch("common")
+end
+
+def fetch_babel_dependencies
+  ENV["USE_BABEL_PACKAGES"] ? PackageJson.read("#{__dir__}").fetch("babel") : {}
 end
 
 Dir.chdir(Rails.root) do
@@ -130,6 +137,9 @@ Dir.chdir(Rails.root) do
   end
 
   peers = fetch_peer_dependencies
+  peers = peers.merge(fetch_common_dependencies)
+  peers = peers.merge(fetch_babel_dependencies)
+
   dev_dependency_packages = ["webpack-dev-server"]
 
   dependencies_to_add = []

data/lib/shakapacker/configuration.rb

@@ -88,6 +88,51 @@ class Shakapacker::Configuration
     fetch(:compiler_strategy)
   end
 
+  def assets_bundler
+    # Show deprecation warning if using old 'bundler' key
+    if data.has_key?(:bundler) && !data.has_key?(:assets_bundler)
+      $stderr.puts "⚠️  DEPRECATION WARNING: The 'bundler' configuration option is deprecated. Please use 'assets_bundler' instead to avoid confusion with Ruby's Bundler gem manager."
+    end
+    ENV["SHAKAPACKER_ASSETS_BUNDLER"] || fetch(:assets_bundler) || fetch(:bundler) || "webpack"
+  end
+
+  # Deprecated: Use assets_bundler instead
+  def bundler
+    assets_bundler
+  end
+
+  def rspack?
+    assets_bundler == "rspack"
+  end
+
+  def webpack?
+    assets_bundler == "webpack"
+  end
+
+  def javascript_transpiler
+    # Show deprecation warning if using old 'webpack_loader' key
+    if data.has_key?(:webpack_loader) && !data.has_key?(:javascript_transpiler)
+      $stderr.puts "⚠️  DEPRECATION WARNING: The 'webpack_loader' configuration option is deprecated. Please use 'javascript_transpiler' instead as it better reflects its purpose of configuring JavaScript transpilation regardless of the bundler used."
+    end
+
+    # Use explicit config if set, otherwise default based on bundler
+    fetch(:javascript_transpiler) || fetch(:webpack_loader) || default_javascript_transpiler
+  end
+
+  # Deprecated: Use javascript_transpiler instead
+  def webpack_loader
+    javascript_transpiler
+  end
+
+  private
+
+    def default_javascript_transpiler
+      # RSpack has built-in SWC support, use it by default
+      rspack? ? "swc" : "babel"
+    end
+
+  public
+
   def fetch(key)
     data.fetch(key, defaults[key])
   end

data/lib/shakapacker/dev_server_runner.rb

@@ -7,6 +7,10 @@ require_relative "runner"
 
 module Shakapacker
   class DevServerRunner < Shakapacker::Runner
+    def self.run(argv)
+      new(argv).run
+    end
+
     def run
       load_config
       detect_unsupported_switches!
@@ -75,12 +79,19 @@ module Shakapacker
           env["NODE_OPTIONS"] = "#{env["NODE_OPTIONS"]} --inspect-brk --trace-warnings"
         end
 
+        # Add config file
         cmd += ["--config", @webpack_config]
-        cmd += ["--progress", "--color"] if @pretty
 
-        # Default behavior of webpack-dev-server is @hot = true
-        cmd += ["--hot", "only"] if @hot == "only"
-        cmd += ["--no-hot"] if !@hot
+        # Add assets bundler-specific flags
+        if webpack?
+          cmd += ["--progress", "--color"] if @pretty
+          # Default behavior of webpack-dev-server is @hot = true
+          cmd += ["--hot", "only"] if @hot == "only"
+          cmd += ["--no-hot"] if !@hot
+        elsif rspack?
+          # Rspack supports --hot but not --no-hot or --progress/--color
+          cmd += ["--hot"] if @hot && @hot != false
+        end
 
         cmd += @argv
 
@@ -90,7 +101,16 @@ module Shakapacker
       end
 
       def build_cmd
-        package_json.manager.native_exec_command("webpack", ["serve"])
+        command = @config.rspack? ? "rspack" : "webpack"
+        package_json.manager.native_exec_command(command, ["serve"])
+      end
+
+      def webpack?
+        @config.webpack?
+      end
+
+      def rspack?
+        @config.rspack?
       end
   end
 end

data/lib/shakapacker/manifest.rb

@@ -108,15 +108,17 @@ class Shakapacker::Manifest
     end
 
     def missing_file_from_manifest_error(bundle_name)
+      bundler_name = config.assets_bundler
       <<-MSG
 Shakapacker can't find #{bundle_name} in #{config.manifest_path}. Possible causes:
 1. You forgot to install javascript packages or are running an incompatible javascript runtime version
 2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
 3. You have set compile: false (see `config/shakapacker.yml`) for this environment
    (unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
-4. webpack has not yet FINISHED running to reflect updates.
+4. Your #{bundler_name} has not yet FINISHED running to reflect updates.
 5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
-6. Your webpack configuration is not creating a manifest.
+6. Your #{bundler_name} configuration is not creating a manifest with the expected structure.
+7. Ensure the 'assets_bundler' in config/shakapacker.yml is set correctly (currently: #{bundler_name}).
 
 Your manifest contains:
 #{JSON.pretty_generate(@data)}