Closed chriszrc closed 5 years ago
I'm getting the same result on an inherited project, it uses just 1 spinner and is the largest dependency.
nvm I just imported the component directly and it fixed it
// before
import {PixelSpinner} from 'epic-spinners'
// after
import PixelSpinner from 'epic-spinners/src/components/lib/PixelSpinner'
@RDelorier yay! confirmed, I see it working here on my project as well-
Importing file is the only way to get correct tree-shaking from current build.
Added the instruction to the docs.
We also plan more fundamental solution for the problem and it's moved to #32
If I include a single spinner in my vue cli 3 project:
This is what I see in the source-map explorer after executing a build:prod
I would have expected that given I'm only including a single component, and that component doesn't depend on the other spinners, that I'd be able to import it singly?