shakapacker 9.0.0.beta.0 → 9.0.0.beta.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1d5eb8596c44c47d26f7d8954138ccff49880d0cfbbda9dd1669dd6d07e7c32f
-  data.tar.gz: 84aabd814e5ff1e723ff796ac4c02b37073c66f91695579dbdfe6850a44cfc6d
+  metadata.gz: 402395e802e7a185fd12d12e18a766cb4adcf87b1b04286a7e2c47bfec83a40d
+  data.tar.gz: 1364c179704bed61e68bf95583331059018b6c46b07681b00f288e4a7b2debd6
 SHA512:
-  metadata.gz: c4158d767e170a0e18dcb1b9ad96558d2e13cd3ceed162c6e231d94cb1f99e8e62fe2da64be70fceeebf11ea1616af9c1da07c77469a9764e22ccaacb6c8da8d
-  data.tar.gz: aec89994b6c27b2109377959dd3ad1be1ca557bacadff21bf37df5c91760ac8f1e1e60eaf47f1be54997966c5b58090b70dd1154cba8431136836529bb8232ae
+  metadata.gz: 8cbcc1fe7b7a4a8440f5513e099480c376e3382c51fef3afde2f48929148090ae8d4c51c56dd009025f63fd0f4ec54c53eaa1f00fda9dc6851fb0e7ab3a1b56a
+  data.tar.gz: e642ec8b91aee622052ff52c7038f074b140aade21130af222311c47137382675a0c536b2a8134d03a4678480946696d9a417c5b8233d344d28f44795bba6431

data/.github/workflows/claude-code-review.yml

@@ -0,0 +1,54 @@
+name: Claude Code Review
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+    # Optional: Only run on specific file changes
+    # paths:
+    #   - "src/**/*.ts"
+    #   - "src/**/*.tsx"
+    #   - "src/**/*.js"
+    #   - "src/**/*.jsx"
+
+jobs:
+  claude-review:
+    # Optional: Filter by PR author
+    # if: |
+    #   github.event.pull_request.user.login == 'external-contributor' ||
+    #   github.event.pull_request.user.login == 'new-developer' ||
+    #   github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
+    
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          prompt: |
+            Please review this pull request and provide feedback on:
+            - Code quality and best practices
+            - Potential bugs or issues
+            - Performance considerations
+            - Security concerns
+            - Test coverage
+            
+            Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
+
+            Use `gh pr comment` with your Bash tool to leave your review as a comment on the PR.
+          
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://docs.claude.com/en/docs/claude-code/sdk#command-line for available options
+          claude_args: '--allowed-tools "Bash(gh issue view:*),Bash(gh search:*),Bash(gh issue list:*),Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh pr list:*)"'
+

data/.github/workflows/claude.yml

@@ -0,0 +1,50 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          
+          # This is an optional setting that allows Claude to read CI results on PRs
+          additional_permissions: |
+            actions: read
+
+          # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
+          # prompt: 'Update the pull request description to include a summary of changes.'
+
+          # Optional: Add claude_args to customize behavior and configuration
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://docs.claude.com/en/docs/claude-code/sdk#command-line for available options
+          # claude_args: '--model claude-opus-4-1-20250805 --allowed-tools Bash(gh pr:*)'
+

data/.github/workflows/dummy.yml

@@ -24,13 +24,13 @@ jobs:
           node-version: '20'
       - uses: ruby/setup-ruby@v1
         with:
-          ruby-version: '3.1.2'
+          ruby-version: '3.2'
           rubygems: latest
       - name: Install dependencies
         run: |
           bundle install
-          yarn install
-          sudo yarn global add yalc
+          npm install -g yalc
+          cd spec/dummy && npm install
 
       - name: Run tests
         run: bundle exec rake run_spec:dummy

data/.github/workflows/test-bundlers.yml

