-
-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the relevant APIs of StatsError. #4339
Comments
Related #4326 |
This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
bump |
Most of StatsError fields had been aligned with webpack: export interface JsStatsError {
message: string
chunkName?: string
chunkEntry?: boolean
chunkInitial?: boolean
file?: string
moduleIdentifier?: string
moduleName?: string
moduleId?: string
chunkId?: string
details?: string
stack?: string
moduleTrace: Array<JsStatsModuleTrace>
} Cause the error handling of rspack on the rust side cannot be completely consistent with nodejs of webpack. Can these fields meet your needs? |
I will close this issue as completed. If you meet some problem again, please just reopen this. |
What problem does this feature solve?
see friendly-errors-webpack-plugin , We need to implement similar functionality. This functionality requires extracting information such as StatsError stack, moduleId, etc. Currently, the api for rspack StatsError is not perfect.
What does the proposed API of configuration look like?
like webpack StatsError
The text was updated successfully, but these errors were encountered: