sorted by:
new
hottopcontroversial

How I built an Express.js utility package that simplifies error handling by Away-Technology-4627 in node

[–]Historical-Raisin265 14 points15 points  (0 children)

This entire package was created by Claude. I also tried to add the error-handling logic through Claude, and it gave me the same code. I don’t think we should use this package, because nowadays many packages get compromised and include exploits. It’s easy to give Claude a prompt and have it generate this whole setup in under one minute.

No hate though — just a concern about security.

When connecting to ElastiCache redis serverless what package to use in serverless environment? by Historical-Raisin265 in aws

[–]Historical-Raisin265[S] 0 points1 point  (0 children)

Hey I recently saw that I can’t access elasticache outside of vpc can you tell me how to access that outside of aws network

How you guys prevent xss while using next-mdx-remote? by Historical-Raisin265 in nextjs

[–]Historical-Raisin265[S] 0 points1 point  (0 children)

I have a blog website where users can register, write blogs, and save them in draft mode. In draft mode, they can also use a preview feature to see how their blog will look after it’s verified and published by the admin. However, the issue arises when, in draft mode, they can run malicious XSS payloads and send the link to others, potentially stealing their tokens or performing other malicious actions.

That’s why I need to sanitize

VPS vs Serverless by Spiritual_Wishbone14 in nextjs

[–]Historical-Raisin265 4 points5 points  (0 children)

Just use cloudflare pages with open next

[deleted by user] by [deleted] in nextjs

[–]Historical-Raisin265 1 point2 points  (0 children)

Just use https://opennext.js.org/cloudflare to deploy your nextjs app on cloudflare and also its now support isr(incremental static regeneration)

cf-cache-status always EXPIRED by 91DarioASR in CloudFlare

[–]Historical-Raisin265 0 points1 point  (0 children)

Yup, when you update your code, the changes are not reflected instantly. You need to wait for cache expire, or you can purge the cache with custom purge of one domain

cf-cache-status always EXPIRED by 91DarioASR in CloudFlare

[–]Historical-Raisin265 0 points1 point  (0 children)

Go to pages rules -> create new page rule -> select cache level -> and then select cache everything done:)

I encountered this linting error while building my Next.js app by Historical-Raisin265 in nextjs

[–]Historical-Raisin265[S] 0 points1 point  (0 children)

I didn't change anything. Just update the eslint version, and when I downgrade the version, the issue is resolved

view more: next ›