-
Notifications
You must be signed in to change notification settings - Fork 72
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
"Extracting CSS" section in README.md should mention mini-css-extract-plugin #95
Comments
Exactly what I thought! |
Hi, I'm having a similar issue with how to use the EmitCss plugin along side svelte-loader. I just started doing production builds and all my styling has disappeared, but mini-css-extract-plugin doesn't seem to be creating corresponding css files for my pages. I've essentially got a bunch of SPAs which stitch together using server side routing, e.g. one JS per page, consisting of a single top level svelte component, then embedded into a HTML template (using pug) and delivered to the client as if it was a regular SPA. The problem is, that in production mode, none of my CSS gets emitted i.e. what I want is something like "signup.js" which would be the svelte javascript for the signup page, and a corresponding "signup.css" which can be embedded along side it. I've included parts of my webpack config below
As you can see I use a flag I'd be happy to write a readme update on this, if I can get it working, so that other people don't fall into this pit. (P.s. the reason I'm not using Sapper is because I tried to move to sapper, but couldn't get it to work with webpack, and when I asked in the discord everyone was like "use rollup") Sorry to be a bother and thanks in advance |
I was being an idiot, and I had |
The mentioned section should replace
extract-text-webpack-plugin
withmini-css-extract-plugin
asextract-text-webpack-plugin
is deprecated sincewebpack v4
.The text was updated successfully, but these errors were encountered: