Next.js VS Radix Primitives

Next.js Reviews

Radix Primitives Reviews

Next.js mentions (929)

• Transforming API requests and responses in Laravel 11 - The easy way

  I've been working on an application using Next.js on the front-end and Laravel on the back-end as a traditional REST API. As you may know, snake_case is the naming convention for variable and function names in PHP, while camelCase is the naming convention in JavaScript. My database tables and columns use snake_case as well, so I stuck to that design. - Source: dev.to / 8 days ago

• Integration of Facial Authentication (Recognition) on an Employee Dashboard using FACEIO, Next.js & Typescript.

  Basic understanding of Next.js and Typescript. - Source: dev.to / 10 days ago

• Netlify Dynamic Site Challenge: Make Your Favorite Image Collection 🎆

  I have built a dynamic image gallery using Pexels API and Next.js. Landing page fetches a list of curated images from Pexels API. User can click on the image to view in detailed mode. User can also use the search functionality to find images of any topic. Moreover, authenticated users are allowed to like any image and create his/her own collection of liked images. From the user profile page, user can upload... - Source: dev.to / 9 days ago

• How I Achieved Maintanability, and Scalability in My Projects

  We took our time evaluating different options and ultimately landed on a focused set of technologies: Next.js, TypeScript, Redux Toolkit, SASS, and Axios. This combination offers a powerful and manageable foundation for our project, avoiding the pitfalls of an overly complex tech stack. - Source: dev.to / 11 days ago

• Monorepo Backend Application with Bundled Packages

  The frustrating part is, when you're working on a Next.js project within a monorepo, adding your module to the transpilePackages entry in the configuration is all it takes. However, for a backend applications with a custom build step, it's not as straightforward. - Source: dev.to / 12 days ago

Radix Primitives mentions (5)

• React: Build your own composable, headless components

  Fast forward to a week ago, I cloned the Reach UI and Radix UI codebase and started exploring. Large codebases are always difficult to comprehend. With some digging around and reverse engineering, I was able to create the first component listed in the Reach UI docs, the Accordion. - Source: dev.to / 4 months ago

• Currently in need of books or repo recommendations that covers intermediate-advanced concepts in react

  Radix UI Primitives - adopts good programming principles to make React components extendable and flexible. Source: almost 2 years ago

• I built a UI component library for React, would love some feedback

  I can also recommend using radix primitives and wrap your components around those https://github.com/radix-ui/primitives. Source: almost 2 years ago

• 2022 is the year of Design Systems

  RadixUI: it is a low-level UI component library focused on accessibility, customization and developer experience. (Source: https://github.com/radix-ui/primitives). - Source: dev.to / about 2 years ago

• Should you compile components before publishing them?

  We only use a few for each project and I want to version them separately. Kinda like [radix ui](https://github.com/radix-ui/primitives) does it. Source: over 2 years ago