ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Background Dart Sass 2.0 removed the legacy synchronous JavaScript API, requiring custom importers and functions to use the async-only API. This forces projects with custom Sass logic to adopt async compilation patterns, even for simple use cases. For low-traffic projects, the primary cost is developer time spent refactoring build tooling rather than computa
Goal Determine how to keep custom Grunt tasks functioning when running on Node.js 18+ while respecting the legacy this.async() contract. Constraints Grunt 1.6.1 core relies on the this.async() callback pattern; it does not natively accept Promise returns. Node.js 18+ emits unhandled rejection warnings for Promise-based code that is not awaited or caught, whi
Grunt executes tasks in a linear sequence without native support for transactional atomicity or state recovery. When a file-write task fails midway, the task runner typically terminates or continues via the --force flag, potentially leaving partial or corrupted files on disk. Because Grunt lacks a built-in retry mechanism for individual tasks, manual retryin
Goal: Determine why figwheel-main’s file‑watcher fails to trigger recompilation when a dependency file is modified, resulting in stale cached JavaScript output when using :optimizations :none. Constraints: The watcher relies on file modification timestamps; system clock adjustments or touching a file without changing its content can leave the cache unchanged
A project compiles Sass through a build tool (for example webpack with sass-loader, Vite, or a framework asset pipeline) on top of Dart Sass. The goal is to reliably diagnose why editing a partial pulled in via @use or @import sometimes leaves the emitted CSS unchanged until some cache is cleared. The uncertainty is which layer caches at all. Dart Sass itsel
Context Grunt's grunt.file.expand and grunt.file.expandMapping currently perform synchronous filesystem reads on every invocation with no internal caching. This design avoids stale results but can impose repeated I/O overhead when the same patterns are evaluated multiple times during a single build. Unresolved behavior The Grunt codebase has not introduced o
grunt
clojurescript
sass