non25

This could silently break perfectly fine demo REPLs for complex published components without package maintainer ever noticing, unless someone post issue in the repo. Sad state of things.

I've found that forcing source version by using `patch-package` yields good results without any effort. :slightly_smiling_face: https://github.com/nodeca/pica/issues/228#issuecomment-1477129545

I've been using this branch for like a month, haven't found something that would drive me off. Sadly it can't successfully replace css when using `svelte-pathfinder` as a router. Here's...

It seems that the approach of replacing just css doesn't work well with conditional markup. Toggling conditional markup after HMR css update results in no css for that markup. Will...

This is known complex types binding behavior. Nothing to do with slotting. Change to primitive like number and it will work once. **Workarounds** Binding arrays: use immutable in child component...

Thanks for bringing this up! :+1: I see two problems here: :one: We can't provide our own stripped down nodes, since plugins like `MarkdownShortcutsPlugin` internally hard-depend on default nodes due...

Hit this issue too. Here's [the solution](https://github.com/sveltejs/svelte-loader/pull/240). :slightly_smiling_face:

For style tag image links there are two ways: 1. HMR compatible: implement `file-loader`-like functionality using `postcss-url` and taking inspiration from `css-loader` - https://github.com/postcss/postcss-url#url-function 2. HMR incompatible: use `emitCss: true`...

Now it checks automatically. `this.emitFile` is not available in loaders spawned by `thread-loader`, so I'm using that.

So what do you think guys? I think adding this feature could be helpful. In default webpack configs it won't do anything, but people can start to experiment with `thread-loader`...