Full-stack developer making thetoolshed.xyz • social media-averse until I found Warpcast • thetoolshed.xyz/raphaelaviz
27 Followers
Is anyone else having incredibly slow compile time in Next.js 14+?
So...wife just bought this:
1. First job: english teacher. 2. College degree: Law. 3. Favorite non-work hobby: joininng my cats on whatever they're doing. 4. Introvert or extrovert: introvert.
Honestly, small conviniences like this on Next.js matter a lot to me. It takes basically no time at all to setup a custom 404 page. It doesn't even go on the to-do list 😅
It's UNBELIEVABLE how much this has done to frontend development
1/2 Some clarification on React / Next.js cache APIs for those who don't use React Query: React Cache Function: ◾ Terrible name, since it's only used for deduplication. ◾ It doesn't persist data across requests. ◾ Use it if you're calling the same function multiple times within the same render. Example: you need the data in multiple server components, so you can call the same function (wrapped in cache()) in different components instead of passing down props. Requests will be deduplicated and only one will actually be fired. Feels weird, but valid.
Cloudy/rainy Sunday yesterday. No grasses were touched (or even seen), so a lot of progress was made on Toolshed's text editor. The highlights are: * Added custom Callout extension, completely stolen from / inspired by paragraph.xyz. Shown in the video below. * Added keyboard shortcuts for Code Blocks and Callouts. * Added Tables, Columns, Font Size and Text Align features. * Added Table of Contents feature, although not sure where to put it on the UI yet (not a priority). Only one more thing left to do: file uploads inside the editor.