docs(config-file): update tip note about string replace

[jprando]

Description

in the documentation, guide developers about errors that may occur in certain use cases, referring to the vite configuration file

Additional context

reproducing:

• start a new project with vite + vue + ts
• insert console.log("import.meta.url") at the end of the vite.config.ts file
• build the project

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

@jprando https://stackblitz.com/edit/vitejs-vite-bme6zd?file=vite.config.ts&terminal=dev
I was not able to reproduce it. Am i missing something?

[jprando]

@jprando https://stackblitz.com/edit/vitejs-vite-bme6zd?file=vite.config.ts&terminal=dev I was not able to reproduce it. Am i missing something?

forward this asciinema

https://asciinema.org/a/492422

look for double quote in console.log

[jprando]

@jprando https://stackblitz.com/edit/vitejs-vite-bme6zd?file=vite.config.ts&terminal=dev I was not able to reproduce it. Am i missing something?

double quote here and the error occurs

[bluwy]

I can reproduce it too with double quotes. On the other hand, I wonder if we should change the strategy to polyfill using globals instead 🤔

globalThis.import = { url: "bla" }
globalThis.__dirname = "bla"

[sapphi-red]

Global variables nor define cannot be used because the value differs among files.

// foo.js
export const myFile = __filename

// -----------
// vite.config.js
const { myFile: myFileFoo } = require('./foo.js')
const myFile = __filename

console.log(myFileFoo) // 'foo.js'
console.log(myFile) // 'vite.config.js'

[bluwy]

That's true, maybe we can inject them at the top of the file as variables, but now I'm also leaning to not polyfilling them at all to keep it closer to specs. And with Vite 3 around the corner, we can group all config issues and make one breaking change 🤔

[patak-dev]

I think we can merge this in the meantime. We may end up removing this section in v3 but it is ok to have it for the moment.