@@ -0,0 +1,152 @@
+name: Test Both Bundlers
+
+on:
+  pull_request:
+  push:
+    branches: [master, main]
+
+jobs:
+  test-webpack:
+    name: Test with Webpack
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: spec/dummy
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.2'
+          bundler-cache: true
+          working-directory: spec/dummy
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: spec/dummy/package-lock.json
+
+      - name: Install yalc
+        run: npm install -g yalc
+
+      - name: Publish shakapacker to yalc
+        run: |
+          cd ../..
+          yalc publish
+
+      - name: Install dependencies
+        run: |
+          yalc link shakapacker
+          npm ci
+
+      - name: Switch to Webpack
+        run: bin/test-bundler webpack
+
+      - name: Build with Webpack
+        run: bin/shakapacker
+
+      - name: Run tests with Webpack
+        run: |
+          bundle exec rspec
+
+  test-rspack:
+    name: Test with RSpack
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: spec/dummy
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.2'
+          bundler-cache: true
+          working-directory: spec/dummy
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: spec/dummy/package-lock.json
+
+      - name: Install yalc
+        run: npm install -g yalc
+
+      - name: Publish shakapacker to yalc
+        run: |
+          cd ../..
+          yalc publish
+
+      - name: Install dependencies
+        run: |
+          yalc link shakapacker
+          npm ci
+
+      - name: Switch to RSpack
+        run: bin/test-bundler rspack
+
+      - name: Build with RSpack
+        run: bin/shakapacker
+
+      - name: Run tests with RSpack
+        run: |
+          bundle exec rspec
+
+  test-switching:
+    name: Test Bundler Switching
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: spec/dummy
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.2'
+          bundler-cache: true
+          working-directory: spec/dummy
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: spec/dummy/package-lock.json
+
+      - name: Install yalc
+        run: npm install -g yalc
+
+      - name: Publish shakapacker to yalc
+        run: |
+          cd ../..
+          yalc publish
+
+      - name: Install dependencies
+        run: |
+          yalc link shakapacker
+          npm ci
+
+      - name: Test switching between bundlers
+        run: |
+          # Start with webpack
+          bin/test-bundler webpack
+          bin/shakapacker
+
+          # Switch to rspack
+          bin/test-bundler rspack
+          bin/shakapacker
+
+          # Switch back to webpack
+          bin/test-bundler webpack
+          bin/shakapacker

data/.rubocop.yml

@@ -9,6 +9,7 @@ AllCops:
     - "vendor/**/*"
     - "node_modules/**/*"
     - "_actions/**/*"
+    - "spec/dummy-rspack/**/*"
 
 # Prefer &&/|| over and/or.
 Style/AndOr:

data/CHANGELOG.md

