You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to #2573 workaround, I could have the reason property on modules' compilation stats.
But some fields are missing in RSPack reasons (JsStatsModuleReason) compared to webpack (StatsModuleReason type)
(I'm showing TS types which should be clearer for reporting)
Nice to have, especially helpful for tools like medusa which do consume alot of info about module reasons
lalexdotcom
changed the title
[Bug Report]: Stats module reasons compared to webpack (module is now moduleId, userRequest and other fields missing)
[Bug Report]: Stats module reasons compared to webpack (userRequest and other fields missing)
Apr 5, 2023
System Info
devcontainer
Details
Thanks to #2573 workaround, I could have the reason property on modules' compilation stats.
But some fields are missing in RSPack reasons (JsStatsModuleReason) compared to webpack (StatsModuleReason type)
(I'm showing TS types which should be clearer for reporting)
RSPack
Webpack
I'm mainly after the
userRequest
property, but others may be used...By the way, the(my bad, moduleId is there 😅)module
field is nowmoduleId
, shouldn't it be ISO with webpack for better interoperability?Reproduce link
https://github.com/lalexdotcom/rspack-bug-report rspack-module-reason-type
Reproduce Steps
!! Be sure to be on rspack-module-reason-type branch !!
npm install
npm run rspack-stats-output
npm run webpack-stats-output
The text was updated successfully, but these errors were encountered: