Enforcing Architectural Boundaries with Custom ESLint Rules
Stop relying on documentation to maintain project architecture. Learn how to write custom ESLint rules using AST visitors to programmatically enforce boundary constraints.
Loading…
ReadMeFeed / Community knowledge
#ast
Real questions. Useful conversations. Find the people who know your stack.
eslint
javascriptArchitecting a Secure Markdown-to-HTML Pipeline
Learn how to build a secure Markdown-to-HTML pipeline using an AST-based approach to prevent XSS, ReDoS, and parser crashes in production environments.
Enforcing Project-Specific Patterns with Custom ESLint Rules
Learn how to build and implement custom ESLint rules using the AST to enforce project-specific architectural patterns and automate code migrations.
Designing Custom Babel Plugins: AST Transformation Architecture
Learn how to architect custom Babel plugins using the visitor pattern and AST paths to avoid infinite loops and tree corruption during JavaScript transformations.
Babel Parser and Generator: AST Formatting Consistency
Babel operates on a pipeline that converts source code into an Abstract Syntax Tree (AST) via the parser and subsequently converts that AST back into code using the generator. While the AST captures the semantic structure of the JavaScript, the process of transpilation is inherently lossy regarding original source formatting. When complex AST transformations
CSS Formatting: Transitioning from Prettier to Biome AST-based output
Biome provides a unified toolchain for CSS formatting and linting, utilizing a deterministic AST-based approach to replace standalone tools like Prettier. While this architecture ensures consistent output regardless of input spacing, the transition involves moving from a separate configuration ecosystem to a centralized biome.json file. When migrating comple
biomeNested #if blocks inside macros produce unexpected AST ordering
Goal: Determine how nested conditional compilation interacts with macro expansion The Haxe compiler evaluates conditional compilation directives (#if, #elseif, #else) at compile‑time, but the interaction with macro‑based transformations is not fully specified. When complex nested #if blocks are expanded by a macro, the order in which the compiler evaluates t
haxeAST modification after parsing silently discarded by GCC
Problem Statement A GCC plugin registers a PLUGIN_ADD_DECL callback to inject a new function declaration after the language front‑end has finished parsing a source file. The documentation does not formally allow adding new AST nodes at this stage, and in practice GCC appears to drop the injected declaration without error. Unresolved Behavior While the plugin
Unexpected token in @babel/parser during optional chaining transformation
When processing modern JavaScript syntax in Babel 7.x, the @babel/parser component throws an "Unexpected token" error if it encounters optional chaining syntax without the appropriate plugin enabled. While enabling @babel/plugin-proposal-optional-chaining resolves the parsing failure, a configuration uncertainty arises when this is paired with @babel/plugin-