Sebastian Kasanzew

Maybe this is a good alternative to this package. But I didn't have the time to try it yet. https://github.com/tanstack/virtual

I've reproduced the issue in react with svg build with visx: https://codesandbox.io/s/visx-html2canvas-issue-l7ox9x?file=/src/App.js Does anyone have an idea, how to fix it?

This prevents me from using [Middleware](https://nextjs.org/docs/pages/building-your-application/routing/middleware) in a Next.js project, because this plugin instruments all files, including `middleware.ts`. But Middleware uses the edge runtime, instead of nodejs and prohibits [eval](https://nextjs.org/docs/app/api-reference/edge#unsupported-apis)....

After some trial and error I found out that this issue got resolved for me after downgrading to Node `v16.19.1`. I had the `fetch failed` error with Node `v18.15.0`, `[email protected]`...

I got the same error and also thought, it's because of this package. But actually the error occurs, when I update `@types/react` to v18.2.20. With `@types/react` v18.2.19 and `@material-tailwind/react` v2.1.0...

I've reproduced the issue here: https://codesandbox.io/p/sandbox/next-safe-middleware-issue-84-6ywgjy Still trying to figure out, why the `csp-manifest.json` cannot be fetched. It uses the correct URL, I get a JSON back if I paste...

I got the same error. I modified the function `parseDefinition()` in the file `dist/src/parser.js` as followed. That fixed the issue for me: before: ```js /* ... */ visitedDefs.push({ name: definition.name,...