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
As you've already discovered @briangann this isn't to do with package managers. Based on the logs I'm inclined to think it's due to the changes in the webpack config which enable lazy loading and prevent the additional webpack runtimes from conflicting.
briangann
changed the title
yarn v3 creates source map files with plugin-id included in webpack path
new plugin-tools creates source map files with plugin-id included in webpack path
Oct 26, 2023
when using yarn v3/v4 (and any other package manager), the source map file ends up with paths like this:
the sourcediff code is only removing the leading
webpack://
which results in the tool reporting the source does not matchthis was encountered using the standard plugin-tools environment but with yarn v3 in this repo https://github.com/briangann/grafana-gauge-panel/releases/tag/v2.0.0
The text was updated successfully, but these errors were encountered: