React VS JSDoc

React Reviews

JSDoc Reviews

React mentions (775)

• Building Llama as a Service (LaaS)

  For this project, there is a frontend built with React hosted on Netlify, connected to the backend. - Source: dev.to / about 1 month ago

• Shared Tailwind Setup For Micro Frontend Application with Nx Workspace

  React: A JavaScript library for building user interfaces. - Source: dev.to / about 1 month ago

• How to stream data over HTTP using NextJS

  In this article we have seen a practical guide to using HTTP streaming for efficient data visualization in Next.js web applications. We have explored how create and customize an instance of ReadableStream, creating a Response object  specialization that accepts it as a result body. To test we have used a NextJS Route Handler. Additionally, to consume data chunk over http, we have developed a... - Source: dev.to / 2 months ago

• How to Create an Online Real-Time Bidding/Auction App

  React is a JavaScript library for building user interfaces. React gives you a template language and some function hooks to render HTML. Your bundles of HTML/JavaScript are called "components". - Source: dev.to / 3 months ago

• Top 20 Frontend Interview Questions With Answers

  When dealing with frontend libraries or frameworks such as React, using the Fullscreen API directly may be difficult because of the way the framework handles the DOM. In scenarios like this, you can opt for an external library, such as react-full-screen, to handle full-screen logic. This enables you to elegantly implement full-screen functionality on a React component. - Source: dev.to / 3 months ago

JSDoc mentions (49)

• Figma's Journey to TypeScript

  You may like JSDoc[1] if you just want some type-safety from the IDE without the compilation overhead. It’s done wonders when I’ve had to wrangle poorly commented legacy JavaScript codebases where most of the overhead is tracing what type the input parameters are. Personally, I’m impartial to TypeScript or JSDoc at this point. But I’d rather have either over plain JavaScript. [1] https://jsdoc.app/. - Source: Hacker News / 10 days ago

• Eloquent JavaScript 4th edition (2024)

  I wholeheartedly agree. At most, I introduce JSDoc[1] to newer developers as standardising how parameters and whatnot are commented at least gets you better documentation and _some_ safety without adding any TS knowledge overhead. [1] https://jsdoc.app/. - Source: Hacker News / 2 months ago

• Add typing to your Javascript code (without Typescript, kinda) ✍🏼

  The best way to do this, of course, is with JSDoc. But something I always found awkward about jsdoc is defining the object types in the same file. So, after a lot of reading, I found a way to combine JSDoc with declaration type files from Typescript. Let me give you an example:. - Source: dev.to / 3 months ago

• What is JSDoc and why you may not need typescript for your next project?

  There is a lot of specific symbols presented on the JSDOC specification that can be found here: https://jsdoc.app. - Source: dev.to / 4 months ago

• TypeScript Might Not Be Your God: Case Study of Migration from TS to JSDoc

  JSDoc is a specification for the comment format in JavaScript. This specification allows developers to describe the structure of their code, data types, function parameters, and much more using special comments. These comments can then be transformed into documentation using appropriate tools. - Source: dev.to / 4 months ago