Ryan Christian
Ryan Christian
Edit: Problem was more widespread than I thought. **Describe the bug** CSS `@import` syntax only works with relative paths within the public directory. Anything else is a no-go. For example:...
**Describe the bug** WMR handles CSS imports from `node_modules` differently based on the current environment. Take the following for example ``` node_modules/ --foo/ ----package.json ----dist/ ------index.css ``` The `package.json` file...
**Describe the bug** WMR creates references to CSS stylesheets too early, before the CSS minification plugin runs, resulting in references to CSS files that no longer exist. In practice, this...
**Describe the bug** When using `yarn link` (and presumably `npm link` too) the cache WMR keeps means that when the package is rebuilt, the user is not using the up-to-date...
CSS relative imports are currently not updated after build. If the CSS file listed in my `index.html` say imports a `additional.css`, while the `style.css` gets copied to `dist/assets.style..css`, `additional.css` will...
I'm guessing that this is a bug based on how unintuitive (to me) it feels, but this could very well just be a lack of a feature. Apologies, not sure...
I know `exclude` and `include` are still quite new, so you may have this planned, but it would be nice for the stats to measure up against purely the included...
**Do you want to request a *feature* or report a *bug*?** Bug **What is the current/expected behavior?** I'd like vim-prettier to match the output of prettier, but it does not....
Partial fix for #321 By delaying `getSheet()` until AFTER `destroy()` has been called, we can ensure a fresh reference to sheet. Else `getSheet()` might create a reference to a ``...
Edit: Sorry in advance for this wall of text. In short, style tags can be become orphans after calling `setup()` multiple times, leading to flashes of unstyled content. This results...