Scott Rippey

Ha ha, been there, forgotten about plenty of my stuff :) I'd be happy to be a collaborator. This package is still useful, because there really isn't much else in...

Hi, I'm the developer for `next-router-mock`, and also a big fan of Cypress and Component testing. I'm eager to get Next 13 support, and I've started a PR to add...

@nklayman I think there's a common misconception that these devtools require app code changes. Once you run the "install" code (eg in the devtools console), the extension stays installed, even...

Let me investigate E9 and see what's different. I'm currently on E8 so thanks for letting me know ahead-of-time about this change!

Looking at the E9 source code, I can see how they've changed `BrowserWindow.addDevToolsExtension` to internally use `session.loadExtension`, but I still see all the same exact "persist the devtools between app...

I created `next-router-mock` to handle this, and it works well with Storybook. You can enable it globally via a decorator, or per-component via a context provider: https://www.npmjs.com/package/next-router-mock

The sample you posted does look correct! You've created a fragment with a conditional projection. This should be supported, here's the unit tests: https://github.com/FormidableLabs/groqd/blob/main/packages/groq-builder/src/commands/fragment.test.ts#L141-L198 Can you give me a little...

I'm running into similar performance issues. I'm attempting to make a reusable groq testing library, and for some queries across 1500 entries, it's taking 15+ seconds. These queries are perfectly...

@carbonrobot This PoC is complete. The approach worked great, but this only applies to the turbo refactor. I suggest we get this merged, as it vastly improves the turbo codebase....

@sedlukha I've been working hard to fix this, and I have a prerelease ready to test! There aren't huge changes in this version, but the documentation was difficult to get...