ancras

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, which expects to control the entire page. In a microfrontend architecture with Module Federation, you're essentially trying to run two routers (Next.js and your shell) simultaneously, leading to conflicts.

Possible Solutions: Client-Side Routing Alignment (Ideal): Shared Routing Library: If possible, strive for a unified routing solution between your React shell and Next.js microfrontend. Consider libraries like react-router that both can integrate with. This might require restructuring, but offers the cleanest long-term solution.

Custom Event Bus: If a shared router isn't feasible, create a lightweight event bus. When next/link triggers navigation within the Next.js app, emit an event. The shell can listen for this event and use its own routing mechanism to update the URL, preventing a full reload.

Next.js Configuration Tweaks: assetPrefix: If your Next.js app is hosted on a subpath, ensure the assetPrefix in your next.config.js is set correctly to avoid asset loading issues. basePath (Next.js 13+): Similar to assetPrefix, but for routing. This can help isolate the Next.js portion of your URL structure.

Strategic Link Handling: Conditional Rendering: For links within the Next.js microfrontend, continue using next/link. For links pointing outside to other microfrontends or the shell, use the shell's routing mechanism.

Also check Module Federation Version Compatibility: Ensure your versions of Next.js, React, and the Module Federation plugin are compatible.

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 problem-solvers. You can go beyond usual job boards: Explore Indie Hackers, GitHub, and Stack Overflow to find passionate devs. Networking is important - you can attend meetups and conferences related to your tech stack. Most likely to get good talent there with high intent. In general take-home assignments should be short & focused) - around 2-4 hours max and you can consider offering compensation. We need to keep refining our approach, and yes don't be afraid to sell your company's vision to attract the right talent!

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!