fix(optimizer): transpile before calling transformGlobImport

[sapphi-red]

Description

When import.meta.glob is used inside Vue SFC with TypeScript, optimizer fails with error.
Minimal reproduction (stackblitz). Run npx vite optimize to reproduce.

Before #7537, TypeScript was transpiled to JavaScript before passing to es-module-lexer.

vite/packages/vite/src/node/optimizer/scan.ts

Lines 304 to 317 in b215493

	if (contents.includes('import.meta.glob')) {
	scripts[key] = {
	// transformGlob already transforms to js
	loader: 'js',
	contents: await transformGlob(
	contents,
	path,
	config.root,
	loader,
	resolve,
	config.logger
	)
	}
	} else {

vite/packages/vite/src/node/optimizer/scan.ts

Lines 493 to 507 in b215493

	async function transformGlob(
	source: string,
	importer: string,
	root: string,
	loader: Loader,
	resolve: (url: string, importer?: string) => Promise<string | undefined>,
	logger: Logger
	) {
	// transform the content first since es-module-lexer can't handle non-js
	if (loader !== 'js') {
	source = (await transform(source, { loader })).code
	}
	await init
	const imports = parse(source)[0]

After #7537, the transpilation was removed.

vite/packages/vite/src/node/optimizer/scan.ts

Lines 302 to 313 in 330e0a9

	scripts[key] = {
	loader: 'js',
	contents:
	(
	await transformGlobImport(
	contents,
	path,
	config.root,
	resolve
	)
	)?.s.toString() || contents
	}

But parseImportGlob which is called from transformGlobImport assumes the code as JavaScript. So that transpilation is still needed.

vite/packages/vite/src/node/plugins/importMetaGlob.ts

Lines 116 to 122 in 330e0a9

	try {
	ast = parseExpressionAt(code, start, {
	ecmaVersion: 'latest',
	sourceType: 'module',
	ranges: true
	}) as any
	} catch (e) {

Additional context

Found while testing alpha.4 with my 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.

[bluwy]

Should we only transpile if loader !== 'js'?