fix: respect absolute paths in handleHotUpdate

[kainstar]

Problem

handleHotUpdate never reloads the virtual module when paths contains an absolute path.

The current check is:

options.paths.some((p) => file.startsWith(path.join(process.cwd(), p)))

path.join (unlike path.resolve) does not strip an absolute prefix from its later arguments — it just concatenates with a separator:

path.join('/cwd', '/Users/me/project/locales')
// → '/cwd/Users/me/project/locales'   ← nonsense

So when a consumer passes an absolute path (very common — e.g. path.resolve(__dirname, '../resources') in a monorepo where cwd ≠ the project root), the join produces a path no real file starts with, the predicate is always false, and HMR for locale files silently does nothing.

This is independent of any Vite version — handleHotUpdate({ file }) has been absolute since Vite 3.

Fix

Only join with process.cwd() when the configured path is relative; pass absolute paths through as-is.

options.paths.some((p) =>
  file.startsWith(path.isAbsolute(p) ? p : path.join(process.cwd(), p)),
)

Tests

Adds src/__tests__/handleHotUpdate.test.ts covering:

• absolute paths → reloadModule is called (regression test for this bug)
• relative paths (relative to cwd) → reloadModule is called
• file outside configured paths → reloadModule is NOT called
• file with non-locale extension → reloadModule is NOT called

All 18 tests pass.

How to reproduce the original bug

In any project where the plugin is configured with an absolute path:

i18nextLoader({
  paths: [path.resolve(__dirname, 'locales')],
})

Edit any locale YAML/JSON and observe that the virtual module is never reloaded; you have to restart Vite to see changes.

[rosskevin]

@kainstar I'm sorry I missed this notification! Thank you

[rosskevin]

I'll fix the release, I need to do a little tooling maintenance. Should be out soon.

[rosskevin]

Released in v4.0.0