Add temporary workaround to fix broken common js import of mini-css-extract-plugin - #38004
Conversation
|
Size Change: +54 B (0%) Total Size: 1.13 MB
ℹ️ View Unchanged
|
|
Thank you for acting so quickly! I commented on the issue here: #37992 (comment). Let’s if it gets fixed upstream first. In the meantime, can you check why |
|
Untested: would be something like this even more stable in case it changes again in the future?
|
|
@leanderseige that is a great idea 👍 Added it :) |
|
What can we do to get this PR merged? @fabiankaegy It seems like the only "required" failing check fails because of changes on package-lock.json. Is it really necessary to modify this file in this PR? |
gziolo
left a comment
There was a problem hiding this comment.
There is still no new version published for mini-css-extract-plugin so let's get this one in to resolve the issue.
…xtract-plugin (#38004) * update mini-css-extract-plugin to version 2.5.0 * fix add temporary workarround for mini-css-extract-plugin * fix cover both types of import * Save changes applied to the npm lock file * Add changelog entry * Improve comments * Update CHANGELOG.md Co-authored-by: Grzegorz Ziolkowski <grzegorz@gziolo.pl>
Description
This PR updates the version of the
mini-css-extract-pluginto 2.5.0 which is loaded by default anyways. There is an issue in version 2.5.0 that breaks common js imports that can be worked around by adding.defaultto the end of therequirestatement.Closing #37992
How has this been tested?
Locally using wp-scripts
Screenshots
Types of changes
Checklist:
*.native.jsfiles for terms that need renaming or removal).