Vite Reviews

node-sass Reviews

Vite mentions (486)

• History of JavaScript: Browser wars, ECMAScript, Node.js, TypeScript, and React

  This idea led to the creation of Vite (French for "fast" — Ed.). Unlike traditional tools, Vite's development server didn't waste time bundling the entire project at startup. Instead, it sent source files directly to the browser like ES modules do, while using esbuild, a Go-based bundler, to pre-bundle dependencies from node_modules. As a result, the time required to initiate these large projects was reduced to... - Source: dev.to / 19 days ago

• Dead Code kills silently

  This article presents a bunch of ways how to find unused code, remove it, and configure tools and bundler to prevent dead code in the future. Sections for bundler are based on set of Vite, which under the hood delegates to Rollup in production. - Source: dev.to / 25 days ago

• TanStack Start vs Next.js: The Server Components Showdown That Actually Matters [2026]

  As Tanner Linsley, creator of TanStack, has explained, TanStack Start and its server components are designed to be "additive" to React — not a replacement for its core primitives. They're framework-agnostic and built on Vite. You opt into server-side capabilities when you need them, not because the framework demands it. - Source: dev.to / 3 months ago

• Zero-config Cesium.js in Vite — introducing vite-plugin-cesium-engine

  If you've ever tried to use CesiumJS with Vite, you know the ritual. Before you can render a globe you have to:. - Source: dev.to / 4 months ago

• VoidZero is driving the unification of the Javascript ecosystem

  VoidZero launch week is drawing to a close, and the world of Javascript development has just been given a significant boost. If you follow developments in build tools, you’ll know that fragmentation is rife, and that it’s difficult to stay at the cutting edge without using the best tool for each task. With the latest announcements regarding Vite, Oxlint and Vitest, Evan You team is taking a major step towards the... - Source: dev.to / 4 months ago

node-sass mentions (3)

• Use TailwindCSS prefixes for shared design system components

  For many years, Culture Amp took the second option, and distributed shared components without compiled CSS. This meant that every app that consumed shared components needed to include the necessary CSS build tooling – at that time CSS Modules and node-sass – with a compatible version and configuration. This was relatively easy to set up, but over time proved difficult to maintain. When node-sass was deprecated in... - Source: dev.to / over 2 years ago

• Syncfusion Essential Studio 2022 Volume 2 Is Here!

  ES 2 component Sass files are compiled using dart Sass instead of node-sass. This change was made because node-sass has been deprecated. Source: about 4 years ago

• Fetching Yelp API via Netlify Function with React.js

  I will deal with SCSS later, in separate blog entry. For here and now, just to make sure everything is working correctly, I need to apply some possibly simplest style to my boilerplate code. To transpile SCSS to CSS, I need to install node-sass package. Version 6.0.0 just came out a few days ago, but for a sake of any possible compatibility issues, I'll install previous version which is 5.0.0:. - Source: dev.to / about 5 years ago