Files that are resolved via nodePaths fail to trigger the watcher's esbuild event source

[KevinBrogan]

My config for esbuild.context includes:
nodePaths: ['./','./components','./functions','./modules']

Any time a file is modified that relies on the nodePaths configuration for import path resolution, the /esbuild event emitter of the watch system will fail to emit an event.

example
/components/Component.js includes import {getElementTag} from 'getElementTag.js'; which is in the functions directory.
changes to getElementTag.js will not fire an event.

modifying the include to import {getElementTag} from '../functions/getElementTag.js'; will result in the event being emitted when getElementTag.js is changed.

versions
node 18.13.0
esbuild 0.17.16
chrome 112.0.5615.121
Windows 10