Not able to console.log in NextJS 13
Alright so kind of a dumb question, but there's no such thing so here it goes. Building out a simple recipe store website, currently trying to display a single recipe, using the id slug to query my DB for it.
I guess the first thing I'm not understanding is why none of these console.logs are printing anywhere? They are neither in my browser console, nor in the terminal window where I'm running npm run dev.
The second problem is that the H2 that's supposed to render the recipe name isn't being rendered on the page, though I suspect I'll at least have a bit of an easier time figuring out what's going on with that if I can at least see these console.logs 😅...
encode uuid to be accepted by google
I'm querying google's calendar api and i get back some 400's due to invalid id. i read on their docs what they match and have concluded they don't support cuid (cuid uses letters up to z and google accept a-v), so i changed to uuid but i keep getting back 400 and so i tried removing the separating dashes to make it happy.
is there a proper way to do this encoding/decoding? right now i did a pretty nasty hack with regex (to remove when posting google's api) and split (to add them back when querying the api). the id's in my db uses prisma's generated uuid so they have dashes, hence i need the dashes in order to be able to match them.
tldr; what's the proper way to encode/decode uuid?...
Benchmarking slow LCP and TTI
I'm looking for advice on this, because I really don't have a mentor to turn to and I'm feeling pretty lost overall. I've detailed before that I'm refactoring a SPA made with CRA that is meant to replace an AngularJS app that was mounted inside a JSP and served as our previous "version" of this page. I've improved performance quite a bit compared to where it was, but I'm still seeing a rather large gap, and I'm trying to audit A) How much can I reasonably improve performance, and B) Where should I look for benefits at this point?
For a bit more context - because the old application is in a JSP, it gets served HTML from our server which contains a pre-computed JSON string that is parsed and added to the page's service. The new version lives in an S3 bucket and sends multiple requests out for data upon page load. I originally thought this was the primary source of difference remaining between the two applications, because naturally sending to a remote server for data will be slower than parsing JSON that is passed alongside HTML. However, I experimented with removing those calls and simply parsing out a hard-coded JSON string with data, and I'm still reading a significant difference in mobile score (around 56 for the new vs 80-85 for the old page).
When I profile the page (CPU 4x throttled, network fast 3G) I'm noticing a significant difference in the number of long tasks that appear to be falling under the umbrella of React-DOM vs the number that happen on the old AngularJS environment. I've attached screenshots of the trace, in case anything seems fishy. I genuinely don't really know how to interpret these results - does React-DOM often struggle when network/processing speeds are throttled, more so than this other app would?...
Are these Prisma models okay?
Hey I'm trying out prisma and I'm attempting to make a bug tracker. Just wondering if these models seem fine or if there's anything I can do to make them "better".
Most bug trackers have a bunch of different roles but I'm new to this so I'm keeping it simple with just a user and an admin (me). Then a project manager which is just the user who created the project so they wouldn't have a role the actual project would have a manager and a user would have a list of projects they manage I think?
For the user model I haven't hooked up NextAuth or anything yet so I'll probably have more fields when I get that far. Just trying to get the initial setup goin. I've seen examples with Account and User with a bunch of information that comes from NextAuth....
