Christoph Bratschi
Christoph Bratschi
Could be related to: https://github.com/vercel/next.js/issues/25852 https://github.com/vercel/next.js/discussions/35637 A pure JavaScript version would be the easiest way to use this in a Next.js SSR component.
Ported the code to TypeScript for anyone interested: https://gist.github.com/cbratschi/a98c3b6270caa561c051af7cb17edb8b However, data is larger than a inlined data URL image and there was some banding.
Same issue on Node.js v20.11.1 and Next.js 14.1.4. npm just returns "Error: command failed" without any further details. It works fine without cluster mode.
@jacobsfletch yes, still happens with the 2.x version from today.
Checked this again and in generateTitle we returned doc.title instead of doc.title.value. It works now fine.
I recommend using file system locking or an object cache with such a feature. With multiple parallel running PHP processes this is still an issue and not solved by closing...
Read about the workaround on Discord: ``` npx create-payload-app@beta --use-npm ``` I am not a yarn user but for one project it was installed. This was causing the installer to...
Unfortunately there are many issues with object caches in combination with WPML. We tried multiple of them and always had problems, such as showing old translations or 404 redirects on...
@monolithed I ended up writing my own img component. Just ignore the TypeScript warning that next/image should be used.
@monolithed This is a company project and I cannot share any source code. We ported our current logic from our web platform to Next.js. Yes, we use a lot of...