This repository has been archived by the owner on Jun 25, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐛 Bug Fix
Problem
related to apache/superset#7058
The root cause ends up being the
sideEffects: true
that is set in eachpackage.json
.webpack
inproduction
mode uses this to determine if the package has any side effects and when it is declaredfalse
, it (via treeshaking) drops the file that does not export anything, includingcss
. Treeshaking only applies toesm
so when importinglib
it works fine.Solution
Setting
sideEffects: ["*.css"]
seems to solve the problem.This is an alternative solution to #55 and subset of #56.
Reference
https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free