-
-
Notifications
You must be signed in to change notification settings - Fork 781
Description
System Info
System:
OS: Windows 10 10.0.26100
CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
Memory: 24.87 GB / 63.91 GB
Binaries:
Node: 20.15.1 - ~\AppData\Local\fnm_multishells\78476_1741742697525\node.EXE
npm: 10.7.0 - ~\AppData\Local\fnm_multishells\78476_1741742697525\npm.CMD
pnpm: 9.9.0 - ~\AppData\Local\pnpm\pnpm.EXE
Browsers:
Edge: Spartan (38.35), Chromium (38.3), ChromiumDev (38.21)
Internet Explorer: 11.0.26100.1882
npmPackages:
@rspack/cli: ^1.2.8 => 1.2.8
@rspack/core: ^1.2.8 => 1.2.8
Details
I was testing out rspack moving from Webpack and I use val-loader together with https://www.npmjs.com/package/val-loader-modernizr
When I execute the build, I get this error:
> rspack -c rspack.config.js
ERROR in ./scripts/.modernizrrc
× Error: on JsLoaderContext.additionalData
│ at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Rspack compiled with 1 error in 58.20 sThe time taken probably reflects my ts-loader as it takes about 60 seconds to typecheck.
The rule looks like:
{
test: /\.modernizrrc$/,
use: [{
loader: 'val-loader',
options: {
executableFile: require.resolve('val-loader-modernizr')
}
}]
}Note: In ESM module in repro, I use fileURLToPath(import.meta.resolve("val-loader-modernizr")) but in my project I'm still using CommonJS config.
Reproduce link
https://github.com/kamranayub/rspack-bug-val-loader
Reproduce Steps
pnpm install(orbun install)npm run buildor (pnpm run build)- Observe error
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels