Closed samccone closed 3 years ago
I guess that's also a setup problem. Including tailwind in the main app.svelte will slow down things a lot. I think 1. because it goes through slower preprocessing 2. because all styles are server rendered and not delivered in a separate css file.
I wonder if it might be more useful to post this at https://github.com/snowpackjs/snowpack/discussions unless there's something SvelteKit-specific at play here.
unless there's something SvelteKit-specific at play here.
This is a good discussion to be had. Should we provide well-lit paths for svelte kit and assume responsibility for the best way to do things? As a consumer of SvelteKit the lines of responsibility are a bit blurry between
Spelling this out and documenting it should help better guide future issues and this class of discussion in a way that is scalable and determined, as compared to depending on the triagers personal thoughts.
WDYT?
@FredKSchott for visibility into this snowpack configuration setup question / potential latency footgun.
Assuming its not a Snowpack issue at this point, but happy to help if there's anything that we can do on our end / if it gets traced back into Snowpack. I know we've had our fair share of issues around CSS processors expecting to bundle everything together, which can be hard to manage in a single-file way.
I took a bit of a look at this. My best guess is that it's because @snowpack/plugin-postcss
starts a new process.
Yes, this was the thinking of Fred and I as well. I am fine closing this ticket out as it is not super actionable, beyond the fact that we might get a lot of questions about this when the repo is opened up, and thus need to provide since kind of guidance.
Describe the bug For a project add:
package.json
postcss.config.js
snowpack.config.js
now in a svelte component do
Observe that the save to reload speed go from instant to multiple seconds.