shakapacker 9.2.0 → 9.3.0.beta.0

data/docs/v6_upgrade.md

@@ -13,41 +13,47 @@ Webpacker used to configure Webpack indirectly, which lead to a [complicated sec
 While you have to configure integration with frameworks yourself, [`webpack-merge`](https://github.com/survivejs/webpack-merge) helps with this. See this example for [Vue](https://github.com/shakacode/shakapacker#other-frameworks) and scroll to the bottom for [more examples](#examples-of-v5-to-v6).
 
 ## webpacker v6.0.0.rc.6 to shakapacker v6.0.0
+
 See an example migration here: [PR 27](https://github.com/shakacode/react_on_rails_tutorial_with_ssr_and_hmr_fast_refresh/pull/27).
 
 ### Update to v6.5.2
+
 1. Remove setting the NODE_ENV in your `bin/webpacker` and `bin/webpacker-dev-server` bin stubs as these are not set in the webpack runner file.
 
 ### Update Steps to v6.0.0 from v6.0.0.rc.6
+
 _If you're on webpacker v5, follow [how to upgrade to webpacker v6.0.0.rc.6 from v5](#how-to-upgrade-to-webpacker-v600rc6-from-v5) to get to v6.0.0.rc.6 first._
 
 1. Change the gem name from `webpacker` to `shakapacker` and the NPM package from `@rails/webpacker` to `shakapacker`.
 1. Install the peer dependencies. Run `yarn add @babel/core @babel/plugin-transform-runtime @babel/preset-env @babel/runtime babel-loader compression-webpack-plugin terser-webpack-plugin webpack webpack-assets-manifest webpack-cli webpack-merge webpack-sources webpack-dev-server`. You may have old versions of libraries. Run `yarn install` and check for warnings like `warning " > shakapacker@6.1.1" has incorrect peer dependency "compression-webpack-plugin@^9.0.0"` and `file-loader@1.1.11" has incorrect peer dependency "webpack@^2.0.0 || ^3.0.0 || ^4.0.0"`. In other words, warnings like these are **serious** and will cause considerable confusion if not respected.
 1. Update any scripts that called `bin/webpack` or `bin/webpack-dev-server` to `bin/webpacker` or `bin/webpacker-dev-server`
 1. Update your webpack config for a single config file, `config/webpack/webpack.config.js`. If you want to use the prior style of having a separate file for each NODE_ENV, you can use this shim for `config/webpack/webpack.config.js`. WARNING, previously, if you did not set `NODE_ENV`, `NODE_ENV` defaulted to `development`. Thus, you might expect `config/webpack/development.js` to run, but you'll instead be using the the configuration file that corresponds to your `RAILS_ENV`. If your `RAILS_ENV` is `test`, you'd be running `config/webpack/test.js`.
+
    ```js
    // name this file config/webpack/webpack.config.js
-   const { env, webpackConfig } = require('shakapacker')
-   const { existsSync } = require('fs')
-   const { resolve } = require('path')
+   const { env, webpackConfig } = require("shakapacker")
+   const { existsSync } = require("fs")
+   const { resolve } = require("path")
 
    const envSpecificConfig = () => {
      const path = resolve(__dirname, `${env.nodeEnv}.js`)
      if (existsSync(path)) {
        console.log(`Loading ENV specific webpack configuration file ${path}`)
        return require(path)
-     } else {                       
+     } else {
        // Probably an error if the file for the NODE_ENV does not exist
-       throw new Error(`Got Error with NODE_ENV = ${env.nodeEnv}`);
+       throw new Error(`Got Error with NODE_ENV = ${env.nodeEnv}`)
      }
    }
 
    module.exports = envSpecificConfig()
    ```
+
 1. Update `babel.config.js` if you need JSX support. See [Customizing Babel Config](./customizing_babel_config.md)
 1. If you are using the view helper called `asset_pack_path`, change "media/" in path to "static/" or consider using the `image_pack_path`.
 
 ## How to upgrade to Webpacker v6.0.0.rc.6 from v5
+
 1. Ensure you have a clean working git branch. You will be overwriting all your files and reverting the changes that you don't want.
 
 1. **Ensure no nested directories in your `source_entry_path`.** Check if you had any entry point files in child directories of your `source_entry_path`. Files for entry points in child directories are not supported by shakacode/shakapacker v6. Move those files to the top level, adjusting any imports in those files.
@@ -80,67 +86,73 @@ _If you're on webpacker v5, follow [how to upgrade to webpacker v6.0.0.rc.6 from
    Overwrite all files and check what changed.
 
    Note, the webpacker:install will install the peer dependencies:
+
    ```bash
    yarn add @babel/core @babel/plugin-transform-runtime @babel/preset-env @babel/runtime babel-loader compression-webpack-plugin terser-webpack-plugin webpack webpack-assets-manifest webpack-cli webpack-merge webpack-sources webpack-dev-server
    ```
 
 1. Review the new default's changes to `webpacker.yml`. Consider each suggested change carefully, especially the change to have your `source_entry_path` be at the top level of your `source_path`.
    The v5 default used `packs` for `source_entry_path`:
+
    ```yml
    source_path: app/javascript
    source_entry_path: packs
    ```
+
    The v6 default uses the top level directory.
+
    ```yml
    source_path: app/javascript
    source_entry_path: /
    ```
+
    If you prefer this configuration, then you will move your `app/javascript/packs/*` (including `application.js`) to `app/javascript/` and update the configuration file.
 
    Note, moving your files is optional, as you can still keep your entries in a separate directory, called something like `packs`, or `entries`. This directory is defined with the `source_path`.
 
 1. Update `webpack-dev-server` to the current version, greater than 4.2, updating `package.json`.
 
-   **Important:** If you encounter the error `[webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema` with an unknown property `_assetEmittingPreviousFiles`, this indicates your webpack-dev-server configuration contains deprecated options. 
-   
+   **Important:** If you encounter the error `[webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema` with an unknown property `_assetEmittingPreviousFiles`, this indicates your webpack-dev-server configuration contains deprecated options.
+
    To resolve this issue:
    - Ensure you're using webpack-cli >= 4.7.0 with webpack-dev-server 5.x (webpack-cli 4.7+ is compatible with webpack-dev-server v5)
    - Check your current versions: `npm list webpack-cli webpack-dev-server`
    - Remove any legacy options like `_assetEmittingPreviousFiles` from your dev-server configuration
    - Review the [webpack-dev-server migration guide](https://github.com/webpack/webpack-dev-server/blob/master/migration-v5.md) for proper v4 to v5 migration steps
-   
+
    See [issue #526](https://github.com/shakacode/shakapacker/issues/526) for more details.
 
-1. Update API usage of the view helpers by changing `javascript_packs_with_chunks_tag` and `stylesheet_packs_with_chunks_tag` to `javascript_pack_tag` and `stylesheet_pack_tag`. Ensure that your layouts and views will only have **at most one call** to `javascript_pack_tag` and **at most one call** to `stylesheet_pack_tag`. You can now pass multiple bundles to these view helper methods. If you fail to changes this, you may experience performance issues, and other bugs related to multiple copies of React, like [issue 2932](https://github.com/rails/webpacker/issues/2932).  If you expose jquery globally with `expose-loader` by using `import $ from "expose-loader?exposes=$,jQuery!jquery"` in your `app/javascript/application.js`, pass the option `defer: false` to your `javascript_pack_tag`.
+1. Update API usage of the view helpers by changing `javascript_packs_with_chunks_tag` and `stylesheet_packs_with_chunks_tag` to `javascript_pack_tag` and `stylesheet_pack_tag`. Ensure that your layouts and views will only have **at most one call** to `javascript_pack_tag` and **at most one call** to `stylesheet_pack_tag`. You can now pass multiple bundles to these view helper methods. If you fail to changes this, you may experience performance issues, and other bugs related to multiple copies of React, like [issue 2932](https://github.com/rails/webpacker/issues/2932). If you expose jquery globally with `expose-loader` by using `import $ from "expose-loader?exposes=$,jQuery!jquery"` in your `app/javascript/application.js`, pass the option `defer: false` to your `javascript_pack_tag`.
 
 1. If you are using any integrations like `css`, `postcss`, `React` or `TypeScript`. Please see https://github.com/shakacode/shakapacker#integrations section on how they work in v6.
 
 1. `config/webpack/environment.js` was changed to `config/webpack/base.js` and exports a native webpack config so no need to call `toWebpackConfig`.
    Use `merge` to make changes:
-   
+
    ```js
    // config/webpack/base.js
-   const { webpackConfig, merge } = require('@rails/webpacker');
+   const { webpackConfig, merge } = require("@rails/webpacker")
    const customConfig = {
      module: {
        rules: [
          {
-           test: require.resolve('jquery'),
-           loader: 'expose-loader',
+           test: require.resolve("jquery"),
+           loader: "expose-loader",
            options: {
-             exposes: ['$', 'jQuery']
+             exposes: ["$", "jQuery"]
            }
          }
        ]
      }
-   };
-   
-   module.exports = merge(webpackConfig, customConfig);
+   }
+
+   module.exports = merge(webpackConfig, customConfig)
    ```
- 
+
 1. Copy over custom browserlist config from `.browserslistrc` if it exists into the `"browserslist"` key in `package.json` and remove `.browserslistrc`.
 
 1. Remove `babel.config.js` if you never changed it. Configure your `package.json` to use the default:
+
    ```json
    "babel": {
      "presets": [
@@ -148,6 +160,7 @@ _If you're on webpacker v5, follow [how to upgrade to webpacker v6.0.0.rc.6 from
      ]
    }
    ```
+
    See customization example the [Customizing Babel Config](./customizing_babel_config.md) for React configuration.
 
 1. `extensions` was removed from the `webpacker.yml` file. Move custom extensions to your configuration by merging an object like this. For more details, see docs for [Webpack Configuration](https://github.com/shakacode/shakapacker/blob/main/README.md#webpack-configuration)
@@ -155,10 +168,11 @@ _If you're on webpacker v5, follow [how to upgrade to webpacker v6.0.0.rc.6 from
    ```js
    {
      resolve: {
-       extensions: ['.ts', '.tsx', '.vue', '.css']
+       extensions: [".ts", ".tsx", ".vue", ".css"]
      }
    }
    ```
+
 1. In `webpacker.yml`, check if you had `watched_paths`. That is now `additional_paths`.
 
 1. Some dependencies were removed in [PR 3056](https://github.com/rails/webpacker/pull/3056). If you see the error: `Error: Cannot find module 'babel-plugin-macros'`, or similar, then you need to `yarn add <dependency>` where <dependency> might include: `babel-plugin-macros`, `case-sensitive-paths-webpack-plugin`, `core-js`, `regenerator-runtime`. Or you might want to remove your dependency on those.
@@ -175,7 +189,6 @@ _If you're on webpacker v5, follow [how to upgrade to webpacker v6.0.0.rc.6 from
 
 1. Now, follow the steps above to get to shakapacker v6 from webpacker v6.0.0.rc.6
 
-
 ## Examples of v5 to v6
 
 1. [React on Rails Project with HMR and SSR](https://github.com/shakacode/react_on_rails_tutorial_with_ssr_and_hmr_fast_refresh/compare/webpacker-5.x...61e897f2c604085f45b9ab5e23642501e430fb28)

data/docs/v7_upgrade.md

@@ -14,7 +14,7 @@ Just so you know, Shakapacker v8 will remove any backward compatibility for spel
 
 **Note:** At each step of changing the version, ensure that you update both gem and npm versions to the same "exact" version (like `x.y.z` and not `^x.y.z` or `>= x.y.z`).
 
-1. Upgrade Shakapacker to the latest 6.x version and make sure there are no issues running your application. 
+1. Upgrade Shakapacker to the latest 6.x version and make sure there are no issues running your application.
 2. Upgrade Shakapacker to version 7.
 3. Run `rake shakapacker:binstubs` to get the new files in place. Then delete the `bin/webpacker` and `bin/webpacker-dev-server` ones.
 4. Change spelling from Webpacker to Shakapacker in the code
@@ -23,8 +23,8 @@ Just so you know, Shakapacker v8 will remove any backward compatibility for spel
      - Rename`Shakapacker.config.webpacker_precompile?` method, replace it with `Shakapacker.config.shakapacker_precompile?`
    - `--debug-webpacker` is now `--debug-shakapacker` for your shakapacker binstubs.
 5. Rename files
-    - Rename `config/webpacker.yml` to `config/shakapacker.yml`.
-    - Rename environment variables from `WEBPACKER_XYZ` to `SHAKAPACKER_XYZ`.
+   - Rename `config/webpacker.yml` to `config/shakapacker.yml`.
+   - Rename environment variables from `WEBPACKER_XYZ` to `SHAKAPACKER_XYZ`.
 6. Where you have used webpackConfig, you must create a new instance with `generateWebpackConfig`. Alternatively, you can rename the import to globalMutableWebpackConfig, which retains the v6 behavior of a global, mutable object.
 7. You may need to upgrade dependencies in package.json. You should use `yarn upgrade-interactive`.
 
@@ -35,25 +35,27 @@ When generating file paths for static assets, a top-level directory will no long
 ## The `webpackConfig` property is changed
 
 The `webpackConfig` property in the `shakapacker` module has been changed. The shakapacker module has two options:
+
 1. `generateWebpackConfig`: a function that returns a new webpack configuration object, which ensures that any modifications made to it will not affect any other usage of the webpack configuration.
 2. `globalMutableWebpackConfig`: if a project still desires the old mutable object. You can rename your imports of `webpackConfig` with `globalMutableWebpackConfig`.
 
 ## Example Upgrade
+
 If you started with:
 
 ```js
-const { webpackConfig } = require('shakapacker')
+const { webpackConfig } = require("shakapacker")
 ```
 
 Switch to:
 
 ```js
-const { generateWebpackConfig } = require('shakapacker')
+const { generateWebpackConfig } = require("shakapacker")
 const webpackConfig = generateWebpackConfig()
 ```
 
 or use `globalMutableWebpackConfig` if the project desires to use a globally mutable object.
 
 ```js
-const { globalMutableWebpackConfig: webpackConfig } = require('shakapacker')
+const { globalMutableWebpackConfig: webpackConfig } = require("shakapacker")
 ```

data/docs/v8_upgrade.md

@@ -18,6 +18,7 @@ If you are not using CDN, then this change will have no effect on your setup.
 If you are using CDN and your CDN host is static, `config.asset_host` setting in Rails will be respected during compilation and when referencing assets through view helpers.
 
 If your host might differ, between various environments for example, you will either need to:
+
 - Ensure the assets are specifically rebuilt for each environment (Heroku pipeline promote feature for example does not do that by default).
 - Make sure the assets are compiled with `SHAKAPACKER_ASSET_HOST=''` ENV variable to avoid hardcording URLs in packs output.
 
@@ -131,41 +132,41 @@ The function will return the same object with less risk:
 
 ```js
 // before
-const { globalMutableWebpackConfig, merge } = require('shakapacker');
+const { globalMutableWebpackConfig, merge } = require("shakapacker")
 
 const customConfig = {
   module: {
     rules: [
       {
-        test: require.resolve('jquery'),
-        loader: 'expose-loader',
-        options: { exposes: ['$', 'jQuery'] }
+        test: require.resolve("jquery"),
+        loader: "expose-loader",
+        options: { exposes: ["$", "jQuery"] }
       }
     ]
   }
-};
+}
 
-module.exports = merge(globalMutableWebpackConfig, customConfig);
+module.exports = merge(globalMutableWebpackConfig, customConfig)
 ```
 
 ```js
 // after
-const { generateWebpackConfig, merge } = require('shakapacker');
+const { generateWebpackConfig, merge } = require("shakapacker")
 
 const customConfig = {
   module: {
     rules: [
       {
-        test: require.resolve('jquery'),
-        loader: 'expose-loader',
-        options: { exposes: ['$', 'jQuery'] }
+        test: require.resolve("jquery"),
+        loader: "expose-loader",
+        options: { exposes: ["$", "jQuery"] }
       }
     ]
   }
-};
+}
 
 // you can also pass your config directly to the generator function to have it merged in!
-module.exports = merge(generateWebpackConfig(), customConfig);
+module.exports = merge(generateWebpackConfig(), customConfig)
 ```
 
 ## `additional_paths` are now stripped just like with `source_path`

data/docs/v9_upgrade.md

@@ -2,6 +2,8 @@
 
 This guide outlines new features, breaking changes, and migration steps for upgrading from Shakapacker v8 to v9.
 
+**📖 For detailed configuration options, see the [Configuration Guide](./configuration.md)**
+
 > **⚠️ Important for v9.1.0 Users:** If you're upgrading to v9.1.0 or later, please note the [SWC Configuration Breaking Change](#swc-loose-mode-breaking-change-v910) below. This affects users who previously configured SWC in v9.0.0.
 
 ## New Features
@@ -130,7 +132,6 @@ import * as styles from './Component.module.css';
 **Migration Options:**
 
 1. **Update your code** (Recommended):
-
    - JavaScript: Change to named imports (`import { className }`)
    - TypeScript: Change to namespace imports (`import * as styles`)
    - Kebab-case class names are automatically converted to camelCase

data/eslint.config.fast.js

@@ -0,0 +1,134 @@
+// Fast ESLint config for quick development feedback
+// Skips type-aware rules that require TypeScript compilation
+
+const { FlatCompat } = require("@eslint/eslintrc")
+const js = require("@eslint/js")
+const typescriptParser = require("@typescript-eslint/parser")
+const typescriptPlugin = require("@typescript-eslint/eslint-plugin")
+const jestPlugin = require("eslint-plugin-jest")
+const prettierConfig = require("eslint-config-prettier")
+
+const compat = new FlatCompat({
+  baseDirectory: __dirname,
+  recommendedConfig: js.configs.recommended
+})
+
+module.exports = [
+  // Global ignores (replaces .eslintignore)
+  {
+    ignores: [
+      "lib/**",
+      "**/node_modules/**",
+      "vendor/**",
+      "spec/**",
+      "package/**" // TODO: Remove after issue #644 is resolved (lints package/ TS source files)
+    ]
+  },
+
+  // Base config for all JS files
+  ...compat.extends("airbnb"),
+  {
+    languageOptions: {
+      ecmaVersion: 2020,
+      sourceType: "module",
+      globals: {
+        // Browser globals
+        window: "readonly",
+        document: "readonly",
+        navigator: "readonly",
+        console: "readonly",
+        // Node globals
+        process: "readonly",
+        __dirname: "readonly",
+        __filename: "readonly",
+        module: "readonly",
+        require: "readonly",
+        exports: "readonly",
+        global: "readonly",
+        Buffer: "readonly"
+      }
+    },
+    rules: {
+      // Webpack handles module resolution, not ESLint
+      "import/no-unresolved": "off",
+      // Allow importing devDependencies in config/test files
+      "import/no-extraneous-dependencies": "off",
+      // TypeScript handles extensions, not needed for JS imports
+      "import/extensions": "off",
+      indent: ["error", 2]
+    },
+    settings: {
+      react: {
+        // Suppress "react package not installed" warning
+        // This project doesn't use React but airbnb config requires react-plugin
+        version: "999.999.999"
+      }
+    }
+  },
+
+  // Jest test files
+  {
+    files: ["test/**"],
+    plugins: {
+      jest: jestPlugin
+    },
+    languageOptions: {
+      globals: {
+        ...jestPlugin.environments.globals.globals
+      }
+    },
+    rules: {
+      ...jestPlugin.configs.recommended.rules,
+      ...jestPlugin.configs.style.rules,
+      "global-require": "off",
+      "jest/prefer-called-with": "error",
+      "jest/no-conditional-in-test": "error",
+      "jest/no-test-return-statement": "error",
+      "jest/prefer-expect-resolves": "error",
+      "jest/require-to-throw-message": "error",
+      "jest/require-top-level-describe": "error",
+      "jest/prefer-hooks-on-top": "error",
+      "jest/prefer-lowercase-title": [
+        "error",
+        { ignoreTopLevelDescribe: true }
+      ],
+      "jest/prefer-spy-on": "error",
+      "jest/prefer-strict-equal": "error",
+      "jest/prefer-todo": "error"
+    }
+  },
+
+  // TypeScript files - fast mode without type-aware linting
+  {
+    files: ["**/*.ts", "**/*.tsx"],
+    languageOptions: {
+      parser: typescriptParser,
+      parserOptions: {
+        // No project specified - disables type-aware linting
+        ecmaVersion: 2020,
+        sourceType: "module"
+      }
+    },
+    plugins: {
+      "@typescript-eslint": typescriptPlugin
+    },
+    rules: {
+      ...typescriptPlugin.configs.recommended.rules,
+      // Same rules as main config minus type-aware ones
+      "import/no-unresolved": "off",
+      "import/no-extraneous-dependencies": "off",
+      "import/extensions": "off",
+      "no-use-before-define": "off",
+      "@typescript-eslint/no-use-before-define": ["error"],
+      "@typescript-eslint/no-unused-vars": [
+        "error",
+        { argsIgnorePattern: "^_" }
+      ],
+      "@typescript-eslint/no-explicit-any": "error",
+      "@typescript-eslint/explicit-module-boundary-types": "off"
+    }
+  },
+
+  // Prettier config must be last to override other configs
+  prettierConfig
+]

data/eslint.config.js

@@ -0,0 +1,140 @@
+const { FlatCompat } = require("@eslint/eslintrc")
+const js = require("@eslint/js")
+const typescriptParser = require("@typescript-eslint/parser")
+const typescriptPlugin = require("@typescript-eslint/eslint-plugin")
+const jestPlugin = require("eslint-plugin-jest")
+const prettierConfig = require("eslint-config-prettier")
+
+const compat = new FlatCompat({
+  baseDirectory: __dirname,
+  recommendedConfig: js.configs.recommended
+})
+
+module.exports = [
+  // Global ignores (replaces .eslintignore)
+  {
+    ignores: [
+      "lib/**",
+      "**/node_modules/**",
+      "vendor/**",
+      "spec/**",
+      "package/**" // TODO: Remove after issue #644 is resolved (lints package/ TS source files)
+    ]
+  },
+
+  // Base config for all JS files
+  ...compat.extends("airbnb"),
+  {
+    languageOptions: {
+      ecmaVersion: 2020,
+      sourceType: "module",
+      globals: {
+        // Browser globals
+        window: "readonly",
+        document: "readonly",
+        navigator: "readonly",
+        console: "readonly",
+        // Node globals
+        process: "readonly",
+        __dirname: "readonly",
+        __filename: "readonly",
+        module: "readonly",
+        require: "readonly",
+        exports: "readonly",
+        global: "readonly",
+        Buffer: "readonly"
+      }
+    },
+    rules: {
+      // Webpack handles module resolution, not ESLint
+      "import/no-unresolved": "off",
+      // Allow importing devDependencies in config/test files
+      "import/no-extraneous-dependencies": "off",
+      // TypeScript handles extensions, not needed for JS imports
+      "import/extensions": "off",
+      indent: ["error", 2]
+    },
+    settings: {
+      react: {
+        // Suppress "react package not installed" warning
+        // This project doesn't use React but airbnb config requires react-plugin
+        version: "999.999.999"
+      }
+    }
+  },
+
+  // Jest test files
+  {
+    files: ["test/**"],
+    plugins: {
+      jest: jestPlugin
+    },
+    languageOptions: {
+      globals: {
+        ...jestPlugin.environments.globals.globals
+      }
+    },
+    rules: {
+      ...jestPlugin.configs.recommended.rules,
+      ...jestPlugin.configs.style.rules,
+      "global-require": "off",
+      "jest/prefer-called-with": "error",
+      "jest/no-conditional-in-test": "error",
+      "jest/no-test-return-statement": "error",
+      "jest/prefer-expect-resolves": "error",
+      "jest/require-to-throw-message": "error",
+      "jest/require-top-level-describe": "error",
+      "jest/prefer-hooks-on-top": "error",
+      "jest/prefer-lowercase-title": [
+        "error",
+        { ignoreTopLevelDescribe: true }
+      ],
+      "jest/prefer-spy-on": "error",
+      "jest/prefer-strict-equal": "error",
+      "jest/prefer-todo": "error"
+    }
+  },
+
+  // TypeScript files
+  {
+    files: ["**/*.ts", "**/*.tsx"],
+    languageOptions: {
+      parser: typescriptParser,
+      parserOptions: {
+        // Enables type-aware linting for better type safety
+        // Note: This can slow down linting on large codebases
+        // Consider using --cache flag with ESLint if performance degrades
+        project: "./tsconfig.eslint.json",
+        tsconfigRootDir: __dirname
+      }
+    },
+    plugins: {
+      "@typescript-eslint": typescriptPlugin
+    },
+    rules: {
+      ...typescriptPlugin.configs.recommended.rules,
+      ...typescriptPlugin.configs["recommended-requiring-type-checking"].rules,
+      // TypeScript compiler handles module resolution
+      "import/no-unresolved": "off",
+      // Allow importing devDependencies in TypeScript files
+      "import/no-extraneous-dependencies": "off",
+      // TypeScript handles file extensions via moduleResolution
+      "import/extensions": "off",
+      // Disable base rule in favor of TypeScript version
+      "no-use-before-define": "off",
+      "@typescript-eslint/no-use-before-define": ["error"],
+      // Allow unused vars if they start with underscore (convention for ignored params)
+      "@typescript-eslint/no-unused-vars": [
+        "error",
+        { argsIgnorePattern: "^_" }
+      ],
+      // Strict: no 'any' types allowed - use 'unknown' or specific types instead
+      "@typescript-eslint/no-explicit-any": "error",
+      // Allow implicit return types - TypeScript can infer them
+      "@typescript-eslint/explicit-module-boundary-types": "off"
+    }
+  },
+
+  // Prettier config must be last to override other configs
+  prettierConfig
+]

data/knip.ts

@@ -0,0 +1,54 @@
+import type { KnipConfig } from "knip"
+
+const config: KnipConfig = {
+  project: ["package/**/*.{ts,js}", "test/**/*.{ts,js}", "scripts/**/*.js"],
+  ignore: [
+    "package/**/*.d.ts",
+    "package/**/*.js",
+    "package/**/*.js.map",
+    "package/**/*.d.ts.map",
+    "test/fixtures/**",
+    "test/helpers.js", // Test utility file used by jest
+    "spec/**",
+    "gemfiles/**"
+  ],
+  ignoreBinaries: ["sed"],
+  ignoreDependencies: [
+    // These are peer dependencies that may not be directly imported
+    "@babel/core",
+    "@types/babel__core",
+    "@types/webpack",
+    "webpack-dev-server",
+    // Test/build tooling
+    "memory-fs",
+    "thenify",
+    // Used in type tests but not directly imported
+    "@rspack/plugin-react-refresh",
+    // CLI tools used by developers
+    "@rspack/cli",
+    "webpack-cli",
+    "husky",
+    // Optional dependencies used in webpack/rspack configs
+    "mini-css-extract-plugin",
+    "webpack-assets-manifest",
+    "webpack-subresource-integrity",
+    "rspack-manifest-plugin",
+    "sass-loader",
+    // Package merger utility
+    "@types/webpack-merge",
+    // Optional runtime dependencies
+    "ts-node",
+    "@pmmmwh/react-refresh-webpack-plugin",
+    // Optional peer dependencies referenced in code
+    "@rspack/core",
+    "@swc/core",
+    "babel-loader",
+    "compression-webpack-plugin",
+    "css-loader",
+    "esbuild-loader",
+    "swc-loader",
+    "webpack"
+  ]
+}
+
+export default config

data/lib/install/bin/export-bundler-config

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 // Minimal shim - all logic is in the TypeScript module
-const { run } = require('shakapacker/configExporter')
+const { run } = require("shakapacker/configExporter")
 
 run(process.argv.slice(2))
   .then((exitCode) => process.exit(exitCode))