-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[10.0.0-dev] Dynamic imports leads to empty CSS bundles #2204
Comments
Merged
I have removed dynamic imports until the release of Webpack 5 (which will fix this issue). |
Emanuel-23
referenced
this issue
Aug 9, 2020
- Refactor default styles and scripts - Clean up default view markup - Change `Title.php` to `Post.php` to suggest a more organized workflow (Supersedes #2320) - Create an `App` composer to show an example of a global variable - Add `align-wide` and `responsive-embeds` to `add_theme_support` by default - Remove deprecated `soil-jquery-cdn` from `add_theme_support` - Clean up docblocks project-wide - Update linting to match the latest PSR-12 standards (e.g. the license docblocks) - Add an appropriate `#app` wrapper to make the project ready for frameworks like Vue - Add `laravel-mix-purgecss` for purgeCSS in production - Add `laravel-mix-copy-watched` for asset watching & versioning - Add `laravel-mix-wp-blocks` to handle compiling blocks - Reduce the footprint of the default `webpack.mix.js` - Append filetypes to asset names - Add default block editor assets - Add handling for the WordPress asset manifest - Remove visual editor styling (Fixes #2269) - Add sensible default styles and folders - Remove unused `phpcs.xml` - Move `sage-directives` and `sage-svg` to suggests - Bump dependencies - Add Brandon Nifong as an author - Change license URI to https - Remove unused function namespaces from setup.php - Append filetypes to asset names - Add default block editor assets - Add handling for the WordPress asset manifest - Ignore dist when running phpcs - Change the search input class the the WP default
@Log1x now that webpack 5 is out, is there any plan to resolve this issue, or work I can do to help implement webpack 5? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In 10.0.0-dev the Dynamic Imports commit #2190 leads to empty CSS bundles.
Steps to reproduce
npm install; npm run build
Expected behavior:
Actual behavior:
Reproduces how often:
100%
Versions
Additional information
I can confirm it works if I either remove
extract()
or remove the dynamic import.Upstream issues:
Release notes
The text was updated successfully, but these errors were encountered: