5 ms·
Remix has the exact same issue unfortunately: https://remix.run/docs/en/v1/guides/constraints https://remix.run/docs/en/v1/guides/constraints
by Widdershin 4y ago
Remix has the exact same issue unfortunately: https://remix.run/docs/en/v1/guides/constraints https://remix.run/docs/en/v1/guides/constraints
- DangitBobby 4y agoYep. But it does a pretty good job of communicating where the boundaries are and telling you when you've crossed them. It's not even close to a deal breaker.
- Widdershin 4y agoUnfortunately that hasn’t been my experience. I learned about this problem after helping a very confused Remix user overcome this issue. I will give kudos to Remix for having a good docs page about this, something Next.js could do better (unless I just couldn’t find the docs). Also just wanted to say that I love your username.
- DangitBobby 4y agoI agree that the lines are a bit more unclear in practice and in the documentation. It genuinely takes some experimentation. That said, I think Next.js has a good reputation for good reason. And thank you!
- dimgl 4y agoThis actually bit me multiple times. I started leaking server-side code to the client, which completely turned me off. Also I've been in several arguments with Remix community members as to why middleware is necessary for server-side frameworks and why there needs to be a global state option. I was going to evangelize them at my current gig... thankful that I didn't go down that route and made my own prototypes. There are solutions (such as implementing your own caching layer) but ugh, why.
- chrisweekly 4y agoI'm very interested to hear more about those arguments w/ the Remix community; got links to share? Re: leaking server code to the client, so far I've been well-served by the recommended preventative measures: audits for inadvertent side-effects, and/or ".server.tsx" filenames as needed. But your experience here may be more extensive. Could you expand on "made my own prototypes"?