{"version":"2.1.271","anchor":"fswatch-reliability-probe-built-no-in-bundle-caller-found","canonical_anchor":"fswatch-reliability-probe-built-no-in-bundle-caller-found","heading":"fs.watch reliability probe: built, no in-bundle caller found","tier":"soon","area":"File Watching","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/fswatch-reliability-probe-built-no-in-bundle-caller-found","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### fs.watch reliability probe: built, no in-bundle caller found\n\nA new fs.watch reliability probe module was added to the bundle, but nothing calls it yet\n\n**Unclear.** The finding does not say when or whether this probe will actually be wired up to affect file-watching behavior.\n\n**What**\n\nA new module writes a test file, watches it with Node's `fs.watch`, writes to it repeatedly over a time budget, and classifies the platform's file-watching behavior as 'delivers', 'refused', 'silent', or 'unprobed' if setup fails. Nothing else in the bundle appears to call this module's entry point yet.\n\n**Why**\n\nThis looks like preparation for choosing a file-watching strategy based on how reliably a given filesystem delivers change notifications, but since nothing invokes it yet, it has no effect on current behavior.\n\n- Area: File Watching\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}