For the grepping aspect, https://github.com/google/zoekt is a powerful one-stop-shop. For the navigating, I don't know. SourceGraph maybe, but the linking is somewhat heuristic I assume, not compilation-graph powered. But maybe that changes or depends per language. - Source: Hacker News / over 2 years ago

Given the shoutouts to Burntsushi and Lemire this is almost certainly a bitmap trigram index based engine similar to https://github.com/google/zoekt The index is likely based on Roaring bitmaps, presumably https://github.com/RoaringBitmap/roaring-rs in this case. Nice architecture, exactly how I would have done it also. - Source: Hacker News / over 2 years ago

The latest index/search engine is https://github.com/google/zoekt. Source: almost 3 years ago

For ESLint + TypeScript ESLint, with the new flat config eslint.config.js:. - Source: dev.to / 21 days ago

Eslint: It analyzes our code to quickly find problems. We will use the default setup provided by Vite. - Source: dev.to / 24 days ago

A big part of my work revolves around JavaScript tooling, and as such it's important to keep an eye on the ecosystem and see where things are going. It's no secret that recently lots of projects are native-ying (??) parts of their codebase, or even rewriting them to native languages altogether. Esbuild is one of the first popular and successful examples of this, which was written in Go. Other examples are Rspack... - Source: dev.to / 27 days ago

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. - Source: dev.to / about 2 months ago

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency. - Source: dev.to / about 2 months ago