Skip to content

Conversation

@lforst
Copy link

@lforst lforst commented Apr 7, 2023

Ref: #191

Similar to #192, we now add debug ID injection to the Webpack plugin.

Note this needs tests. We will add them as a follow-up when we identified some quirks with the injection across all bundlers.

@lforst lforst requested review from AbhiPrasad, Lms24 and mydea April 7, 2023 11:12
"magic-string": "0.27.0",
"unplugin": "1.0.1"
"unplugin": "1.0.1",
"webpack-sources": "^3.2.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

m: should we hard pin? Also this doesn't change yarn.lock?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point. Added. The yarn lock didn't change because unplugin itself depended on the exact same version.

return;
}

compilation.updateAsset(fileName, () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to cache here? So we only inject once?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the cache inspired by webpack/webpack#15454

@lforst lforst mentioned this pull request Apr 7, 2023
@lforst lforst enabled auto-merge (squash) April 7, 2023 11:45
@lforst lforst merged commit f5db486 into main Apr 7, 2023
@lforst lforst deleted the lforst-webpack-debug-id branch April 7, 2023 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants