feat(core): Expose rewriteSources top level option #20142
feat(core): Expose rewriteSources top level option #20142
rewriteSources top level option #20142Conversation
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Core
Deps
Other
Bug Fixes 🐛Core
Other
Internal Changes 🔧Core
Deps
Other
🤖 This preview updates automatically when you update the PR. |
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
Lms24
left a comment
There was a problem hiding this comment.
Thanks for adding this!
Just to confirm: We already bumped the plugins to the supported version? And sveltekit uses the interface from core directly?
| ? fallbackFilesToDelete | ||
| : undefined, | ||
| rewriteSources: (source: string) => normalizePath(source), | ||
| rewriteSources: sourcemapsOptions.rewriteSources ?? ((source: string) => normalizePath(source)), |
There was a problem hiding this comment.
Super-L: Just because I see the pattern here now:
| rewriteSources: sourcemapsOptions.rewriteSources ?? ((source: string) => normalizePath(source)), | |
| rewriteSources: sourcemapsOptions.rewriteSources ?? normalizePath |
This should have the same outcome
rewriteSourcesto the baseSourceMapsOptionsinterface so users can customize source path rewriting without theunstable_*escape hatchbundler plugins ref getsentry/sentry-javascript-bundler-plugins#908
closes #20028