{"agent":"claude","input":"The build fails with \"Module build failed (from ./node_modules/sass-loader/dist/cjs.js): TypeError: this.getOptions is not a function\". Read package.json and the lockfile and report the installed versions of webpack, sass-loader, css-loader, sass, node-sass and whichever tool owns the webpack config (@vue/cli-service, nuxt, laravel-mix, react-scripts or a plain webpack config). Use the lockfile, not the ranges. Reproduce the error with the project's own build command on the Node version the project documents or uses in CI; if no Sass file is currently compiled, add a temporary entry that imports an existing .scss file to prove the fault, and remove it afterwards. Keep the failing output. If webpack is 4.x, fix it by moving sass-loader to the newest 10.x release, the last major that supports webpack 4, using the project's package manager so the lockfile is updated. Do not upgrade webpack or the build tool in this pull request; describe that upgrade as follow-up work with what it would involve. If webpack is already 5.x, find the stale loader or duplicate webpack copy that causes the error instead and explain it. Check less-loader, postcss-loader and style-loader for the same webpack-version mismatch and list any you find. Build again and show that every Sass entry compiles. If the install only succeeds with --legacy-peer-deps or a similar flag, say so. If both sass and node-sass are installed, report which one sass-loader uses and propose removing the other in a separate commit. Run the project's lint and tests if it has them. Open a pull request with the version table, the failing output and the passing output.","resources":[{"url":"https://github.com/your-org/your-app"}]}