shakapacker 10.1.0 → 10.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8dc01ff79d020c836ae53bdef4d47df68ad3c8984a105b1fd8b52facc80ad8fa
-  data.tar.gz: 2fe07359eea5a27e55a566ee28c33ad5bd32cedce9a7aab3d0f27418cec2a808
+  metadata.gz: 441942bb193dab20df1d0956197e3d441adb6fef5e25001a4eb1f05c69543312
+  data.tar.gz: 4aea05e5fa5f72da3b65fd108514400ca6c7140c85cdf7d10aa1d6edf6118d43
 SHA512:
-  metadata.gz: fc172e0660b3aca80927669091428921033af0cf103b3502dd4dc5be68b4d85d287b684e4c66b224125a6b20f747b3a60d840807c442e3d28a7c34bea520151b
-  data.tar.gz: 071a4e88670fb3503edbbeef1fce516b2accb953751e3abb60d88d92622468821871d15a71251b1beb055ffe1c86b36a1d60a4a8f4a2e296d43161413f4b917c
+  metadata.gz: a2d3907c1a2d5121c7b70f72cb46c8ea09157e263241803b67ce2d250f7183121442bc0e0b6387d1552008565a3802e5a57c6447f4f6bee0d3e3f9214f16786f
+  data.tar.gz: 3b59158ac878b1403defdc3a22293a2559bb99d13c106175d2c72d637596ad4dfbdd5174aea80222070f50ee911bb7e585a1cae830886bb75be9f942f310e6ed

data/CHANGELOG.md

@@ -9,6 +9,31 @@
 
 ## [Unreleased]
 
+## [v10.2.0] - July 3, 2026
+
+### Added
+
+- **Added `webpack_compile_flags` configuration**. [PR #1180](https://github.com/shakacode/shakapacker/pull/1180) by [justin808](https://github.com/justin808). Allows Rails-driven Shakapacker compiles to pass extra webpack/rspack CLI flags, such as `--fail-on-warnings` or `--progress`, through `bin/shakapacker`. Fixes [#1175](https://github.com/shakacode/shakapacker/issues/1175).
+- **Added AI analysis prompt generation to the config exporter**. [PR #695](https://github.com/shakacode/shakapacker/pull/695), [PR #1184](https://github.com/shakacode/shakapacker/pull/1184) by [justin808](https://github.com/justin808). When running doctor mode (`bin/shakapacker-config --doctor`), the exporter now also writes an `AI-ANALYSIS-PROMPT.md`: a ready-to-paste prompt that guides an AI assistant (ChatGPT, Claude, Gemini, etc.) to review the configuration for migration issues (webpack ↔ rspack), build errors, client/server and development/production optimizations, and best practices. The React on Rails–specific guidance in the generated prompt is included only when React on Rails is detected in the app (via `package.json`, `Gemfile`, or `Gemfile.lock`). This is purely additive; existing exports are unchanged, and a failure to write the prompt file only warns without affecting the exported configs.
+- **Added support for `sass-loader` v17**. [PR #1141](https://github.com/shakacode/shakapacker/pull/1141) by [fukayatsu](https://github.com/fukayatsu). Widened the optional `sass-loader` peer range to `^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0` in core `shakapacker`, `shakapacker-webpack`, and `shakapacker-rspack`. The Sass rule already selects `loadPaths` for v16+ and keeps `api: "modern"`, both of which remain valid in v17. Note that sass-loader v17 requires Node.js 22.11.0+ and drops `node-sass` and the legacy Sass JS API, so apps that opt into v17 must already be on Node 22.12+ (the upper branch of Shakapacker's `engines.node` range).
+- **Added Babel 8 peer dependency support**. [PR #1187](https://github.com/shakacode/shakapacker/pull/1187) by [justin808](https://github.com/justin808). Widened the Babel peer ranges in core `shakapacker` and the `shakapacker-webpack` supplemental package to allow Babel 8, and updated the Shakapacker Babel preset to omit options removed in Babel 8 while preserving existing Babel 7 behavior. Repository development pins stay on Babel 7, with added compatibility tests covering Babel 8. Refs [#1163](https://github.com/shakacode/shakapacker/issues/1163).
+
+### Changed
+
+- **New installs now default to Rspack instead of webpack**. [PR #1150](https://github.com/shakacode/shakapacker/pull/1150) by [justin808](https://github.com/justin808). `bundle exec rake shakapacker:install` now scaffolds an Rspack project (config, dependencies, and `config/shakapacker.yml`) by default. This is a new-install default only: existing applications are unaffected. The Rspack default applies only to brand-new installs — re-running the installer on an app that already has a `config/shakapacker.yml` keeps that app's current bundler (and installs that bundler's dependencies), so the installer never silently switches an existing project's bundler. To install with webpack, run `bundle exec rake shakapacker:install[webpack]` or set `SHAKAPACKER_ASSETS_BUNDLER=webpack`; to change an existing app's bundler, use `bundle exec rake shakapacker:switch_bundler`.
+- **Changed Rspack support to target Rspack v2 only.** [PR #1179](https://github.com/shakacode/shakapacker/pull/1179) by [justin808](https://github.com/justin808). Core, installer, switch-bundler defaults, supplemental package, dummy app, and docs now use `@rspack/core`, `@rspack/cli`, `@rspack/dev-server`, and `@rspack/plugin-react-refresh` v2 ranges. Rspack installs now also require `rspack-manifest-plugin@^5.2.2`, and `shakapacker-rspack` requires `css-loader@^7.1.4` for Rspack v2 peer compatibility. The Rspack React Refresh loader now uses the v2 named `ReactRefreshRspackPlugin` export instead of retaining legacy v1 export-shape fallbacks.
+
+### Fixed
+
+- **Fixed helper binstubs and doctor checks for subdirectory JavaScript layouts**. [PR #1192](https://github.com/shakacode/shakapacker/pull/1192) by [justin808](https://github.com/justin808). `bin/shakapacker-config` and `bin/diff-bundler-config` now resolve package scripts from a configured client package root before falling back to the Rails root, and `shakapacker:doctor` now searches package metadata, lockfiles, and installed packages across client/root layouts while reducing false SWC dependency issues for custom hybrid webpack/Rspack setups. Fixes [#1170](https://github.com/shakacode/shakapacker/issues/1170) and [#1090](https://github.com/shakacode/shakapacker/issues/1090).
+- **Fixed dev-server passthrough argument validation messages**. [PR #1180](https://github.com/shakacode/shakapacker/pull/1180) by [justin808](https://github.com/justin808). `bin/shakapacker-dev-server -- --host ...` or `--port ...` now fails with a clearer Shakapacker message instead of forwarding the separator to the bundler; set `dev_server.host` and `dev_server.port` in `config/shakapacker.yml` instead.
+- **Fixed `shakapacker:export_bundler_config` regression on apps upgraded from older Shakapacker versions**. [PR #1127](https://github.com/shakacode/shakapacker/pull/1127) by [justin808](https://github.com/justin808). The task previously invoked `bin/shakapacker-config` unconditionally via `RbConfig.ruby`, which crashed when the file was still the legacy JavaScript binstub (`#!/usr/bin/env node`) left over from earlier installs. The task now inspects the shebang and exec's the file directly when it points at Node, while keeping the Ruby+`RbConfig.ruby` path for the current Ruby binstub. Affected users are also nudged to run `bundle exec rake shakapacker:binstubs` to refresh their helper binstub. Refs [#1123](https://github.com/shakacode/shakapacker/issues/1123).
+- **Fixed `shakapacker:doctor` Sass implementation detection for `sass-embedded` apps**. [PR #1178](https://github.com/shakacode/shakapacker/pull/1178) by [justin808](https://github.com/justin808). The doctor now accepts either modern Sass implementation package (`sass` or `sass-embedded`) when Sass files are present, matching Shakapacker's default modern Sass API instead of incorrectly requiring Dart Sass. New installs also include `sass` alongside `sass-loader`. Fixes [#1172](https://github.com/shakacode/shakapacker/issues/1172).
+- **Fixed `Psych::DisallowedClass` boot crash when `pnpm-lock.yaml` contains a `time:` section.** [PR #1161](https://github.com/shakacode/shakapacker/pull/1161) by [justin808](https://github.com/justin808). pnpm >= 10.16 (default in pnpm 11) writes publish timestamps into `pnpm-lock.yaml` that Psych 4+ refuses to safe-load, so the `shakapacker.version_checker` boot initializer raised `Psych::DisallowedClass: Tried to load unspecified class: Time` and crashed every Rails boot — even when version checking was disabled. The lockfile is now parsed with `YAML.safe_load(..., permitted_classes: [Time, Date])`. Fixes [#1160](https://github.com/shakacode/shakapacker/issues/1160).
+- **Fixed Rspack dev-server lazy compilation defaults for Rails split dev-server topology**. [PR #1179](https://github.com/shakacode/shakapacker/pull/1179) by [justin808](https://github.com/justin808). Generated Rspack development configs now set top-level `lazyCompilation: false` while the dev server is running, preventing Rspack CLI dev-server auto-lazy behavior from routing dynamic imports through lazy trigger URLs Rails does not serve. Apps that intentionally use lazy compilation can still set a safe top-level `lazyCompilation` value in their Rspack config.
+- **Fixed Rspack dev-server config loading during static watch builds**. [PR #1142](https://github.com/shakacode/shakapacker/pull/1142) by [justin808](https://github.com/justin808). The Rspack `devServer` configuration is now gated behind `WEBPACK_SERVE=true`, matching the webpack development config, so static watch builds (`bin/shakapacker --watch`) no longer load the dev-server client. The `devMiddleware.writeToDisk` filter that skips hot-update files is preserved. Fixes [#1137](https://github.com/shakacode/shakapacker/issues/1137).
+- **Fixed compiler strategies ignoring the instance config of custom `Shakapacker::Instance` objects.** [PR #1147](https://github.com/shakacode/shakapacker/pull/1147) by [justin808](https://github.com/justin808). Ports [#976](https://github.com/shakacode/shakapacker/pull/976) by [brunodccarvalho](https://github.com/brunodccarvalho). Strategies now read the instance-specific config and watch both webpack and rspack config directories.
+
 ## [v10.1.0] - May 27, 2026
 
 ### Added
@@ -30,6 +55,7 @@
 ### ⚠️ Breaking Changes
 
 - **Breaking: tightened `package.json` `engines.node` to `^20.19.0 || >=22.12.0`**. [PR #1099](https://github.com/shakacode/shakapacker/pull/1099) by [justin808](https://github.com/justin808). Raised from `>= 20`, dropping support for Node 20.0.0–20.18.x and Node 21.x to match `@rspack/core@2.0.0-rc.0`. Consumers on those versions will hit an engine error with `--engine-strict` or yarn workspaces and need to upgrade. The PR also bumps `.node-version` to `22.20.0` and updates `conductor-setup.sh` to enforce the same disjoint range up front, so contributors get a clear error before `yarn install` fails with a confusing engine mismatch.
+- **Breaking: native ESM named imports of lazy `baseConfig` and `rules` no longer work**. [PR #1107](https://github.com/shakacode/shakapacker/pull/1107) by [justin808](https://github.com/justin808). The side-effect fix for [#1095](https://github.com/shakacode/shakapacker/issues/1095) reimplements `baseConfig` and `rules` as lazy getters, so Node no longer statically detects those two CommonJS properties as named exports. Native ESM consumers must access them via the default import (`import shakapacker from 'shakapacker'; const { baseConfig, rules } = shakapacker`, or the same pattern for `shakapacker/rspack`) rather than `import { baseConfig, rules } ...`, which now throws a `SyntaxError` at load time. Other named imports (`config`, `generateWebpackConfig`, `env`, `merge`, `generateRspackConfig`, etc.) are unaffected and explicitly preserved. CommonJS access (`require('shakapacker').baseConfig`, `require('shakapacker/rspack').baseConfig`) — including direct assignment to override the lazy value — continues to work.
 
 ### Changed
 
@@ -40,6 +66,7 @@
 
 - **Fixed webpack-dev-server `static` config defaulting to watch `public/` directory unnecessarily**. [PR #1032](https://github.com/shakacode/shakapacker/pull/1032) by [ihabadham](https://github.com/ihabadham). Three bugs fixed: (1) `static` now defaults to `false` instead of a misconfigured object that caused webpack-dev-server to watch the `public/` directory, which is already served by Rails via `ActionDispatch::Static`; (2) setting `static: false` in `shakapacker.yml` is no longer silently ignored; (3) the default template no longer includes `static.watch`, which was a v3→v4 migration artifact. Fixes [#1031](https://github.com/shakacode/shakapacker/issues/1031).
 - **Fixed Rspack React Refresh plugin loading with `@rspack/plugin-react-refresh` v2**. [PR #1116](https://github.com/shakacode/shakapacker/pull/1116) by [justin808](https://github.com/justin808). Shakapacker now reads the v2 named `ReactRefreshRspackPlugin` export while retaining compatibility with v1 direct/default CommonJS export shapes, preventing `TypeError: ReactRefreshRspackPlugin is not a constructor` during rspack dev-server startup.
+- **Fixed `require("shakapacker")` and `require("shakapacker/rspack")` triggering plugin initialization as a side effect**. [PR #1107](https://github.com/shakacode/shakapacker/pull/1107) by [justin808](https://github.com/justin808). `baseConfig` and `rules` are now exposed via lazy getters for both webpack and rspack entry points, so `ensureManifestExists`, plugin constructors, and (for rspack) `@rspack/core` / `rspack-manifest-plugin` resolution are delayed until config generation or the relevant lazy export is actually requested. Fixes [#1095](https://github.com/shakacode/shakapacker/issues/1095). Note: directly assigning `baseConfig` (e.g. `require("shakapacker").baseConfig = custom`) overrides the value read back from the entry point, but it changes `generateWebpackConfig`/`generateRspackConfig` output only in the fallback case where no `environments/<NODE_ENV>.js` file exists; normal NODE_ENV builds load `environments/<env>.js` (which requires the real base directly) and are unaffected. For `shakapacker/rspack`, see the matching ⚠️ Breaking Changes entry about native ESM named imports of these lazy exports.
 - **Widened `@rspack/plugin-react-refresh` peer range to `^1.0.0 || ^2.0.0-0`**. [PR #1091](https://github.com/shakacode/shakapacker/pull/1091) by [ihabadham](https://github.com/ihabadham). Fixes the `ERESOLVE` conflict when installing `@rspack/plugin-react-refresh@^2.0.0` alongside `shakapacker@10.0.0`.
 - **Fixed `NodePackageVersion#find_version` for local-path `shakapacker` installs (e.g. `yalc`, `file:`, relative paths)**. [PR #1086](https://github.com/shakacode/shakapacker/pull/1086), [PR #1106](https://github.com/shakacode/shakapacker/pull/1106) by [justin808](https://github.com/justin808). The version check now consults `package.json` first and short-circuits on `../`, `./`, and `file:` dependencies, so stale lockfile semvers no longer trigger false gem↔node version mismatches. `package_json_dependency` also consults `devDependencies` in addition to `dependencies`. The `LOCAL_PATH_REGEX` constant replaces a duplicated inline regex and anchors both alternatives to the start of the string, removing a latent false-positive on version strings containing `..` mid-value. Fixes [#1103](https://github.com/shakacode/shakapacker/issues/1103).
 - **Fix rspack setup not reusing certain shared webpack-rspack config settings**. [PR #1085](https://github.com/shakacode/shakapacker/pull/1085) by [brunodccarvalho](https://github.com/brunodccarvalho). Default config changes include `optimization.splitChunks.chunks="all"`, `optimization.runtimeChunk="single"`, the webpack compression plugin in production, and the removal of minimization plugins in development. Fixes [#984](https://github.com/shakacode/shakapacker/issues/984).
@@ -946,7 +973,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/v10.1.0...main
+[Unreleased]: https://github.com/shakacode/shakapacker/compare/v10.2.0...main
+[v10.2.0]: https://github.com/shakacode/shakapacker/compare/v10.1.0...v10.2.0
 [v10.1.0]: https://github.com/shakacode/shakapacker/compare/v10.0.0...v10.1.0
 [v10.0.0]: https://github.com/shakacode/shakapacker/compare/v9.7.0...v10.0.0
 [v9.7.0]: https://github.com/shakacode/shakapacker/compare/v9.6.1...v9.7.0