Errors happening in other folders point to the wrong file

[posva]

Describe the bug

While developing, some errors can crash the error formatted by trying to access non existing lines. This seems to happen with:

• An npm package referring to a folder outside of the project
• Using Tailwind + postcssnon-existing

I didn't manage to crash the server in the reproduction as it does in my dev environment but the crash happened at

vite/packages/vite/src/node/utils.ts

Line 250 in 1e711c0

start += lines[i].length + 1

(which is where the cannot read property 'length' of undefined happens)

Reproduction

• Clone https://github.com/posva/vite-tailwind-bug-error-report
• Go to project and npm i with npm 7
• npm run dev
• You should see an error

  Internal server error: Cannot read property 'length' of undefined
  

• Remove the whole comment in package/style.css
• See the actual error is pointing to the wrong file and the line + column is just happening to also exist in the local file theme.css

System Info

System:
    OS: macOS 11.5.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
    Memory: 1.54 GB / 16.00 GB
    Shell: 5.8 - /usr/local/bin/zsh
  Binaries:
    Node: 16.6.1 - ~/.nvm/versions/node/v16.6.1/bin/node
    Yarn: 1.22.11 - ~/.nvm/versions/node/v16.6.1/bin/yarn
    npm: 7.20.3 - ~/.nvm/versions/node/v16.6.1/bin/npm

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[bluwy]

This seems to be fixed since #6293

I now get