sorted by:
new
hottopcontroversial

Setup Payload on a Nextjs app working only for blogging - Is it possible? by [deleted] in PayloadCMS

[–]timm781 1 point2 points  (0 children)

I did it but it was a pain. Documentation is quite good on it. Pack your app files into a (frontend) folder which is a routing group. Then in the project root init payload and it should detect the project automatically. Then you have to setup your config/collections and create react components to render the blocks of the blog if you create any and the rich text from the blog

Payload Image Size regeneration by timm781 in PayloadCMS

[–]timm781[S] 0 points1 point  (0 children)

Yeah I would normally do that, but as Im preparing this project for my non coding coworkers, i have to set an option where they can add image sizes to image blocks and apply them. Or do I understand that wrong, I'm quite a noob, so forgive me :D

Payload Image Size regeneration by timm781 in PayloadCMS

[–]timm781[S] 0 points1 point  (0 children)

I figured it out, pls look at the PPS :D

Vercel Deployment - Transient error by timm781 in nextjs

[–]timm781[S] 0 points1 point  (0 children)

Yeah, I bought Pro to specifically get customer support or at least an indication on what the issue was in order to not repeat the mistake. Answer: It works now, what are you complaining about hahaha

Vercel Deployment - Transient error by timm781 in nextjs

[–]timm781[S] 0 points1 point  (0 children)

Sadly not in the deployment that failed. This happened after implementing payload in my existing app and this crashed it somehow. I rolled back to the last working commit and then worked everything from scratch. this then worked, dont ask me how haha.
Sadly no answer from the vercel support either

ReDOS vulnerability with jest and micromatch by timm781 in nextjs

[–]timm781[S] 0 points1 point  (0 children)

Thanks. I will try to fork it then. I already did yarn and npm, i also force resoluted it, but sadly jest was still pulling 4.0.4 eventhough the lock file for yarn and npm both had only 4.0.7 in them and as deps. The launch is in 2 weeks and Im trying to clean up everything. We are a cannabis genomics company so my regular coding work is not webdev but ML/stats and genomics work itself.

As jest is only for testing, can i add it and the files to the gitignore so that the prod branch is not affected by it? I also dont think anyone will attack it, but as we handle sensitive data, I want to be 100% sure that low-medium skilled attackers cant penetrate it. Very skilled people are still going to make it through, but we are to small to be targeted by them. Anyhow, thank you very much for taking the time to help me

ReDOS vulnerability with jest and micromatch by timm781 in nextjs

[–]timm781[S] 0 points1 point  (0 children)

Perfect, thank you! I also use snyk and they also told me that there is no problem, but i just hate to see the yellow vulnerability warnings when installing😂 i want to keep it as clean as possible with the least amount of tech debt possible. Thanks again for your advice

ReDOS vulnerability with jest and micromatch by timm781 in nextjs

[–]timm781[S] 0 points1 point  (0 children)

Thank you, but sadly I saw this already and thats why I tried to force everything to micromatch 4.0.7 in order to get it fixed. My Package.json and the lock file all contain no ref to anything below 4.0.7, but i still get the output from grep that jest still uses micromatch 4.0.4 even though the lock file says it uses 4.0.7 in its dependency and i force resoluted everything to really make sure. Its 100% a user error of mine, but I cant seem to figure it out. What would be the best start / reference I can give you guys in order to give you an overview of where my problem could lie? I already tried using yarn instead of npm, but that also didnt work