This usually happens because the stack trace is resolving to where Devtools is mounted (__root.tsx), not necessarily where the console.log is written.

It’s not that Devtools is modifying the log, but more about how source maps / module mapping are handled in dev.

A few things you can check:

1. Make sure source maps are enabled

Vite:

export default {
  build: {
    sourcemap: true,
  },
}

Webpack:

devtool: 'source-map'

2. Try logging directly inside your component/function

console.log('test')

If it still points to __root.tsx, it's likely a mapping issue rather than where the log is called from.

3. Check the call stack in DevTools
Click the file link and inspect the stack — the correct source usually appears there.

4. Dev mode quirk
In some setups (especially with Vite + TanStack Router/Devtools), this can just be a dev-time source map quirk where everything resolves to the root entry.