nft

Summary Add location tracking to the function to capture where assets, dependencies, and imports are referenced in source code. This enables downstream tools (like bundlers and transformers) to rewrite asset references while preserving source maps and code structure. Motivation Currently, identifies which assets/dependencies a file uses but doesn't track where in the source code those references occur. This limits the ability to: 1. Transform asset references: Build tools that need to rewrite asset paths (e.g., Vite plugins, custom bundlers) must re-parse and duplicate nft's sophisticated detection heuristics 2. Generate accurate source maps: Without position information, transformations can't maintain proper source map mappings Use Case Vite/Rolldown/Esbuild Plugin for Asset Transformation Proposed API Enhanced Interface Example Usage Coverage I think that the following detection heuristics can be enhanced: Fully Trackable (13 cases): ✅ , , ✅ ESM / declarations ✅ Dynamic expressions ✅ function calls (readFileSync, readFile, etc.) ✅ functions (join, resolve) ✅ , references ✅ ✅ Special bindings (BINDINGS, NODE_GYP_BUILD, NBIND_INIT, etc.) Partially Trackable (3 cases): ⚠️ Glob patterns (, ) Can track the expression that triggered the glob Cannot track individual files discovered from filesystem Open Questions 1. Opt-in flag: Should location tracking be behind a feature flag to avoid performance overhead for users who don't need it? 2. Glob patterns: How should we represent assets discovered through glob patterns? Current proposal is to track the pattern expression but not individual files.