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
ignoreList is part of sourcemap spec and supported in chrome devtools, even it can be implemented in user side like next.js's implementation but it will introduce extra performance cost especially in Rspack, if it's implemented in sourceMapDevtoolPlugin, rspack can also provide same functionality with best performance.
What is the expected behavior?
support ignoreList option in sourcemapDevtoolPlugin What is motivation or use case for adding/changing the behavior?
follow sourcemap spec and provide same api for rspack & webpack with performant implementation How should this be implemented in your opinion?
nearly same as next's implementation but no need to introduce extra processAssets hook call Are you willing to work on this yourself?
yes
The text was updated successfully, but these errors were encountered:
@hardfist how you are trying to approach this my idea would be the to extend plugin option: adding a option of ignorelist and then integrating that during source map generation
@hardfist how you are trying to approach this my idea would be the to extend plugin option: adding a option of ignorelist and then integrating that during source map generation
Feature request
ignoreList
is part of sourcemap spec and supported in chrome devtools, even it can be implemented in user side like next.js's implementation but it will introduce extra performance cost especially in Rspack, if it's implemented in sourceMapDevtoolPlugin, rspack can also provide same functionality with best performance.What is the expected behavior?
support
ignoreList
option in sourcemapDevtoolPluginWhat is motivation or use case for adding/changing the behavior?
follow sourcemap spec and provide same api for rspack & webpack with performant implementation
How should this be implemented in your opinion?
nearly same as next's implementation but no need to introduce extra processAssets hook call
Are you willing to work on this yourself?
yes
The text was updated successfully, but these errors were encountered: