shakapacker 9.3.1 → 9.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 827667fa6e3a24bab59f3d9c2ef8404755b0deed67e1fce8ec62ada24e9b1a51
-  data.tar.gz: 06e18cd459b5e343601524ef2a1275ed0a86e6f842f63ef49d22e94fd7468ff2
+  metadata.gz: 0516b9d770d17a8e04f5b51e49f854823339760856dfd93a281586ea975513db
+  data.tar.gz: e0951145646eaeca52df5fc65aba8217e60de0ad0ea10de21271d6e7e62f7b6f
 SHA512:
-  metadata.gz: ccc98e916ba625cc386091668bad5737376f0d031758ce44124f8c3a45f463e8e9dbdc2e42c302387b3f1f074a075524e9856e01295cd73ea1efa7ebf3f40469
-  data.tar.gz: 5b256253fb6abd10007f861c6fc16a2a2500db40ca2a454cd75f8aeb89f83a13669394524cffb3cfffac6b490aa9a57f498358d3c57c0836d069072d208713eb
+  metadata.gz: 32963185a3ef79ffe8da898d800d9c014acc34854ad17dadb30243b5c46a6ae7caa74be034d1c9971048fab0809ba2caefae3ad82faa86d5684ed2dd46782a6c
+  data.tar.gz: 80f01b964e5df32104861c13a3e1924e497fa57f0201f4522417c407bc52bcf89e26315146d1e441fa5cd4a092994438aa2449ee95a07ba9c5c51eb6f48f830e

data/.claude/commands/update-changelog.md

@@ -109,50 +109,58 @@ When a new version is released:
 
 ### For Regular Changelog Updates
 
-1. **Determine the correct version tag to compare against**:
+1. **ALWAYS fetch latest changes first**:
+   - **CRITICAL**: Run `git fetch origin main` to ensure you have the latest commits
+   - The workspace may be behind origin/main, causing you to miss recently merged PRs
+   - After fetching, use `origin/main` for all comparisons, NOT local `main` branch
+
+2. **Determine the correct version tag to compare against**:
    - First, check the tag dates: `git log --tags --simplify-by-decoration --pretty="format:%ai %d" | head -10`
    - Find the latest version tag and its date
-   - Compare main branch date to the tag date
-   - If the tag is NEWER than main, it means main needs to be updated to include the tag's commits
+   - Compare origin/main branch date to the tag date
+   - If the tag is NEWER than origin/main, it means the branch needs to be updated to include the tag's commits
    - **CRITICAL**: Always use `git log TAG..BRANCH` to find commits that are in the tag but not in the branch, as the tag may be ahead
 
-2. **Check commits and version boundaries**:
-   - Run `git log --oneline LAST_TAG..main` to see commits since the last release
-   - Also check `git log --oneline main..LAST_TAG` to see if the tag is ahead of main
+3. **Check commits and version boundaries**:
+   - **IMPORTANT**: Use `origin/main` in all commands below, not local `main`
+   - Run `git log --oneline LAST_TAG..origin/main` to see commits since the last release
+   - Also check `git log --oneline origin/main..LAST_TAG` to see if the tag is ahead of origin/main
    - If the tag is ahead, entries in "Unreleased" section may actually belong to that tagged version
-   - Identify which commits contain user-visible changes
-   - Extract PR numbers and author information from commit messages
-   - **Never ask the user for PR details** - get them from the git history
+   - **Extract ALL PR numbers** from commit messages using grep: `git log --oneline LAST_TAG..origin/main | grep -oE "#[0-9]+" | sort -u`
+   - For each PR number found, check if it's already in CHANGELOG.md using: `grep "PR #XXX" CHANGELOG.md`
+   - Identify which commits contain user-visible changes (look for keywords like "Fix", "Add", "Feature", "Bug", etc.)
+   - Extract author information from commit messages
+   - **Never ask the user for PR details** - get them from the git history or use WebFetch on the PR URL
 
-3. **Validate** that changes are user-visible (per the criteria above). If not user-visible, skip those commits.
+4. **Validate** that changes are user-visible (per the criteria above). If not user-visible, skip those commits.
 
-4. **Read the current CHANGELOG.md** to understand the existing structure and formatting.
+5. **Read the current CHANGELOG.md** to understand the existing structure and formatting.
 
-5. **Determine where entries should go**:
-   - If the latest version tag is NEWER than main branch, move entries from "Unreleased" to that version section
-   - If main is ahead of the latest tag, add new entries to "Unreleased"
+6. **Determine where entries should go**:
+   - If the latest version tag is NEWER than origin/main branch, move entries from "Unreleased" to that version section
+   - If origin/main is ahead of the latest tag, add new entries to "Unreleased"
    - Always verify the version date in CHANGELOG.md matches the actual tag date
 
-6. **Add or move entries** to the appropriate section under appropriate category headings.
+7. **Add or move entries** to the appropriate section under appropriate category headings.
    - **CRITICAL**: When moving entries from "Unreleased" to a version section, merge them with existing entries under the same category heading
    - **NEVER create duplicate section headings** (e.g., don't create two "### Fixed" sections)
    - If the version section already has a category heading (e.g., "### Fixed"), add the moved entries to that existing section
    - Maintain the category order as defined above
 
-7. **Verify formatting**:
+8. **Verify formatting**:
    - Bold description with period
    - Proper PR link
    - Proper author link
    - Consistent with existing entries
    - File ends with a newline character
 
-8. **Run linting** after making changes:
+9. **Run linting** after making changes:
 
    ```bash
    yarn lint
    ```
 
-9. **Show the user** the added or moved entries and explain what was done.
+10. **Show the user** the added or moved entries and explain what was done.
 
 ### For Beta to Non-Beta Version Release
 

data/CHANGELOG.md

@@ -9,16 +9,23 @@
 
 ## [Unreleased]
 
+Changes since the last non-beta release.
+
 ### Fixed
 
-- Extended manifest merging for multiple client configurations to all environments. [PR #800](https://github.com/shakacode/shakapacker/pull/800) by [Judahmeek](https://github.com/Judahmeek).
+- Use `@ts-ignore` to suppress potential import error in public types when `webpack` is not installed. [PR #828](https://github.com/shakacode/shakapacker/pull/828) by [G-Rath]
 
-Changes since the last non-beta release.
+## [v9.3.1] - November 9, 2025
+
+### Fixed
+
+- **Fixed NODE_ENV not being set when running shakapacker-dev-server**. [PR #823](https://github.com/shakacode/shakapacker/pull/823) by [Seifeldin7](https://github.com/Seifeldin7). Resolves [#802](https://github.com/shakacode/shakapacker/issues/802). The dev server now properly initializes NODE_ENV to match RAILS_ENV (or "production" by default), fixing webpack configurations that dynamically load environment-specific files.
+- Extended manifest merging for multiple client configurations to all environments. [PR #800](https://github.com/shakacode/shakapacker/pull/800) by [Judahmeek](https://github.com/Judahmeek).
 
 ### Added
 
 - **Support for `css_modules_export_mode` configuration option**. [PR #817](https://github.com/shakacode/shakapacker/pull/817) by [justin808](https://github.com/justin808). Adds `css_modules_export_mode` setting in `shakapacker.yml` to control CSS Modules export style. Set to `"named"` (default, v9+ behavior with true named exports) or `"default"` (v8 behavior with default export object). Allows teams to opt into v8-style exports for easier migration from v8 or when using TypeScript with strict type checking.
-- **`Configuration#data` public API method** with enhanced documentation and safety. [PR #820](https://github.com/shakacode/shakapacker/pull/820) by [justin808](https://github.com/justin808). The `Configuration#data` method is now part of the public Ruby API, providing stable access to raw configuration data. Returns a frozen hash with symbolized keys to prevent accidental mutations. Includes comprehensive test coverage and detailed RDoc documentation.
+- **`Configuration#data` public API method** with enhanced documentation and safety. [PR #818](https://github.com/shakacode/shakapacker/pull/818) by [justin808](https://github.com/justin808). The `Configuration#data` method is now part of the public Ruby API, providing stable access to raw configuration data. Returns a frozen hash with symbolized keys to prevent accidental mutations. Includes comprehensive test coverage and detailed RDoc documentation.
 - **Support for `javascript_transpiler: 'none'`** for completely custom webpack configurations. [PR #799](https://github.com/shakacode/shakapacker/pull/799) by [justin808](https://github.com/justin808). Allows users with custom webpack configs to skip Shakapacker's transpiler setup and validation by setting `javascript_transpiler: 'none'` in `shakapacker.yml`. Useful when managing transpilation entirely outside of Shakapacker's defaults.
 
 ## [v9.3.0] - November 2, 2025
@@ -727,7 +734,8 @@ Note: [Rubygem is 6.3.0.pre.rc.1](https://rubygems.org/gems/shakapacker/versions
 
 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/v9.3.0...main
+[Unreleased]: https://github.com/shakacode/shakapacker/compare/v9.3.1...main
+[v9.3.1]: https://github.com/shakacode/shakapacker/compare/v9.3.0...v9.3.1
 [v9.3.0]: https://github.com/shakacode/shakapacker/compare/v9.2.0...v9.3.0
 [v9.2.0]: https://github.com/shakacode/shakapacker/compare/v9.1.0...v9.2.0
 [v9.1.0]: https://github.com/shakacode/shakapacker/compare/v9.0.0...v9.1.0

data/CONTRIBUTING.md

@@ -105,34 +105,21 @@ Shakapacker uses optional peer dependencies (via `peerDependenciesMeta`) for max
 
 ### TypeScript Declaration Files and Optional Dependencies
 
-When importing types from optional peer dependencies, we use `@ts-expect-error` directives:
+When importing types from optional peer dependencies, we use `@ts-ignore` directives:
 
 ```typescript
-// @ts-expect-error: webpack is an optional peer dependency (using type-only import)
+// @ts-ignore: webpack is an optional peer dependency (using type-only import)
 import type { Configuration } from "webpack"
 ```
 
-**Important behavior:**
-
-- **In development** (webpack installed): TypeScript doesn't error, but `@ts-expect-error` expects one → TypeScript compilation will fail
-- **In production** (webpack not installed): TypeScript errors on import, `@ts-expect-error` suppresses it → TypeScript compilation succeeds
-
-This is counterintuitive but correct. Our CI validates both scenarios to ensure the behavior works as expected.
-
-**Example scenario:**
-
-If webpack were changed from optional to required in `package.json`:
-
-- Development builds would fail with: `error TS2578: Unused '@ts-expect-error' directive`
-- This surfaces the dependency change immediately, preventing accidental breakage
-- The build failure prompts developers to remove the `@ts-expect-error` directive
+This ensures that typecheck downstream won't fail if lib checks are on regardless of if `webpack` is available.
 
 ### When modifying dependencies:
 
 1. Add new peer dependencies to both `peerDependencies` and `peerDependenciesMeta` (marking as optional)
 2. Keep version ranges synchronized between `devDependencies` and `peerDependencies`
 3. Test with multiple package managers: `npm`, `yarn`, and `pnpm`
-4. If adding type-only imports from optional dependencies, use the `@ts-expect-error` pattern shown above
+4. If adding type-only imports from optional dependencies, use the `@ts-ignore` pattern shown above
 
 ### Testing peer dependency changes:
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    shakapacker (9.3.1)
+    shakapacker (9.3.2)
       activesupport (>= 5.2)
       package_json
       rack-proxy (>= 0.6.1)

data/README.md

@@ -163,7 +163,7 @@ Then run the following to install Shakapacker:
 
 ```bash
 ./bin/bundle install
-./bin/rails shakapacker:install
+bundle exec rake shakapacker:install
 ```
 
 Before initiating the installation process, ensure you have committed all the changes. While installing Shakapacker, there might be some conflict between the existing file content and what Shakapacker tries to copy. You can either approve all the prompts for overriding these files or use the `FORCE=true` environment variable before the installation command to force the override without any prompt.
@@ -282,12 +282,10 @@ Depending on your setup, you'll need different subsets of the optional peer depe
 **Quick tip:** You can easily switch between webpack and rspack using:
 
 ```bash
-rails shakapacker:switch_bundler rspack --install-deps
-# or with rake (note the -- separator)
-rake shakapacker:switch_bundler rspack -- --install-deps
+bundle exec rake shakapacker:switch_bundler rspack -- --install-deps
 
 # For faster switching, use --no-uninstall to keep both bundlers installed
-rails shakapacker:switch_bundler webpack --install-deps --no-uninstall
+bundle exec rake shakapacker:switch_bundler webpack -- --install-deps --no-uninstall
 ```
 
 See the [Rspack Migration Guide](./docs/rspack_migration_guide.md) for details.
@@ -1117,13 +1115,13 @@ Otherwise, Shakapacker will use the production environment as a fallback environ
 For example, the below command will compile assets in production mode but will use staging configurations from `config/shakapacker.yml` if available or use fallback production environment configuration:
 
 ```bash
-RAILS_ENV=staging bundle exec rails assets:precompile
+RAILS_ENV=staging bundle exec rake assets:precompile
 ```
 
 And, this will compile in development mode and load configuration for the cucumber environment if defined in `shakapacker.yml` or fallback to production configuration
 
 ```bash
-RAILS_ENV=cucumber NODE_ENV=development bundle exec rails assets:precompile
+RAILS_ENV=cucumber NODE_ENV=development bundle exec rake assets:precompile
 ```
 
 Please note, binstubs compiles in development mode however rake tasks compiles in production mode.
@@ -1134,8 +1132,8 @@ Please note, binstubs compiles in development mode however rake tasks compiles i
 ./bin/shakapacker-dev-server
 
 # Compiles in production mode by default unless NODE_ENV is specified, per `lib/tasks/shakapacker/compile.rake`
-bundle exec rails assets:precompile
-bundle exec rails shakapacker:compile
+bundle exec rake assets:precompile
+bundle exec rake shakapacker:compile
 ```
 
 ### Upgrading
@@ -1147,7 +1145,7 @@ You can run the following commands to upgrade Shakapacker to the latest stable v
 bundle update shakapacker
 
 # overwrite your changes to the default install files and revert any unwanted changes from the install
-rails shakapacker:install
+bundle exec rake shakapacker:install
 
 # using npm
 npm install shakapacker@latest
@@ -1294,7 +1292,7 @@ For detailed CDN setup instructions, including CloudFlare configuration, trouble
 
 ```bash
 export SHAKAPACKER_ASSET_HOST=https://cdn.example.com
-RAILS_ENV=production bundle exec rails assets:precompile
+RAILS_ENV=production bundle exec rake assets:precompile
 ```
 
 For more deployment documentation, see [Deployment](./docs/deployment.md).
@@ -1348,3 +1346,10 @@ The following companies support our Open Source projects, and ShakaCode uses the
 <a href="https://www.honeybadger.io">
   <img src="https://user-images.githubusercontent.com/4244251/184881133-79ee9c3c-8165-4852-958e-31687b9536f4.png" alt="Honeybadger" height="55px">
 </a>
+<a href="https://coderabbit.ai">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://victorious-bubble-f69a016683.media.strapiapp.com/White_Typemark_7229870ac5.svg">
+    <source media="(prefers-color-scheme: light)" srcset="https://victorious-bubble-f69a016683.media.strapiapp.com/Orange_Typemark_7958cfa790.svg">
+    <img alt="CodeRabbit" src="https://victorious-bubble-f69a016683.media.strapiapp.com/Orange_Typemark_7958cfa790.svg" height="55px">
+  </picture>
+</a>

data/docs/cdn_setup.md

@@ -91,7 +91,7 @@ During deployment, compile your assets as usual:
 ```bash
 # The SHAKAPACKER_ASSET_HOST will be used during compilation
 # to set the webpack publicPath
-RAILS_ENV=production bundle exec rails assets:precompile
+RAILS_ENV=production bundle exec rake assets:precompile
 ```
 
 This ensures that:
@@ -204,7 +204,7 @@ import("./components/HeavyComponent").then((module) => {
 **Solutions**:
 
 1. Ensure you set `SHAKAPACKER_ASSET_HOST` **before** running `assets:precompile`
-2. Clear Rails cache: `rails tmp:cache:clear`
+2. Clear Rails cache: `bundle exec rake tmp:cache:clear`
 3. Check the manifest.json file includes CDN URLs:
    ```bash
    cat public/packs/manifest.json
@@ -369,7 +369,7 @@ end
 ```bash
 # Deployment script
 export SHAKAPACKER_ASSET_HOST=https://cdn.example.com
-RAILS_ENV=production bundle exec rails assets:precompile
+RAILS_ENV=production bundle exec rake assets:precompile
 ```
 
 ## Summary

data/docs/common-upgrades.md

@@ -411,16 +411,15 @@ bin/shakapacker compile
 Shakapacker provides a convenient rake task to automate the migration:
 
 ```bash
-# Switch to rspack with automatic dependency management
-rails shakapacker:switch_bundler rspack --install-deps
-
-# Or with rake (note the -- separator)
-rake shakapacker:switch_bundler rspack -- --install-deps
+# Switch to rspack with automatic dependency management (note the -- separator)
+bin/rake shakapacker:switch_bundler rspack -- --install-deps
 
 # Fast switching without uninstalling webpack (keeps both)
-rails shakapacker:switch_bundler rspack --install-deps --no-uninstall
+bin/rake shakapacker:switch_bundler rspack -- --install-deps --no-uninstall
 ```
 
+> **⚠️ Important:** This task must be run with `bin/rake`, not `bin/rails`.
+
 The task will:
 
 - Update `config/shakapacker.yml` to use rspack
@@ -432,7 +431,7 @@ The task will:
 **Custom dependencies:** You can customize which dependencies are installed:
 
 ```bash
-rails shakapacker:switch_bundler --init-config
+bin/rake shakapacker:switch_bundler -- --init-config
 ```
 
 #### 2. Manual installation (alternative)

data/docs/configuration.md

@@ -36,7 +36,7 @@ Common configuration options with their defaults:
 | `compiler_strategy`            | string  | `"mtime"` (dev), `"digest"` (prod)      | How to determine if recompilation is needed                |
 | `useContentHash`               | boolean | `false` (dev), `true` (prod)            | Include content hashes in asset filenames                  |
 | `webpack_compile_output`       | boolean | `true`                                  | Show webpack/rspack compilation output                     |
-| `shakapacker_precompile`       | boolean | `true`                                  | Include in `rails assets:precompile`                       |
+| `shakapacker_precompile`       | boolean | `true`                                  | Include in `bundle exec rake assets:precompile`            |
 | `ensure_consistent_versioning` | boolean | `true`                                  | Enforce gem/npm version matching                           |
 | `dev_server.host`              | string  | `"localhost"`                           | Development server host                                    |
 | `dev_server.port`              | number  | `3035`                                  | Development server port                                    |
@@ -401,7 +401,7 @@ production:
 **Type:** `boolean`
 **Default:** `true`
 
-Whether `rails assets:precompile` should compile webpack/rspack assets.
+Whether `bundle exec rake assets:precompile` should compile webpack/rspack assets.
 
 ```yaml
 # Include in assets:precompile (recommended)
@@ -414,7 +414,7 @@ shakapacker_precompile: false
 **Override via environment variable:**
 
 ```bash
-SHAKAPACKER_PRECOMPILE=false rails assets:precompile
+SHAKAPACKER_PRECOMPILE=false bundle exec rake assets:precompile
 ```
 
 ### `cache_manifest`

data/docs/deployment.md

@@ -16,7 +16,7 @@ Quick example for production deployment:
 ```yaml
 # config/shakapacker.yml
 production:
-  precompile_hook: "bin/rails react_on_rails:generate_packs"
+  precompile_hook: "bin/rake react_on_rails:generate_packs"
 ```
 
 This ensures your dynamic entry points are generated before `assets:precompile` runs.
@@ -56,7 +56,7 @@ Your production build process is responsible for installing your JavaScript depe
 RAILS_ENV=staging bin/shakapacker
 
 # Also works with rake task
-RAILS_ENV=staging bundle exec rails assets:precompile
+RAILS_ENV=staging bundle exec rake assets:precompile
 ```
 
 **How it works:**
@@ -156,7 +156,7 @@ Shakapacker supports serving JavaScript bundles and assets from a CDN. For a com
 
 ```bash
 export SHAKAPACKER_ASSET_HOST=https://cdn.example.com
-RAILS_ENV=production bundle exec rails assets:precompile
+RAILS_ENV=production bundle exec rake assets:precompile
 ```
 
 Note: Shakapacker does NOT use the `ASSET_HOST` environment variable. You must use `SHAKAPACKER_ASSET_HOST` instead (`WEBPACKER_ASSET_HOST` if using Shakapacker before v7).

data/docs/early_hints_manual_api.md

@@ -399,7 +399,7 @@ development: # or production
 bundle exec puma --early-hints
 
 # Option 2: Test in production mode locally (more realistic)
-RAILS_ENV=production rails assets:precompile  # Compile assets first
+RAILS_ENV=production bundle exec rake assets:precompile  # Compile assets first
 RAILS_ENV=production bundle exec puma --early-hints -e production
 ```
 

data/docs/feature_testing.md

@@ -434,7 +434,7 @@ curl http://localhost:3035/packs/application.js
 
 Use this checklist to verify a complete Shakapacker setup:
 
-- [ ] **Assets compile:** `bundle exec rails assets:precompile` succeeds
+- [ ] **Assets compile:** `bundle exec rake assets:precompile` succeeds
 - [ ] **Manifest exists:** `public/packs/manifest.json` contains entrypoints
 - [ ] **Assets load:** Page loads without 404s for pack files
 - [ ] **Code splitting works:** Multiple chunks load in Network tab
@@ -456,7 +456,7 @@ cat public/packs/manifest.json | jq .
 **Recompile:**
 
 ```bash
-bundle exec rails assets:precompile
+bundle exec rake assets:precompile
 ```
 
 ### Old Assets Cached
@@ -465,7 +465,7 @@ bundle exec rails assets:precompile
 
 ```bash
 rm -rf public/packs
-bundle exec rails assets:precompile
+bundle exec rake assets:precompile
 ```
 
 ### Dev Server Won't Start

data/docs/optional-peer-dependencies.md

@@ -102,7 +102,7 @@ If upgrading from Shakapacker v8:
 
 ### New Installations
 
-The installer (`rails shakapacker:install`) only adds packages needed for your configuration:
+The installer (`bundle exec rake shakapacker:install`) only adds packages needed for your configuration:
 
 - Detects your preferred bundler (webpack/rspack)
 - Installs appropriate JavaScript transpiler (babel/swc/esbuild)
@@ -159,7 +159,7 @@ The test suite includes:
 
 1. Check you've installed required dependencies for your configuration
 2. Refer to the configuration examples above
-3. Run `rails shakapacker:doctor` for diagnostics
+3. Run `bundle exec rake shakapacker:doctor` for diagnostics
 
 ### TypeScript errors?
 

data/docs/precompile_hook.md

@@ -14,14 +14,14 @@ This is useful for:
 
 The precompile hook is especially useful when you need to run commands like:
 
-- `bin/rails react_on_rails:generate_packs` - Generate dynamic entry points
-- `bin/rails react_on_rails:locale` - Generate locale files
+- `bin/rake react_on_rails:generate_packs` - Generate dynamic entry points
+- `bin/rake react_on_rails:locale` - Generate locale files
 - Any custom script that prepares files before asset compilation
 
 **Important:** The hook runs in **both development and production**:
 
 - **Development**: Runs before `bin/shakapacker --watch` or dev server starts
-- **Production**: Runs before `rails assets:precompile`
+- **Production**: Runs before `bundle exec rake assets:precompile`
 
 ## Configuration
 
@@ -39,7 +39,7 @@ development:
 
 production:
   <<: *default
-  precompile_hook: "bin/rails react_on_rails:generate_packs"
+  precompile_hook: "rake react_on_rails:generate_packs"
 ```
 
 ## Creating a Precompile Hook Script
@@ -51,8 +51,8 @@ production:
 # bin/shakapacker-precompile-hook
 
 echo "Preparing assets..."
-bin/rails react_on_rails:generate_packs
-bin/rails react_on_rails:locale
+bundle exec rake react_on_rails:generate_packs
+bundle exec rake react_on_rails:locale
 echo "Assets prepared successfully"
 ```
 
@@ -117,14 +117,14 @@ For React on Rails projects, the hook replaces manual steps in your workflow:
 
 ```bash
 # Development
-bin/rails react_on_rails:generate_packs
-bin/rails react_on_rails:locale
+bundle exec rake react_on_rails:generate_packs
+bundle exec rake react_on_rails:locale
 bin/shakapacker-dev-server
 
 # Production
-bin/rails react_on_rails:generate_packs
-bin/rails react_on_rails:locale
-RAILS_ENV=production bin/rails assets:precompile
+bundle exec rake react_on_rails:generate_packs
+bundle exec rake react_on_rails:locale
+RAILS_ENV=production rake assets:precompile
 ```
 
 ### After (Automatic)
@@ -138,8 +138,8 @@ default: &default
 ```bash
 #!/usr/bin/env bash
 # bin/react-on-rails-hook
-bin/rails react_on_rails:generate_packs
-bin/rails react_on_rails:locale
+bundle exec rake react_on_rails:generate_packs
+bundle exec rake react_on_rails:locale
 ```
 
 Now simply run:
@@ -149,7 +149,7 @@ Now simply run:
 bin/shakapacker-dev-server
 
 # Production
-RAILS_ENV=production bin/rails assets:precompile
+RAILS_ENV=production bin/rake assets:precompile
 ```
 
 ## Security
@@ -292,7 +292,7 @@ default:
 
 if [ "$RAILS_ENV" = "production" ]; then
   echo "Running production-specific setup..."
-  bin/rails react_on_rails:generate_packs
+  bin/rake react_on_rails:generate_packs
 else
   echo "Running development setup..."
   # Lighter-weight setup for development

data/docs/react.md

@@ -132,7 +132,7 @@ rails new myapp --skip-javascript
 cd myapp
 bundle add shakapacker --strict
 ./bin/bundle install
-./bin/rails shakapacker:install
+bundle exec rake shakapacker:install
 npm install react react-dom @babel/preset-react
 npm install css-loader style-loader mini-css-extract-plugin css-minimizer-webpack-plugin
 ```

data/docs/releasing.md

@@ -36,16 +36,16 @@ The automated release task handles the entire release process:
 
 ```bash
 # For a specific version (e.g., 9.1.0)
-rake create_release[9.1.0]
+bundle exec rake create_release[9.1.0]
 
 # For a beta release (note: use period, not dash)
-rake create_release[9.2.0.beta.1]  # Creates npm package 9.2.0-beta.1
+bundle exec rake create_release[9.2.0.beta.1]  # Creates npm package 9.2.0-beta.1
 
 # For a patch version bump (auto-increments)
-rake create_release
+bundle exec rake create_release
 
 # Dry run to test without publishing
-rake create_release[9.1.0,true]
+bundle exec rake create_release[9.1.0,true]
 ```
 
 ### 3. What the Release Task Does
@@ -83,13 +83,13 @@ The task automatically converts Ruby gem format to npm semver format:
 
 ```bash
 # Regular release
-rake create_release[9.1.0]  # Gem: 9.1.0, npm: 9.1.0
+bundle exec rake create_release[9.1.0]  # Gem: 9.1.0, npm: 9.1.0
 
 # Beta release
-rake create_release[9.2.0.beta.1]  # Gem: 9.2.0.beta.1, npm: 9.2.0-beta.1
+bundle exec rake create_release[9.2.0.beta.1]  # Gem: 9.2.0.beta.1, npm: 9.2.0-beta.1
 
 # Release candidate
-rake create_release[10.0.0.rc.1]  # Gem: 10.0.0.rc.1, npm: 10.0.0-rc.1
+bundle exec rake create_release[10.0.0.rc.1]  # Gem: 10.0.0.rc.1, npm: 10.0.0-rc.1
 ```
 
 ### 5. During the Release

data/docs/rspack_migration_guide.md

@@ -212,28 +212,22 @@ Shakapacker provides a convenient rake task to switch between webpack and rspack
 
 ```bash
 # Switch to rspack with automatic dependency management
-rails shakapacker:switch_bundler rspack --install-deps
-# or with rake (note the -- separator)
-rake shakapacker:switch_bundler rspack -- --install-deps
+bin/rake shakapacker:switch_bundler rspack -- --install-deps
 
 # Fast switching without uninstalling old bundler (keeps both)
-rails shakapacker:switch_bundler webpack --install-deps --no-uninstall
-rake shakapacker:switch_bundler rspack -- --install-deps --no-uninstall
+bin/rake shakapacker:switch_bundler rspack -- --install-deps --no-uninstall
 
 # Switch to rspack manually (you manage dependencies yourself)
-rails shakapacker:switch_bundler rspack
-rake shakapacker:switch_bundler rspack
+bin/rake shakapacker:switch_bundler rspack
 
 # Switch back to webpack if needed
-rails shakapacker:switch_bundler webpack --install-deps
-rake shakapacker:switch_bundler webpack -- --install-deps
+bin/rake shakapacker:switch_bundler webpack -- --install-deps
 
 # Show help
-rails shakapacker:switch_bundler --help
-rake shakapacker:switch_bundler -- --help
+bin/rake shakapacker:switch_bundler -- --help
 ```
 
-**Note:** When using `rake`, you must use `--` to separate rake options from task arguments.
+> **⚠️ Important:** This task must be run with `bin/rake`, not `bin/rails`.
 
 The task will:
 
@@ -246,7 +240,7 @@ The task will:
 **Custom Dependencies:** You can customize which dependencies are installed by creating a `.shakapacker-switch-bundler-dependencies.yml` file:
 
 ```bash
-rails shakapacker:switch_bundler --init-config
+bundle exec rake shakapacker:switch_bundler --init-config
 ```
 
 ### Manual Migration Steps
@@ -840,7 +834,7 @@ To compare your webpack and rspack configurations during migration:
 bin/shakapacker-config --doctor
 
 # Switch to rspack
-rails shakapacker:switch_bundler rspack --install-deps
+bundle exec rake shakapacker:switch_bundler rspack --install-deps
 
 # Export rspack configs to compare
 bin/shakapacker-config --doctor

data/docs/troubleshooting.md

@@ -280,7 +280,7 @@ See the [deployment guide](./deployment.md#custom-rails-environments-eg-staging)
 ## ENOENT: no such file or directory - node-sass
 
 If you get the error `ENOENT: no such file or directory - node-sass` on deploy with
-`assets:precompile` or `bundle exec rails shakapacker:compile` you may need to
+`assets:precompile` or `bundle exec rake shakapacker:compile` you may need to
 move Sass to production `dependencies`.
 
 Move any packages that related to Sass (e.g. `node-sass` or `sass-loader`) from
@@ -326,13 +326,13 @@ In `package.json`:
 
 ## webpack or webpack-dev-server not found
 
-- This could happen if `shakapacker:install` step is skipped. Please run `bundle exec rails shakapacker:install` to fix the issue.
+- This could happen if `shakapacker:install` step is skipped. Please run `bundle exec rake shakapacker:install` to fix the issue.
 
 - If you encounter the above error on heroku after upgrading from Rails 4.x to 5.1.x, then the problem might be related to missing `yarn` binstub. Please run following commands to update/add binstubs:
 
 ```bash
 bundle config --delete bin
-./bin/rails app:update:bin # or rails app:update:bin
+bundle exec rake app:update:bin
 ```
 
 ## Running webpack on Windows