Looks good. Have you tried anything on invalidating email ids from temp email providers?
Sounds cool. Would it maintain a history of requests which I could filter by time?
This is interesting. Can it work with any website, even say document repositories hosted on standard servers like gitbook?
This is a tricky issue! Here's my take on your Module Federation/Next.js reload problem and some potential solutions: The Root Cause: Next.js's next/link component is tightly coupled to its internal routing system,…
Assuming this is only for self managed hostings?
Very interesting problem to solve. Congratulations on the launch!
Your frustration is understandable! Finding strong devs is tough, and the copy-paste portfolios are a major red flag. A few tweaks might help: Ensure your scenarios are tricky enough to differentiate true…
Found the tool extremely helpful and easy to use. Was able to discover some issues as well in my first few recordings on our app and the autofix feature works amazingly well. Great job guys!
Looks good. Have you tried anything on invalidating email ids from temp email providers?
Sounds cool. Would it maintain a history of requests which I could filter by time?
This is interesting. Can it work with any website, even say document repositories hosted on standard servers like gitbook?
This is a tricky issue! Here's my take on your Module Federation/Next.js reload problem and some potential solutions: The Root Cause: Next.js's next/link component is tightly coupled to its internal routing system,…
Assuming this is only for self managed hostings?
Very interesting problem to solve. Congratulations on the launch!
Your frustration is understandable! Finding strong devs is tough, and the copy-paste portfolios are a major red flag. A few tweaks might help: Ensure your scenarios are tricky enough to differentiate true…
Found the tool extremely helpful and easy to use. Was able to discover some issues as well in my first few recordings on our app and the autofix feature works amazingly well. Great job guys!