Scott Rippey

Closing as duplicate of #58 I'm still considering how to fix this.

I'm able to reproduce this with these bare minimal steps: ``` npm init -y npm i electron@3 spectron@5 node -e "new (require('spectron').Application)({ path: require('electron') }).start()" ``` This launches the main...

I'm able to workaround this issue by manually focusing the window: ``` await app.client.waitUntilWindowLoaded(); await app.client.waitUntil(async () => { await app.browserWindow.focus(); return await app.browserWindow.isFocused(); }); ``` This has to be...

I attempted to workaround this by comparing based on `ctime`, but unfortunately only `mtime` is stored in the cache. So ultimately, I went with the approach recommended in webpack's docs:...

Very cool, thanks for the info. I've successfully built the functionality I was looking for! Although I had little C++ or Obj-C experience, I was very pleased with your codebase,...

Unfortunately, Storybook does not have a per-story way to mock imported modules. I wish it did! But, there still might be a solution. I haven't tried this, but you should...

Yeah, here's why: the `MemoryRouterProvider` will only work with the `useRouter()` hook. It doesn't use the singleton router, it creates its own. So you can't use it to mock the...

My idea is this: I could add a `singleton` property to the `MemoryRouterProvider`, which would tell it to use the singleton router instead of creating its own. When the component...

Thank you for the explanation! That's a perfectly valid use-case for using the singleton router, so I totally get it. I'm thinking, it might actually be best for me to...

I hadn't thought of your use-case before, but now I'm realizing that it's a totally valid, great approach for performance. Using the singleton router (for components that don't need to...