Eric Burel

@VladDubrovskis can you please share a working package.json? I struggle to find the right combination

Just linking @lifeiscontent excellent addon for Next.js router specifically: https://storybook.js.org/addons/storybook-addon-next-router I'll test that today but it sounds great, I've also opened a related discussion on supporting full pages: https://github.com/vercel/next.js/discussions/28290 Mocking...

> Hi all, I've been trying to experiment a bit with this as well. Has anyone figured out a more generic solution via webpack? I'm hoping to avoid an alias...

> Thanks for the response! We have a mono-repo with a package structure like this: > > ``` > packages/ > package-1/ > index.js > __mocks__/ > index.js > package-2/...

Sample code using evaluate: ```js test("display in a small container", async ({ page }) => { await page.goto("/debug-page") await page.evaluate(() => { const body = document.querySelector("body") if (body) { body.innerHTML...

I've been exploring Next.js codebase for an article about server context. In order to get access to more request information than headers and cookies, as far as I understand, a...

> @benweiser can you edit your post above to provide a detailed account of that particular use case? This may be taken into consideration when the team considers building this...

Hi, is this related to the error encountered in @leerob [SPA example](https://github.com/leerob/next-static-export-example/blob/4c8dac076b26289bf9ab48fe9cd4ef35bd7abea9/app/spa-post/%5Bid%5D/page.tsx)? The error message seems surprising, and params are meant to be obtained via page props rather than the...

@goerlitz starting step 3 and 4 I think you get confused: - move the code that needs "use client" into a separate file, for instance: ``` // app/datasets/[slug]/page.tsx export const...

You'd want to take a look at https://github.com/zeromq/zeromq.js/issues/384, similar issue. I got the development mode to work, using an `external`, and I am testing the bundle, though I suspect this...