John Schottler

A workaround was pointed out here that worked for me: https://github.com/EmilTholin/svelte-routing/issues/41#issuecomment-503462045 The `activeRoute` property on the `ROUTER` context is a store. The store has `uri`, `params`, etc.

As a workaround, you can import it directly from node_modules like kysonic points out here: https://github.com/EmilTholin/svelte-routing/issues/41 ``` import {getContext} from 'svelte'; import {ROUTER} from 'svelte-routing/src/contexts'; const { activeRoute } =...

Seems like webpack's native `output.clean` actually handles what this plugin does. Wonder if this plugin can be deprecated? https://webpack.js.org/configuration/output/#outputclean

hmm, that link takes me to something that looks like this: 

Can you provide a more detailed example?

We're just using webpack, so all of our component tests work by just using @dvopalecky's suggestion above. I created a PR for that change, so that it will work for...

Would `svelte:component` be what you're looking for? https://svelte.dev/docs#svelte_component Can pass a comonent type in and render and instance of it.

Oh sorry, I misunderstood what you were asking. The way I've been doing it is by wrapping the component(s) I want to test in a wrapper components with some example...

Makes it really nice when building up a component too. Kind of like an interactive style guide that shows how to use your components and what the expected behavior of...

Oh, sorry about that--had copied/pasted my comment on the closed issue I linked to and didn't see I missed the image.