@@ -1,4 +1,5 @@
 * For the changelog of versions prior to v6, see the [5.x stable branch of rails/webpacker](https://github.com/rails/webpacker/tree/5-x-stable).
+* **Please see the [v9 Upgrade Guide](./docs/v9_upgrade.md) for upgrading to version 9 and accounting for breaking changes.**
 * Please see the [v8 Upgrade Guide](./docs/v8_upgrade.md) for upgrading to version 8 and accounting for breaking changes.
 * Please see the [v7 Upgrade Guide](./docs/v7_upgrade.md) for upgrading to new spelling in version 7.
 * Please see the [v6 Upgrade Guide](./docs/v6_upgrade.md) to go from versions prior to v6.
@@ -8,10 +9,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.
+### Added
+- Rspack support as an alternative assets bundler to webpack. Configure `assets_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 assets bundler detection in `bin/shakapacker` with fallback support for webpack configurations.
+- Add `private_output_path` configuration option for server-side rendering bundles. This allows specifying a separate output directory for private server bundles that shouldn't be served publicly. [PR 592](https://github.com/shakacode/shakapacker/pull/592) by [justin808](https://github.com/justin808).
+- Enhanced TypeScript type definitions for better IDE support and type safety. Improved Config and DevServerConfig interfaces with additional properties. [PR 602](https://github.com/shakacode/shakapacker/pull/602) by [justin808](https://github.com/justin808).
 
-## [v8.4.0] - September 8, 2025
+### Changed
+- Configuration option renamed from `bundler` to `assets_bundler` to avoid confusion with Ruby's Bundler gem manager. The old `bundler` option is deprecated but still supported with a warning (not a breaking change).
+- BREAKING CHANGE: Configuration option renamed from `webpack_loader` to `javascript_transpiler` to better reflect its purpose of configuring JavaScript transpilation regardless of the bundler used. The old `webpack_loader` option is deprecated but still supported with a warning.
+- **BREAKING CHANGE**: CSS Modules are now configured with named exports (`namedExport: true` and `exportLocalsConvention: 'camelCase'`) to align with Next.js and modern tooling standards.
+  - **JavaScript**: Use named imports (`import { className } from './styles.module.css'`)
+  - **TypeScript**: Requires namespace imports (`import * as styles from './styles.module.css'`) due to TypeScript's inability to type dynamic named exports
+  - Note: Default imports (`import styles from '...'`) will no longer work as css-loader with `namedExport: true` doesn't generate a default export
+  - See the [CSS Modules Export Mode documentation](./docs/css-modules-export-mode.md) for detailed migration instructions and override options
+
+## [v9.0.0.beta.2] - September 25, 2025
 ### Added
 
 * Support for subresource integrity. [PR 570](https://github.com/shakacode/shakapacker/pull/570) by [panagiotisplytas](https://github.com/panagiotisplytas)

data/CLAUDE.md

@@ -0,0 +1,29 @@
+# Shakapacker Project Guidelines
+
+## Critical Requirements
+- **ALWAYS end all files with a trailing newline character.** This is required by the project's linting rules.
+- **ALWAYS use `bundle exec` prefix when running Ruby commands** (rubocop, rspec, rake, etc.)
+- **ALWAYS run `bundle exec rubocop` before committing Ruby changes**
+- **ALWAYS run `yarn lint` before committing JavaScript changes**
+
+## Testing
+- Run corresponding RSpec tests when changing source files
+- For example, when changing `lib/shakapacker/foo.rb`, run `spec/shakapacker/foo_spec.rb`
+- Run the full test suite with `bundle exec rspec` before pushing
+
+## Code Style
+- Follow existing code conventions in the file you're editing
+- Use the project's existing patterns and utilities
+- No unnecessary comments unless requested
+- Keep changes focused and minimal - avoid extraneous diffs
+
+## Git Workflow
+- Create feature branches for all changes
+- Never push directly to main branch
+- Create small, focused PRs that are easy to review
+- Always create a PR immediately after pushing changes
+
+## Shakapacker-Specific
+- This gem supports both webpack and rspack configurations
+- Test changes with both bundlers when modifying core functionality
+- Be aware of the dual package.json/Gemfile dependency management

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    shakapacker (9.0.0.beta.0)
+    shakapacker (9.0.0.beta.3)
       activesupport (>= 5.2)
       package_json
       rack-proxy (>= 0.6.1)

data/README.md

@@ -1,4 +1,9 @@
 # Shakapacker (v8)
+---
+
+_🚀 Shakapacker 9.0.0.beta.2 supports [Rspack](https://rspack.rs/)! 10x faster than webpack!_
+
+---
 
 _Official, actively maintained successor to [rails/webpacker](https://github.com/rails/webpacker). ShakaCode stands behind the long-term maintenance and development of this project for the Rails community._
 
@@ -926,6 +931,30 @@ source_path: frontend # packs are the files in frontend/
 public_output_path: assets/packs # outputs to => public/assets/packs
 ```
 
+For server-side rendering (SSR) scenarios where you need to generate bundles that should not be served publicly, you can use the `private_output_path` configuration:
+
+```yml
+# config/shakapacker.yml
+private_output_path: ssr-generated # outputs to => ssr-generated/
+```
+
+This is particularly useful when working with libraries like React on Rails where server bundles need to be kept separate from client bundles.
+
+#### Migration Guide for React on Rails Users
+
+If you're using React on Rails with separate client and server bundles, you can now leverage the `private_output_path` configuration instead of using custom webpack configurations:
+
+1. Update your `config/shakapacker.yml`:
+   ```yml
+   # Before: both client and server bundles in public/
+   # After: separate directories
+   public_output_path: packs        # Client bundles (publicly served)
+   private_output_path: ssr-bundles  # Server bundles (not publicly served)
+   ```
+
+2. Update your webpack configuration to use the appropriate output path based on the bundle type
+3. The validation ensures `private_output_path` and `public_output_path` are different to prevent configuration errors
+
 Similarly, you can also control and configure `webpack-dev-server` settings from `config/shakapacker.yml` file:
 
 ```yml
@@ -993,7 +1022,19 @@ pnpm install --frozen-lockfile
 bun install --frozen-lockfile
 ```
 
-If you are using a CDN setup, Shakapacker does NOT use the `ASSET_HOST` environment variable to prefix URLs for assets during bundle compilation. You must use the `SHAKAPACKER_ASSET_HOST` environment variable instead (`WEBPACKER_ASSET_HOST` if you're using any version of Webpacker or Shakapacker before Shakapacker v7).
+### CDN
+
+Shakapacker supports serving JavaScript bundles and assets from a CDN. The key configuration is setting the `SHAKAPACKER_ASSET_HOST` environment variable (NOT the Rails `ASSET_HOST` variable).
+
+For detailed CDN setup instructions, including CloudFlare configuration, troubleshooting, and advanced setups, see the [CDN Setup Guide](./docs/cdn_setup.md).
+
+**Quick example:**
+```bash
+export SHAKAPACKER_ASSET_HOST=https://cdn.example.com
+RAILS_ENV=production bundle exec rails assets:precompile
+```
+
+For more deployment documentation, see [Deployment](./docs/deployment.md).
 
 ## Example Apps
 * [React on Rails Tutorial With SSR, HMR fast refresh, and TypeScript](https://github.com/shakacode/react_on_rails_tutorial_with_ssr_and_hmr_fast_refresh)

data/Rakefile

@@ -14,16 +14,51 @@ namespace :run_spec do
     sh("bundle exec rspec spec/shakapacker/*_spec.rb")
   end
 
-  desc "Run specs in the dummy app"
+  desc "Run specs in the dummy app with webpack"
   task :dummy do
-    puts "Running dummy app specs"
+    puts "Running dummy app specs with webpack"
     spec_dummy_dir = Pathname.new(File.join("spec", "dummy")).realpath
     Bundler.with_unbundled_env do
       sh_in_dir(".", "yalc publish")
       sh_in_dir(spec_dummy_dir, [
         "bundle install",
         "yalc link shakapacker",
-        "yarn install",
+        "npm install",
+        "bin/test-bundler webpack",
+        "NODE_ENV=test RAILS_ENV=test bin/shakapacker",
+        "bundle exec rspec"
+      ])
+    end
+  end
+
+  desc "Run specs in the dummy app with rspack"
+  task :dummy_with_rspack do
+    puts "Running dummy app specs with rspack"
+    spec_dummy_dir = Pathname.new(File.join("spec", "dummy")).realpath
+    Bundler.with_unbundled_env do
+      sh_in_dir(".", "yalc publish")
+      sh_in_dir(spec_dummy_dir, [
+        "bundle install",
+        "yalc link shakapacker",
+        "npm install",
+        "bin/test-bundler rspack",
+        "NODE_ENV=test RAILS_ENV=test bin/shakapacker",
+        "bundle exec rspec"
+      ])
+    end
+  end
+
+  desc "Run specs in the dummy-rspack app"
+  task :dummy_rspack do
+    puts "Running dummy-rspack app specs"
+    spec_dummy_dir = Pathname.new(File.join("spec", "dummy-rspack")).realpath
+    Bundler.with_unbundled_env do
+      sh_in_dir(".", "yalc publish")
+      sh_in_dir(spec_dummy_dir, [
+        "bundle install",
+        "yalc link shakapacker",
+        "npm install",
+        "NODE_ENV=test RAILS_ENV=test npm exec --no -- rspack build --config config/rspack/rspack.config.js",
         "bundle exec rspec"
       ])
     end
@@ -35,7 +70,7 @@ namespace :run_spec do
   end
 
   desc "Run all specs"
-  task all_specs: %i[gem dummy generator] do
+  task all_specs: %i[gem dummy dummy_with_rspack dummy_rspack generator] do
     puts "Completed all RSpec tests"
   end
 end

data/TODO.md

@@ -0,0 +1,51 @@
+# TypeScript Migration Status
+
+## ✅ Completed (PR #602)
+- Enhanced `package/index.d.ts` with comprehensive type definitions
+- Added TypeScript type packages for better IDE support
+- Improved Config and DevServerConfig interfaces
+- Added missing properties (private_output_path, inline_css, env_prefix, etc.)
+- All tests passing
+- Zero JavaScript modifications (no whitespace changes)
+- Full backward compatibility maintained
+
+## 📋 Next Steps (Issue #605)
+
+### Phase 2: Core Module Conversion
+- [ ] Convert `package/config.js` to TypeScript
+- [ ] Convert `package/env.js` to TypeScript  
+- [ ] Convert `package/index.js` to TypeScript
+- [ ] Convert `package/utils/helpers.js` to TypeScript
+
+### Phase 3: Environment & Build System
+- [ ] Convert environment files (base, development, production, test)
+- [ ] Convert dev_server.js
+- [ ] Convert webpackDevServerConfig.js
+
+### Phase 4: Rules & Loaders
+- [ ] Convert all files in `package/rules/`
+- [ ] Convert all files in `package/plugins/`
+- [ ] Convert all files in `package/optimization/`
+
+### Phase 5: Framework-Specific Modules
+- [ ] Convert rspack support files
+- [ ] Convert swc support files
+- [ ] Convert esbuild support files
+- [ ] Convert babel preset
+
+### Phase 6: Final Cleanup
+- [ ] Convert remaining utilities
+- [ ] Add TypeScript linting
+- [ ] Enable strict mode
+- [ ] Update documentation
+
+## Why Gradual Migration?
+- **Lower risk**: Each phase can be tested independently
+- **Team learning**: Get familiar with TypeScript incrementally
+- **Immediate value**: Type definitions already provide IDE benefits
+- **No breaking changes**: Users unaffected during migration
+
+## Related Links
+- Original issue: #200
+- Initial PR: #602
+- Next steps issue: #605

data/TODO_v9.md

@@ -0,0 +1,84 @@
+# Shakapacker v9 TODO List
+
+## CSS Modules Configuration Alignment
+
+### Problem
+Current CSS modules configuration causes TypeScript/webpack warnings because of default vs named export mismatch.
+
+### Current Behavior (v8)
+- CSS modules use default export: `import styles from './styles.module.css'`
+- This causes warnings but works at runtime
+- Warning example: `export 'default' (imported as 'style') was not found in './HelloWorld.module.css'`
+
+### Proposed v9 Change
+Align with Next.js and modern tooling by using named exports:
+
+1. **Update css-loader configuration:**
+```javascript
+{
+  loader: 'css-loader',
+  options: {
+    modules: {
+      namedExport: true,
+      exportLocalsConvention: 'camelCase'
+    }
+  }
+}
+```
+
+2. **Update TypeScript types:**
+- Ensure proper typing for CSS modules with named exports
+- May need to update or generate `.d.ts` files for CSS modules
+
+3. **Migration guide for users:**
+- Document the breaking change
+- Provide codemod or migration script to update imports from:
+  ```javascript
+  import styles from './styles.module.css'
+  styles.className
+  ```
+  to:
+  ```javascript
+  import * as styles from './styles.module.css'
+  // or
+  import { className } from './styles.module.css'
+  ```
+
+### Benefits
+- Eliminates webpack/TypeScript warnings
+- Better tree-shaking potential
+- More explicit about what CSS classes are being used
+- Easier interoperability with frameworks that support named exports
+
+### Implementation Notes
+- This is a BREAKING CHANGE and appropriate for major version bump
+- Need to test with both webpack and rspack
+- Consider providing a compatibility mode via configuration option
+
+---
+
+## Related Issues from PR #597
+
+### React Component Not Rendering (spec/dummy) - RESOLVED ✅
+- **Issue**: React component was not rendering due to CSS module import mismatch
+- **Symptoms**:
+  - Component wasn't rendering "Hello, Stranger!"
+  - Input field not rendered, making interactive test fail
+  - Only the static H1 "Hello, World!" was visible
+- **Resolution**:
+  - Fixed CSS module import syntax from `import style from` to `import * as style from`
+  - This matched webpack's named exports configuration for CSS modules
+  - Tests now pass with both React 18.3.1 and webpack/rspack configurations
+- **Root Cause**: CSS module import/export mismatch
+  - Webpack was configured to use named exports for CSS modules
+  - TypeScript code was using default import syntax
+  - This caused `style` to be undefined, breaking SSR and client rendering
+- **Status**: FIXED
+  - All tests re-enabled and passing
+  - Both SSR and client-side rendering working
+  - Interactive functionality restored
+
+### Test Infrastructure
+- Successfully implemented dual bundler support (webpack/rspack)
+- test-bundler script working well with status command
+- Consider adding more comprehensive tests for both bundlers