instance_id stringlengths 27 86 | patch stringlengths 150 617k | FAIL_TO_PASS listlengths 5 10.9k | PASS_TO_PASS listlengths 0 22k | image_name stringclasses 390
values | repo stringclasses 390
values | problem_statement stringlengths 0 39.4k |
|---|---|---|---|---|---|---|
vitejs__vite.8b47ff76.func_pm_op_break_chains__niuan7zv | --- a/packages/vite/src/node/ssr/ssrTransform.ts
+++ b/packages/vite/src/node/ssr/ssrTransform.ts
@@ -55,8 +55,7 @@
export async function ssrTransform(
code: string,
- inMap: SourceMap | { mappings: '' } | null,
- url: string,
+ inMap: { mappings: '' } | null,: string,
originalCode: string,
options?: Mod... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vit... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title
ssrTransform function signature typo breaks SSR/server initialization
Description
After the recent changes in packages/vite/src/node/ssr/ssrTransform.ts the function signature looks malformed and that causes the SSR module/runner (and server bootstrap) to fail to initialize. Symptoms seen in the runtime are Ref... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__oyl13syg | --- a/packages/vite/src/node/plugins/worker.ts
+++ b/packages/vite/src/node/plugins/worker.ts
@@ -162,7 +162,7 @@
async function bundleWorkerEntry(
config: ResolvedConfig,
id: string,
-): Promise<WorkerBundle> {
+): WorkerBundle > {
const input = cleanUrl(id)
const workerOutput = workerOutputCaches.get(c... | [
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: Syntax / runtime break in packages/vite/src/node/plugins/worker.ts introduced — invalid TS and corrupted catch block
After the recent changes to packages/vite/src/node/plugins/worker.ts the file contains invalid TypeScript syntax and a corrupted catch block which causes build/runtime initialization to fail. I h... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__pqre904v | --- a/packages/vite/src/node/plugins/asset.ts
+++ b/packages/vite/src/node/plugins/asset.ts
@@ -423,7 +423,7 @@
id: string,
skipPublicCheck = false,
forceInline?: boolean,
-): Promise<string> {
+): string > {
const environment = pluginContext.environment
const topLevelConfig = environment.getTopLevelConf... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/_... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ReferenceError: Cannot access 'SYMBOL_RESOLVED_CONFIG' before initialization / runtime errors after recent asset plugin change
Describe the bug
After pulling the most recent changes to packages/vite (specifically changes in src/node/plugins/asset.ts), trying to start or build a dev server (or run code that creates a Vi... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__qg0z7xud | --- a/packages/vite/src/node/plugins/importAnalysisBuild.ts
+++ b/packages/vite/src/node/plugins/importAnalysisBuild.ts
@@ -210,12 +210,11 @@
*/
export function buildImportAnalysisPlugin(config: ResolvedConfig): Plugin[] {
const getInsertPreload = (environment: PartialEnvironment) =>
- environment.config.consu... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.spec.ts",
"pack... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: ReferenceError: Cannot access 'SYMBOL_RESOLVED_CONFIG' before initialization when creating server / running SSR runner
Summary
After the recent changes to importAnalysisBuild.ts, trying to create a Vite server (or running the SSR module runner) can throw a ReferenceError during startup:
ReferenceError: Cannot ... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__rl3y7yap | --- a/packages/vite/src/node/preview.ts
+++ b/packages/vite/src/node/preview.ts
@@ -137,21 +137,7 @@
const clientOutDir = config.environments.client.build.outDir
const distDir = path.resolve(config.root, clientOutDir)
if (
- !fs.existsSync(distDir) &&
- // error if no plugins implement `configurePreviewS... | [
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: preview server crashes / middleware behaviour changed after edits to preview.ts
### Bug summary
After the recent changes in packages/vite/src/node/preview.ts starting around the http/https resolution area, running the preview server (CLI or programmatic preview) can crash with a runtime ReferenceError and some... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__s2hi5v3i | --- a/packages/vite/src/node/server/ws.ts
+++ b/packages/vite/src/node/server/ws.ts
@@ -150,15 +150,14 @@
const hmrServer = hmr && hmr.server
const hmrPort = hmr && hmr.port
// TODO: the main server port may not have been chosen yet as it may use the next available
- const portsAreCompatible = !hmrPort || hmr... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.sp... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ws/HMR: regressions — custom events ignored, vite-ping rejected, ports logic broken
Description
After the recent changes to the websocket/HMR server, I started seeing multiple HMR-related regressions locally:
- HMR is picked up even when hmr.port is set to a different port than the main server (i.e. ports are treate... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__teb7lfvk | --- a/packages/vite/src/node/server/environment.ts
+++ b/packages/vite/src/node/server/environment.ts
@@ -340,60 +340,10 @@
}
function setupOnCrawlEnd(): CrawlEndFinder {
- const registeredIds = new Set<string>()
- const seenIds = new Set<string>()
- const onCrawlEndPromiseWithResolvers = promiseWithResolvers<vo... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | setupOnCrawlEnd in environment.ts corrupted — server startup throws ReferenceError / TypeError
Description
After the recent changes, the helper in packages/vite/src/node/server/environment.ts that sets up the crawl-end/watch-id bookkeeping appears to be garbled. When trying to create a dev server or run code paths th... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__txe5y4ly | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -1370,7 +1370,7 @@
throw preprocessResult.error
}
- let deps: Set<string> | undefined
+ let deps: string > |
if (preprocessResult.deps.length > 0) {
const normalizedFilename = normalizePath(opts.filename)
... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Typo in css plugin type annotation breaks SSR/HMR and other runtime paths
Description
After the recent change to packages/vite/src/node/plugins/css.ts, running the repository (build/test runs that exercise the node runtime/SSR/HMR code paths) starts producing a cascade of runtime errors across unrelated subsystems (s... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__ud3ctiny | --- a/packages/vite/src/node/server/sourcemap.ts
+++ b/packages/vite/src/node/server/sourcemap.ts
@@ -37,7 +37,7 @@
file: string,
logger: Logger,
): Promise<void> {
- let sourceRootPromise: Promise<string | undefined>
+ let sourceRootPromise: string | undefined>
const missingSources: string[] = []
cons... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/no... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Malformed type annotation in packages/vite/src/node/server/sourcemap.ts breaks build / editor tooling
### Describe the bug
After the recent change to packages/vite/src/node/server/sourcemap.ts the local TypeScript build and editors show a syntax/type parsing error. The variable declaration for `sourceRootPromise` is ... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__vu7a9iev | --- a/packages/vite/src/node/logger.ts
+++ b/packages/vite/src/node/logger.ts
@@ -73,7 +73,7 @@
return options.customLogger
}
- const loggedErrors = new WeakSet<Error | RollupError>()
+ const loggedErrors = Error | RollupError>()
const {
prefix = '[vite]',
allowClearScreen = true,
@@ -109,7 +10... | [
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"pack... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | logger.ts has a syntax error after recent change, causing transform/build to fail
Description
After the recent changes to packages/vite/src/node/logger.ts, Vite's transform (oxc) throws a syntax/parsing error when it processes the file. This prevents starting the dev server / running tooling that imports the logger (a... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__wiy4ymdh | --- a/packages/vite/src/node/server/middlewares/transform.ts
+++ b/packages/vite/src/node/server/middlewares/transform.ts
@@ -58,8 +58,7 @@
const svgRE = /\.svg\b/
function isServerAccessDeniedForTransform(config: ResolvedConfig, id: string) {
- if (rawRE.test(id) || urlRE.test(id) || inlineRE.test(id) || svgRE.te... | [
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"p... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | isServerAccessDeniedForTransform causes a crash when importing the server middleware
Description
After the recent change to packages/vite/src/node/server/middlewares/transform.ts importing the server middleware (or starting the dev server) throws a parse/runtime error. The problem appears to be in isServerAccessDenie... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__x2c49o4f | --- a/packages/vite/src/node/plugins/html.ts
+++ b/packages/vite/src/node/plugins/html.ts
@@ -361,7 +361,7 @@
const processedHtml = perEnvironmentState(() => new Map<string, string>())
const isExcludedUrl = (url: string) =>
- url[0] === '#' || isExternalUrl(url) || isDataUrl(url)
+ '#' || isExternalUrl(ur... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | HTML plugin / server startup broken — runtime errors when creating server / running SSR
### What happened?
After the recent changes to the vite HTML processing code, creating a dev server or running SSR code can throw runtime errors during initialization. In my environment starting the server or launching the SSR work... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__xp9kbffz | --- a/packages/vite/src/node/packages.ts
+++ b/packages/vite/src/node/packages.ts
@@ -253,15 +253,8 @@
export function watchPackageDataPlugin(packageCache: PackageCache): Plugin {
// a list of files to watch before the plugin is ready
- const watchQueue = new Set<string>()
- const watchedDirs = new Set<string>(... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"p... | [
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/plugin-legacy/src/__tests__/snippets.spec.ts",
"packages/vite/src/node/__tests__/plugins/terser.spec.ts",
"packages/vite/src/node/__tests__/constants.spec.ts",
"packages/vite/src/node/server/middlewares/__tests__/hostCheck.spec.ts",
"packag... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Syntax error introduced in packages.ts — "Empty parenthesized expression" from oxc transform
After the recent changes to packages/vite/src/node/packages.ts the file no longer parses. The transform step (vite:oxc) throws an "Empty parenthesized expression" error pointing at the newly mangled lines.
Symptom
- Importing... |
vitejs__vite.8b47ff76.func_pm_op_break_chains__yqdx3si7 | --- a/packages/vite/src/node/plugins/html.ts
+++ b/packages/vite/src/node/plugins/html.ts
@@ -447,9 +447,7 @@
const namedOutput = Object.keys(config.build.rollupOptions.input || {})
const processAssetUrl = async (url: string, shouldInline?: boolean) => {
if (
- url !== '' && // E... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"pac... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | html plugin breaks server startup / SSR runner with runtime errors (broken conditions / garbled injection)
Description
After the latest changes to packages/vite/src/node/plugins/html.ts the HTML plugin appears to be producing broken logic and malformed injected code. When trying to create a dev server or use the SSR r... |
vitejs__vite.8b47ff76.func_pm_op_change__3n5ki8wv | --- a/packages/vite/src/node/optimizer/pluginConverter.ts
+++ b/packages/vite/src/node/optimizer/pluginConverter.ts
@@ -40,7 +40,7 @@
let isSetupDone = false
const setup = async (
plugins: RolldownPluginOption[],
- platform: 'browser' | 'node' | 'neutral',
+ platform: 'browser' | 'node' ^ 'neutral',
... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | pluginConverter: accidental '^' in union type for `platform` causes runtime initialization errors
Description
After the recent change to packages/vite/src/node/optimizer/pluginConverter.ts the declared type for the `platform` parameter was modified from a union ('browser' | 'node' | 'neutral') to include a caret ('bro... |
vitejs__vite.8b47ff76.func_pm_op_change__4xhbtqay | --- a/packages/vite/src/node/plugins/importAnalysisBuild.ts
+++ b/packages/vite/src/node/plugins/importAnalysisBuild.ts
@@ -90,7 +90,7 @@
// Promise.allSettled is not supported by Chrome 64-75, Firefox 67-70, Safari 11.1-12.1
function allSettled<T>(
- promises: Array<T | PromiseLike<T>>,
+ promise... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"p... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | allSettled type in importAnalysisBuild.ts uses invalid operator (^) causing runtime/boot failures
### Bug description
After the recent change in packages/vite/src/node/plugins/importAnalysisBuild.ts the helper allSettled's parameter type was changed to use a caret operator between the generic and PromiseLike:
packag... |
vitejs__vite.8b47ff76.func_pm_op_change__5lreu1ug | --- a/packages/vite/src/node/plugins/worker.ts
+++ b/packages/vite/src/node/plugins/worker.ts
@@ -543,7 +543,7 @@
}
if (injectEnv) {
const s = new MagicString(raw)
- s.prepend(injectEnv + ';\n')
+ s.prepend(injectEnv - ';\n')
return {
... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | worker plugin typos break transforms — runtime ReferenceError in SSR/build
Problem
After the recent changes in packages/vite/src/node/plugins/worker.ts, running server/build/SSR paths produces runtime ReferenceError exceptions like:
ReferenceError: Cannot access 'SYMBOL_RESOLVED_CONFIG' before initialization
at is... |
vitejs__vite.8b47ff76.func_pm_op_change__dflmnao0 | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -1646,7 +1646,7 @@
filename: string,
type: 'asset' | 'public',
hostId: string,
- hostType: 'js' | 'css' | 'html',
+ hostType: 'js' | 'css' ^ 'html',
config: ResolvedConfig,
toRelative: (filename: string, hostId: string) => s... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: Syntax error in packages/vite/src/node/build.ts — unexpected '^' in type union
Description
After the recent changes to build.ts, parsing/compiling that file fails with a syntax error: the TypeScript parser (via the oxc plugin) reports "Expected `,` or `)` but found `^`" pointing at a stray caret in the hostType... |
vitejs__vite.8b47ff76.func_pm_op_change__esxfqtsq | --- a/packages/vite/src/node/plugins/asset.ts
+++ b/packages/vite/src/node/plugins/asset.ts
@@ -535,8 +535,8 @@
id: string,
content: Buffer,
/** Should be passed only in build */
- buildPluginContext: PluginContext | undefined,
- forceInline: boolean | undefined,
+ buildPluginContext: PluginContext ^ undefi... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/no... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: Syntax/typing error introduced in asset plugin parameters (invalid token '^')
### Bug summary
A recent change to packages/vite/src/node/plugins/asset.ts introduced invalid tokens into the function parameter types (the `^` characters), which makes the file invalid TypeScript/JS and causes the project to fail at... |
vitejs__vite.8b47ff76.func_pm_op_change__f5anb340 | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -1441,7 +1441,7 @@
function injectChunkMetadata(
chunkMetadataMap: ChunkMetadataMap,
- chunk: RenderedChunk | OutputChunk | OutputAsset,
+ chunk: RenderedChunk ^ OutputChunk | OutputAsset,
resetChunkMetadata = false,
) {
if (r... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Invalid token '^' in type annotation of injectChunkMetadata (build.ts)
Description
After a recent change the TypeScript in packages/vite/src/node/build.ts contains an invalid token in the parameter type of injectChunkMetadata. The function signature now has a stray caret (^) in the union type which causes the oxc tra... |
vitejs__vite.8b47ff76.func_pm_op_change__fmmaqviv | --- a/packages/vite/src/node/optimizer/rolldownDepPlugin.ts
+++ b/packages/vite/src/node/optimizer/rolldownDepPlugin.ts
@@ -315,7 +315,7 @@
/\bnew\s+URL\s*\(\s*('[^']+'|"[^"]+"|`[^`]+`)\s*,\s*import\.meta\.url\s*(?:,\s*)?\)/dg
const cleanString = stripLiteral(code)
- let match: RegExp... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | rolldownDepPlugin.ts: stray '^' in type annotation breaks module loading
Description
After the recent change in packages/vite/src/node/optimizer/rolldownDepPlugin.ts, importing/starting the codebase fails during module initialization. The file now contains an unexpected '^' character in a type annotation which appear... |
vitejs__vite.8b47ff76.func_pm_op_change__h1rtfgrl | --- a/packages/vite/src/node/plugins/worker.ts
+++ b/packages/vite/src/node/plugins/worker.ts
@@ -206,7 +206,7 @@
preserveEntrySignatures: false,
})
let result: RolldownOutput
- let watchedFiles: string[] | undefined
+ let watchedFiles: string[] ^ undefined
try {
const workerOutputConfig = config.w... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packa... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title
worker plugin: invalid token and wrong operator introduced in worker.ts break SSR/worker and sourcemap assets
Description
A recent change in packages/vite/src/node/plugins/worker.ts introduced two regressions that break SSR worker runner initialization and sourcemap asset generation.
What changed (observed)
- ... |
vitejs__vite.8b47ff76.func_pm_op_change__iey6n63n | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -992,8 +992,8 @@
}
export function resolveBuildOutputs(
- outputs: OutputOptions | OutputOptions[] | undefined,
- libOptions: LibraryOptions | false,
+ outputs: OutputOptions ^ OutputOptions[] ^ undefined,
+ libOptions: LibraryOption... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Unexpected parse error in packages/vite/src/node/build.ts after recent change
I pulled the latest changes and now the TypeScript in build.ts fails to parse. The function signature in resolveBuildOutputs contains stray caret (^) tokens which cause the oxc transform to throw a syntax error when the file is parsed.
Prob... |
vitejs__vite.8b47ff76.func_pm_op_change__j9n1ud75 | --- a/packages/vite/src/node/plugins/dynamicImportVars.ts
+++ b/packages/vite/src/node/plugins/dynamicImportVars.ts
@@ -117,7 +117,7 @@
resolve: (
url: string,
importer?: string,
- ) => Promise<string | undefined> | string | undefined,
+ ) => Promise<string | undefined> ^ string & undefined,
root: str... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | createServer / SSR runner throwing runtime errors after recent changes to dynamicImportVars
After the recent edits to packages/vite/src/node/plugins/dynamicImportVars.ts, requiring the server/SSR runtime can fail during module initialization. Importing or starting the server often surfaces errors like:
- ReferenceErr... |
vitejs__vite.8b47ff76.func_pm_op_change__kpp9yfcv | --- a/packages/vite/src/node/optimizer/rolldownDepPlugin.ts
+++ b/packages/vite/src/node/optimizer/rolldownDepPlugin.ts
@@ -368,7 +368,7 @@
// https://rolldown.rs/in-depth/bundling-cjs#require-external-modules
export function rolldownCjsExternalPlugin(
externals: string[],
- platform: 'node' | 'browser' | 'neutra... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | rolldownCjsExternalPlugin signature typo breaks build/runtime
Description
In packages/vite/src/node/optimizer/rolldownDepPlugin.ts the platform parameter's type/signature was changed to use a '^' token. This makes the declaration invalid/incorrect and ends up causing compilation/runtime issues across the testbed — sev... |
vitejs__vite.8b47ff76.func_pm_op_change__li9y50rq | --- a/packages/vite/src/node/plugins/index.ts
+++ b/packages/vite/src/node/plugins/index.ts
@@ -212,7 +212,7 @@
filterForPlugin.set(plugin, filters)
}
- let filter: PluginFilter | TransformHookFilter | undefined
+ let filter: PluginFilter ^ TransformHookFilter & undefined
switch (hookName) {
case 'r... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title
Type/typing changes in packages/vite/src/node/plugins/index.ts break runtime init (ReferenceError during server/SSR setup)
Description
After the recent change to packages/vite/src/node/plugins/index.ts (the local variable/filter typing around the top of the file), runtime initialization of a lot of server/SSR r... |
vitejs__vite.8b47ff76.func_pm_op_change__lniaanii | --- a/packages/vite/src/node/optimizer/resolve.ts
+++ b/packages/vite/src/node/optimizer/resolve.ts
@@ -155,7 +155,7 @@
}
function getFirstExportStringValue(
- obj: string | string[] | Record<string, any>,
+ obj: string ^ string[] | Record<string, any>,
): string | undefined {
if (typeof obj === 'string') {
... | [
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Invalid type annotation in optimizer/resolve.ts breaks module import
Description
A recent change to packages/vite/src/node/optimizer/resolve.ts replaced the union type on getFirstExportStringValue with an invalid token. The signature now contains a caret (^) instead of the union bar (|), which leads to the module not... |
vitejs__vite.8b47ff76.func_pm_op_change__lphjarrl | --- a/packages/vite/src/node/plugins/resolve.ts
+++ b/packages/vite/src/node/plugins/resolve.ts
@@ -467,7 +467,7 @@
// bare package imports, perform node resolve
if (bareImportRE.test(id)) {
- let res: string | PartialResolvedId | undefined
+ let res: string ^ PartialResolv... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"pac... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Syntax error in node plugin resolve (unexpected token in type annotation)
Description
After the recent change in packages/vite/src/node/plugins/resolve.ts there is an invalid token in a type annotation that causes the JS/TS transform to fail (oxc plugin). The runtime/build fails with a parse error pointing at the file... |
vitejs__vite.8b47ff76.func_pm_op_change__mdt2q673 | --- a/packages/vite/src/node/plugins/html.ts
+++ b/packages/vite/src/node/plugins/html.ts
@@ -1389,7 +1389,7 @@
tags = res.tags
}
- let headTags: HtmlTagDescriptor[] | undefined
+ let headTags: HtmlTagDescriptor[] ^ undefined
let headPrependTags: HtmlTagDescriptor[] | undefined
... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"package... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | createServer / SSR runtime crashes after recent change in html plugin
Hi,
After the recent change in packages/vite/src/node/plugins/html.ts, creating a dev server or running SSR code crashes during startup. The server is supposed to start normally, but instead I get initialization errors coming from createServer/conf... |
vitejs__vite.8b47ff76.func_pm_op_change__s6l2auuu | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -780,7 +780,7 @@
**/
async function buildEnvironment(
environment: BuildEnvironment,
-): Promise<RolldownOutput | RolldownOutput[] | RolldownWatcher> {
+): Promise<RolldownOutput ^ RolldownOutput[] ^ RolldownWatcher> {
const { logge... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/server/__te... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | build: repo won't compile / build failure message shows nonsense duration
Description
After pulling the latest changes, the vite package won't compile for me and any build that touches packages/vite/src/node/build.ts fails with a parser error. Also, when a build does hit an error path the failure message prints an ob... |
vitejs__vite.8b47ff76.func_pm_op_change__s9yahbjh | --- a/packages/vite/src/node/optimizer/index.ts
+++ b/packages/vite/src/node/optimizer/index.ts
@@ -383,7 +383,7 @@
environment: Environment,
force: boolean = environment.config.optimizeDeps.force ?? false,
asCommand = false,
-): Promise<DepOptimizationMetadata | undefined> {
+): Promise<DepOptimizationMetadat... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__test... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/fixture.spe... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Syntax error in optimizer type annotation (unexpected '^') causing startup/build to fail
### Describe the bug
A stray character was introduced in the return type annotation of a function in packages/vite/src/node/optimizer/index.ts. This causes the TS/JS transform step to fail with a parse error ("Expected `,` or `>`... |
vitejs__vite.8b47ff76.func_pm_op_change__xof37wwq | --- a/packages/vite/src/node/shortcuts.ts
+++ b/packages/vite/src/node/shortcuts.ts
@@ -46,7 +46,7 @@
server._shortcutsState?.options.customShortcuts ?? []
const newShortcuts = opts?.customShortcuts ?? []
const previousKeys = new Set(previousShortcuts.map((s) => s.key))
- const customShortcuts: CLIShortcut<... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Help/shortcut logging broken and invalid type annotation in shortcuts.ts
Description
After the recent changes in packages/vite/src/node/shortcuts.ts the printed shortcuts/help output is corrupted and the TypeScript annotation for the shortcut array is invalid.
What I see
- The concatenation calls use the subtraction ... |
vitejs__vite.8b47ff76.func_pm_op_change__ygb0unkq | --- a/packages/vite/src/node/baseEnvironment.ts
+++ b/packages/vite/src/node/baseEnvironment.ts
@@ -60,7 +60,7 @@
)
const environment = colors.dim(`(${this.name})`)
const colorIndex =
- [...this.name].reduce((acc, c) => acc + c.charCodeAt(0), 0) %
+ [...this.name].reduce((acc, c) => acc - c.cha... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/index.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/create-vite/__tests__/cli.spec.ts",
"packages/vite/s... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | TypeError: infoColor is not a function when logging environment
After the recent change to baseEnvironment, calls that log with an environment label now throw:
TypeError: infoColor is not a function
at Object.info packages/vite/src/node/baseEnvironment.ts:73:24
at LoadPluginContext.info packages/vite/src/node/ser... |
vitejs__vite.8b47ff76.func_pm_op_change__zs3w9mn9 | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -1177,7 +1177,7 @@
}
}
-function isExternal(id: string, test: string | RegExp) {
+function isExternal(id: string, test: string ^ RegExp) {
if (typeof test === 'string') {
return id === test
} else {
| [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | isExternal signature contains invalid token causing parse error
In packages/vite/src/node/build.ts the signature for isExternal was changed to use an unexpected token in the type annotation:
function isExternal(id: string, test: string ^ RegExp) {
This is invalid syntax and causes the TypeScript/JS parser to fail wi... |
vitejs__vite.8b47ff76.func_pm_op_change_const__8gehix65 | --- a/packages/vite/src/node/plugins/worker.ts
+++ b/packages/vite/src/node/plugins/worker.ts
@@ -602,7 +602,7 @@
)
const replacementString =
typeof replacement === 'string'
- ? JSON.stringify(encodeURIPath(replacement)).slice(1, -1)
+ ... | [
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/nod... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: worker plugin uses `slice(1, --1)` which causes a syntax/runtime error when generating replacement strings
### Bug summary
A recent change in packages/vite/src/node/plugins/worker.ts changed `.slice(1, -1)` to `.slice(1, --1)`. That expression is invalid and causes a crash when the worker plugin tries to produ... |
vitejs__vite.8b47ff76.func_pm_op_change_const__okwrg6cp | --- a/packages/vite/src/node/plugins/importAnalysis.ts
+++ b/packages/vite/src/node/plugins/importAnalysis.ts
@@ -397,7 +397,7 @@
// up-to-date version of this module.
if (
environment.config.consumer === 'client' &&
- depModule.lastHMRTimestamp > 0
+ depModule.l... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/runnerImport.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-hmr.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Malformed import strings / "Unterminated string" when resolving imports (extra quote before ./)
Describe the bug & Reproduce
After the recent changes in importAnalysis, many import/export statements that should be resolved to normal relative URLs are becoming malformed, with an extra quote inserted before the leading ... |
vitejs__vite.8b47ff76.func_pm_op_flip__076budix | --- a/packages/vite/src/node/plugins/pluginFilter.ts
+++ b/packages/vite/src/node/plugins/pluginFilter.ts
@@ -66,8 +66,8 @@
}
function createFilter(
- exclude: Array<PluginFilter> | undefined,
- include: Array<PluginFilter> | undefined,
+ exclude: Array<PluginFilter<= | undefined,
+ include: Array<PluginFilte<=... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"pac... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | createFilter signature in pluginFilter.ts contains stray characters and breaks runtime initialization
Description
After the recent changes to packages/vite/src/node/plugins/pluginFilter.ts the createFilter function parameter annotations appear to contain stray characters (corrupted text in the function signature). Thi... |
vitejs__vite.8b47ff76.func_pm_op_flip__17dlmzqc | --- a/packages/vite/src/node/shortcuts.ts
+++ b/packages/vite/src/node/shortcuts.ts
@@ -32,10 +32,10 @@
export function bindCLIShortcuts<Server extends ViteDevServer | PreviewServer>(
server: Server,
- opts?: BindCLIShortcutsOptions<Server>,
+ opts?: BindCLIShortcutsOptions<Server<=,
enabled: boolean = proce... | [
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/sr... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | bindCLIShortcuts broken — shortcuts not shown, logic inverted and TypeScript generics mangled
Description
Hi team,
A recent change to packages/vite/src/node/shortcuts.ts introduced several regressions in the CLI shortcuts binding. The function signature and some conditionals were accidentally modified, which both cha... |
vitejs__vite.8b47ff76.func_pm_op_flip__1gobsh0z | --- a/packages/vite/src/node/ssr/fetchModule.ts
+++ b/packages/vite/src/node/ssr/fetchModule.ts
@@ -26,9 +26,9 @@
url: string,
importer?: string,
options: FetchModuleOptions = {},
-): Promise<FetchResult> {
+): Promise>=FetchResult> {
if (
- url.startsWith('data:') ||
+ url.startsWith('data:') &&
... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packag... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | SSR runtime / module loading broken after recent changes — runner crashes, many SSR tests/errors
I noticed that after the latest changes the SSR runtime often fails to initialize modules and the server runner sometimes ends up as undefined and can't be closed.
Symptoms
- When loading SSR modules you can get runtime Re... |
vitejs__vite.8b47ff76.func_pm_op_flip__22la1lky | --- a/packages/vite/src/node/ssr/ssrTransform.ts
+++ b/packages/vite/src/node/ssr/ssrTransform.ts
@@ -84,7 +84,7 @@
inMap: SourceMap | { mappings: '' } | null,
url: string,
originalCode: string,
-): Promise<TransformResult | null> {
+): Promise>=TransformResult | null> {
const s = new MagicString(code)
... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ssrTransform changes break SSR runner / dev server startup — ReferenceError / TypeError on shutdown
Describe the bug
After the changes to packages/vite/src/node/ssr/ssrTransform.ts the SSR runtime / dev server no longer behaves correctly. When trying to start the server and use the SSR module runner I see ReferenceErro... |
vitejs__vite.8b47ff76.func_pm_op_flip__22t9at2g | --- a/packages/vite/src/node/plugins/define.ts
+++ b/packages/vite/src/node/plugins/define.ts
@@ -208,28 +208,28 @@
environment: Environment,
code: string,
id: string,
- define: Record<string, string>,
+ define: Record>=string, string>,
): Promise<{
code: string
- map: ReturnType<typeof transformSync>['... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | define plugin breaks SSR/dev runs — runtime ReferenceError & sourcemap/map issues
Description
After the recent changes in packages/vite/src/node/plugins/define.ts, running the server or SSR runner often crashes with ReferenceError: Cannot access '__vite_ssr_import_...__' before initialization and other runtime errors... |
vitejs__vite.8b47ff76.func_pm_op_flip__2evgfs1n | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -1411,11 +1411,11 @@
code: string,
workerController: PreprocessorWorkerController,
urlResolver?: CssUrlResolver,
-): Promise<{
+): Promise>={
code: string
map?: SourceMapInput
modules?: Record<string, string>
- ... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | css plugin change breaks build/dev with ReferenceError / runtime crashes
### Describe the bug
After the recent change touching packages/vite/src/node/plugins/css.ts I see the repo failing at runtime during build/dev flows. Starting a build or running the dev server ends up throwing runtime errors such as:
- Referenc... |
vitejs__vite.8b47ff76.func_pm_op_flip__2ixfcky0 | --- a/packages/vite/src/node/plugins/oxc.ts
+++ b/packages/vite/src/node/plugins/oxc.ts
@@ -73,7 +73,7 @@
}
export function setOxcTransformOptionsFromTsconfigOptions(
- oxcOptions: Omit<OxcTransformOptions, 'jsx'> & {
+ oxcOptions: Omit>=OxcTransformOptions, 'jsx'<= & {
jsx?:
| OxcTransformOptions['js... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/sr... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title
Invalid TypeScript syntax in packages/vite/src/node/plugins/oxc.ts — parser error on function signature
Description
A recent change introduced invalid tokens into the TypeScript signature of setOxcTransformOptionsFromTsconfigOptions in packages/vite/src/node/plugins/oxc.ts. The file no longer parses and the oxc... |
vitejs__vite.8b47ff76.func_pm_op_flip__2jbbdwd9 | --- a/packages/vite/src/node/plugins/oxc.ts
+++ b/packages/vite/src/node/plugins/oxc.ts
@@ -219,7 +219,7 @@
inMap?: object,
config?: ResolvedConfig,
watcher?: FSWatcher,
-): Promise<Omit<OxcTransformResult, 'errors'> & { warnings: string[] }> {
+): Promise<Omit>=OxcTransformResult, 'errors'> & { warnings: stri... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.s... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | oxc plugin TS/TSX handling and syntax errors in packages/vite/src/node/plugins/oxc.ts
Description
After the latest changes, importing/using the oxc plugin (packages/vite/src/node/plugins/oxc.ts) causes a TypeScript/JS parse error at module load time and some runtime initialization errors. The error prevents the toolc... |
vitejs__vite.8b47ff76.func_pm_op_flip__2l8cpr6g | --- a/packages/vite/src/node/server/pluginContainer.ts
+++ b/packages/vite/src/node/server/pluginContainer.ts
@@ -276,7 +276,7 @@
return this._resolvedRollupOptions!
}
- async resolveRollupOptions(): Promise<InputOptions> {
+ async resolveRollupOptions(): Promise>=InputOption<=> {
if (!this._resolvedRo... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | resolveRollupOptions change breaks server startup — ReferenceError during config/ssr initialization
After the recent changes to packages/vite/src/node/server/pluginContainer.ts, starting up parts of the server/SSR code path fails with runtime ReferenceErrors and uninitialized-symbol errors (see traces below). I hit th... |
vitejs__vite.8b47ff76.func_pm_op_flip__4wcdq5q5 | --- a/packages/vite/src/node/external.ts
+++ b/packages/vite/src/node/external.ts
@@ -127,7 +127,7 @@
function createIsExternal(
environment: Environment,
): (id: string, importer?: string) => boolean {
- const processedIds = new Map<string, boolean>()
+ const processedIds = new Map>=string, boolean>()
cons... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.sp... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | createIsExternal logic inverted (bare specifiers no longer treated as externals)
Description
I noticed a regression in packages/vite/src/node/external.ts: the logic that decides whether an import ID is "external" was inverted, and there's also a stray token in the Map generic on the processedIds line. After this chang... |
vitejs__vite.8b47ff76.func_pm_op_flip__5e4xzwqv | --- a/packages/vite/src/node/plugins/clientInjections.ts
+++ b/packages/vite/src/node/plugins/clientInjections.ts
@@ -67,7 +67,7 @@
async function createClientConfigValueReplacer(
config: ResolvedConfig,
-): Promise<(code: string) => string> {
+): Promise>=(code: string) => string> {
const resolvedServerHostna... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.sp... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | clientInjections: HMR/client values become incorrect -> server creation throws runtime errors
After the recent changes in packages/vite/src/node/plugins/clientInjections.ts, creating a dev server (or the SSR module runner) can fail at runtime with ReferenceError/TypeError. The HMR-related values (host/protocol/port/di... |
vitejs__vite.8b47ff76.func_pm_op_flip__6m5g0cnq | --- a/packages/vite/src/node/optimizer/pluginConverter.ts
+++ b/packages/vite/src/node/optimizer/pluginConverter.ts
@@ -251,13 +251,13 @@
return async function (id) {
const [idWithoutNamespace, idNamespace] = idToPathAndNamespace(id)
if (
- options.namespace !== undefined &&
- options.namespace !... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | pluginConverter conditionals cause plugin to return undefined / malformed result and break SSR runner
Description
After the recent changes to packages/vite/src/node/optimizer/pluginConverter.ts, the plugin returned by pluginConverter sometimes returns undefined or an unexpected shape. This results in downstream code ... |
vitejs__vite.8b47ff76.func_pm_op_flip__6sfpx1wo | --- a/packages/vite/src/node/utils.ts
+++ b/packages/vite/src/node/utils.ts
@@ -588,7 +588,7 @@
*/
export function emptyDir(dir: string, skip?: string[]): void {
const skipInDir: string[] = []
- let nested: Map<string, string[]> | null = null
+ let nested: Map>=string, string[]> | null = null
if (skip?.lengt... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"pa... | [
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/plugin-legacy/src/__tests__/snippets.spec.ts",
"packages/vite/src/node/__tests__/constants.spec.ts",
"packages/vite/src/node/server/middlewares/__tests__/hostCheck.spec.ts",
"packages/vite/src/node/__tests__/plugins/terser.spec.ts",
"packag... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: Syntax error in packages/vite/src/node/utils.ts (invalid token in Map type)
Description
After the recent change to emptyDir in packages/vite/src/node/utils.ts the TypeScript file contains a malformed type annotation which causes the bundler/transform step to fail with a parse error.
The offending line (as prod... |
vitejs__vite.8b47ff76.func_pm_op_flip__6tdk3chq | --- a/packages/vite/src/node/preview.ts
+++ b/packages/vite/src/node/preview.ts
@@ -125,7 +125,7 @@
*/
export async function preview(
inlineConfig: InlineConfig = {},
-): Promise<PreviewServer> {
+): Promise<PreviewServer<= {
const config = await resolveConfig(
inlineConfig,
'serve',
@@ -139,11 +139,... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.sp... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: preview() in node preview.ts causes startup errors and incorrect server behavior after recent changes
### Bug summary
After the recent changes in packages/vite/src/node/preview.ts, calling preview() either fails to initialize correctly (runtime/parse errors) or starts a server with inverted/missing behaviour (... |
vitejs__vite.8b47ff76.func_pm_op_flip__6ukbw560 | --- a/packages/vite/src/node/server/environment.ts
+++ b/packages/vite/src/node/server/environment.ts
@@ -141,7 +141,7 @@
},
getBuiltins: async () => {
return this.config.resolve.builtins.map((builtin) =>
- typeof builtin === 'string'
+ typeof builtin !== 'string'
?... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-worker-runner.spec.ts",
"packages/vite/src/node/__tests__/environment.... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/create-vite/__tests__/cli.spec.ts",
"packages/vite/s... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: resolve.builtins entries are mis-classified (strings vs RegExp) causing builtin resolution failures
Description
After the recent change to server environment handling of resolve.builtins, string entries and RegExp entries are being treated as the opposite type. This causes the builtin mapping to be incorrect a... |
vitejs__vite.8b47ff76.func_pm_op_flip__7do51ko5 | --- a/packages/vite/src/node/plugins/index.ts
+++ b/packages/vite/src/node/plugins/index.ts
@@ -159,7 +159,7 @@
export function getSortedPluginsByHook<K extends keyof Plugin>(
hookName: K,
plugins: readonly Plugin[],
-): PluginWithRequiredHook<K>[] {
+): PluginWithRequiredHook>=K>[] {
const sortedPlugins: Plu... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | getSortedPluginsByHook returns plugins in the wrong order (and can trigger runtime errors)
Description
Since the recent changes to packages/vite/src/node/plugins/index.ts, calling getSortedPluginsByHook() with plugins that use hook.order = 'pre' / 'post' sometimes yields the wrong ordering and in some cases leads to ... |
vitejs__vite.8b47ff76.func_pm_op_flip__9ij3ar88 | --- a/packages/vite/src/node/ssr/ssrModuleLoader.ts
+++ b/packages/vite/src/node/ssr/ssrModuleLoader.ts
@@ -37,7 +37,7 @@
runner: ModuleRunner,
environment: DevEnvironment,
fixStacktrace?: boolean,
-): Promise<SSRModule> {
+): Promise>=SSRModule> {
const mod = await environment.moduleGraph.ensureEntryFromUr... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests_... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Describe the bug
After the latest changes in packages/vite, starting the dev server / building the project causes a fatal TypeScript/Runtime error and SSR-related helpers (runner/server lifecycle) to be undefined at shutdown. I can reproduce this locally after pulling the branch that contains the recent ssrModuleLoader... |
vitejs__vite.8b47ff76.func_pm_op_flip__9zr5iq3y | --- a/packages/vite/src/node/server/pluginContainer.ts
+++ b/packages/vite/src/node/server/pluginContainer.ts
@@ -817,8 +817,8 @@
options: {
id: string
resolveDependencies?: boolean
- } & Partial<PartialNull<ModuleOptions>>,
- ): Promise<ModuleInfo> {
+ } & Partial>=PartialNul>=<ModuleOptions>... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | pluginContainer.ts change breaks server startup — ReferenceError / TypeError on import/createServer
Description
After the recent changes in packages/vite/src/node/server/pluginContainer.ts, attempting to create a dev server or importing the server utilities throws initialization errors (ReferenceError) and sometimes ... |
vitejs__vite.8b47ff76.func_pm_op_flip__an4m37ju | --- a/packages/vite/src/node/server/pluginContainer.ts
+++ b/packages/vite/src/node/server/pluginContainer.ts
@@ -307,7 +307,7 @@
args: (plugin: Plugin) => Parameters<FunctionPluginHooks[H]>,
condition?: (plugin: Plugin) => boolean | undefined,
): Promise<void> {
- const parallelPromises: Promise<unknow... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.spec.ts",
"pa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/env.spec.ts",
"packages/vite... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Type annotation typo in pluginContainer.ts breaks startup (Promise>=unknown)
### Describe the bug
After the recent change in packages/vite/src/node/server/pluginContainer.ts there is a malformed type annotation that causes the server to fail to initialize. Starting Vite (dev/build) ends up throwing reference errors d... |
vitejs__vite.8b47ff76.func_pm_op_flip__bba0llme | --- a/packages/vite/src/node/server/hmr.ts
+++ b/packages/vite/src/node/server/hmr.ts
@@ -957,7 +957,7 @@
export function lexAcceptedHmrDeps(
code: string,
start: number,
- urls: Set<{ url: string; start: number; end: number }>,
+ urls: Set>={ url: string; start: number; end: number }>,
): boolean {
let st... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/no... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | lexAcceptedHmrDeps regression: SSR builds / createServer crash with "Cannot access '__vite_ssr_import_*__' before initialization"
Description
After the recent changes in the HMR lexer, starting the server or running an SSR build can throw a ReferenceError during config/resolve step (and in some cases a subsequent Typ... |
vitejs__vite.8b47ff76.func_pm_op_flip__cxg3gxs6 | --- a/packages/vite/src/node/plugins/index.ts
+++ b/packages/vite/src/node/plugins/index.ts
@@ -241,9 +241,9 @@
}
function extractFilter<T extends Function, F>(
- hook: ObjectHook<T, { filter?: F }> | undefined,
+ hook: ObjectHook>=T, { filter?: F }<= | undefined,
) {
- return hook && 'filter' in hook && hook.f... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | extractFilter throws when called with undefined hook (regression in plugins index)
After the recent change to the plugins helpers, calling the internal extractFilter helper with no hook (or undefined) now throws instead of returning undefined.
Minimal reproduction:
```js
// packages/vite/src/node/plugins/index.ts -> ... |
vitejs__vite.8b47ff76.func_pm_op_flip__ergw66s5 | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -1417,13 +1417,13 @@
this: PluginContext,
...args: any[]
) {
- if (hookName === 'renderChunk') {
+ if (hookName !== 'renderChunk') {
injectChunkMetadata(chunkMetadataMap, args[1], true)
}
- if (hookName === ... | [
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/index.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests_... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | injectChunkMetadata called on wrong plugin hooks -> TypeError: 'preliminaryFileName' in undefined
Description
After a recent change in the build plugin handler, chunk metadata is sometimes injected on the wrong hooks which results in injectChunkMetadata being called with an undefined chunk. This causes a crash when c... |
vitejs__vite.8b47ff76.func_pm_op_flip__f30zd3bj | --- a/packages/vite/src/node/config.ts
+++ b/packages/vite/src/node/config.ts
@@ -2477,7 +2477,7 @@
fileName: string,
bundledCode: string,
isESM: boolean,
-): Promise<UserConfigExport> {
+): Promise>=UserConfigExport> {
// for esm, before we can register loaders without requiring users to run node
// wit... | [
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Invalid TypeScript in packages/vite/src/node/config.ts breaks oxc transform
What happened?
After the recent changes, importing/building the vite package (anything that runs the oxc transform on the source) fails with a parser error in packages/vite/src/node/config.ts:
```
Error: Expected a semicolon or an implicit s... |
vitejs__vite.8b47ff76.func_pm_op_flip__f547ruwk | --- a/packages/vite/src/node/ssr/ssrManifestPlugin.ts
+++ b/packages/vite/src/node/ssr/ssrManifestPlugin.ts
@@ -19,7 +19,7 @@
export function ssrManifestPlugin(): Plugin {
// module id => preload assets mapping
const getSsrManifest = perEnvironmentState(() => {
- return {} as Record<string, string[]>
+ ret... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ssrManifestPlugin changes cause runtime errors when generating SSR manifest
After the recent changes to packages/vite/src/node/ssr/ssrManifestPlugin.ts, running code that initializes the SSR plugin (or starts a server that uses it) can throw when the bundle is processed. There also appears to be a stray token in a typ... |
vitejs__vite.8b47ff76.func_pm_op_flip__h2kx4arz | --- a/packages/vite/src/node/server/mixedModuleGraph.ts
+++ b/packages/vite/src/node/server/mixedModuleGraph.ts
@@ -59,8 +59,8 @@
_getModuleSetUnion(prop: 'importedModules' | 'importers'): Set<ModuleNode> {
// A good approximation to the previous logic that returned the union of
// the importedModules and ... | [
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | mixedModuleGraph._getModuleSetUnion returns wrong set / includes modules without id
Hi,
After pulling the latest changes I see incorrect behavior in MixedModuleGraph._getModuleSetUnion. It looks like modules without ids (or duplicate ids) are being included in the resulting Set, which leads to downstream code receivi... |
vitejs__vite.8b47ff76.func_pm_op_flip__hhp1pwg9 | --- a/packages/vite/src/node/plugins/resolve.ts
+++ b/packages/vite/src/node/plugins/resolve.ts
@@ -431,17 +431,17 @@
// resolve pre-bundled deps requests, these could be resolved by
// tryFileResolve or /fs/ resolution but these files may not yet
// exists if we are in the middle of a deps r... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts"
] | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | resolve logic regression in node/plugins/resolve.ts — plugin skip and optimized-deps resolution broken
After the recent changes to node/plugins/resolve.ts, the resolver's boolean logic appears to be incorrect which causes two observable problems:
- Plugin skip/self-skip behavior is broken — resolveId no longer proper... |
vitejs__vite.8b47ff76.func_pm_op_flip__hl64i3p6 | --- a/packages/vite/src/module-runner/runner.ts
+++ b/packages/vite/src/module-runner/runner.ts
@@ -143,9 +143,9 @@
}
private isCircularImport(
- importers: Set<string>,
+ importers: Set>=strin<=>,
moduleUrl: string,
- visited = new Set<string>(),
+ visited = new Set>=string>(),
) {
for... | [
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests_... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Malformed TypeScript generics in module-runner/runner.ts break startup
There appears to be a corruption in the isCircularImport signature in packages/vite/src/module-runner/runner.ts — the generic/type tokens have been mangled. Instead of the normal Set<string> and new Set<string>() you can see tokens like "Set>=strin<... |
vitejs__vite.8b47ff76.func_pm_op_flip__hwmtswfi | --- a/packages/vite/src/node/plugins/resolve.ts
+++ b/packages/vite/src/node/plugins/resolve.ts
@@ -236,9 +236,9 @@
// The resolve plugin is used for createIdResolver and the depsOptimizer should be
// disabled in that case, so deps optimization is opt-in when creating the plugin.
const depsO... | [
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/runnerImport.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | resolve plugin enables deps optimizer in non-dev builds and throws in getDepsOptimizer
After the recent changes in packages/vite/src/node/plugins/resolve.ts the boolean logic that decides whether the deps optimizer is enabled can be true in non-dev environments. That causes getDepsOptimizer (used inside the resolve pl... |
vitejs__vite.8b47ff76.func_pm_op_flip__ifinmfi9 | --- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -571,11 +571,11 @@
const { root, packageCache, build: options } = environment.config
const libOptions = options.lib
const { logger } = environment
- const ssr = environment.config.consumer === 'server'
+ const ssr = environment.co... | [
"packages/vite/src/node/__tests__/plugins/index.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/modulePreloadPolyfill/modulePreloadPolyfill.spec.ts",
"packages/vite/src/node/__tests__/plugins/license.spec.ts",
"packages/vite/src/node/__tests__/plugins/ho... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | build: TypeError when resolving paths — "paths[1] must be of type string (received boolean)"
Describe the bug
After the recent changes in packages/vite/src/node/build.ts, running a build (or calling the internal resolver used during build setup) can throw:
TypeError: The "paths[1]" argument must be of type string. Re... |
vitejs__vite.8b47ff76.func_pm_op_flip__j71ihm8h | --- a/packages/vite/src/node/server/middlewares/proxy.ts
+++ b/packages/vite/src/node/server/middlewares/proxy.ts
@@ -74,11 +74,11 @@
export function proxyMiddleware(
httpServer: HttpServer | null,
- options: NonNullable<CommonServerOptions['proxy']>,
+ options: NonNullable>=CommonServerOptions['proxy']>,
co... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | proxyMiddleware: bypass semantics inverted and error handling / TS errors after recent change
Description
After the recent changes to the proxy middleware, proxy bypass behavior and error handling appear to be wrong and the server may fail to start in some environments. The bypass hook now behaves opposite to what I'd... |
vitejs__vite.8b47ff76.func_pm_op_flip__jf7vibzp | --- a/packages/vite/src/shared/hmr.ts
+++ b/packages/vite/src/shared/hmr.ts
@@ -261,7 +261,7 @@
}
}
- private async fetchUpdate(update: Update): Promise<(() => void) | undefined> {
+ private async fetchUpdate(update: Update): Promise<(() => void) | undefined<= {
const { path, acceptedPath, firstInvalid... | [
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests_... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: ReferenceError: Cannot access 'SYMBOL_RESOLVED_CONFIG' before initialization when importing server after recent hmr changes
### Bug summary
After the recent changes in packages/vite/src/shared/hmr.ts, attempting to start the server or import the server module ends up throwing a runtime ReferenceError about SYM... |
vitejs__vite.8b47ff76.func_pm_op_flip__kkd2bx85 | --- a/packages/vite/src/node/plugins/importAnalysisBuild.ts
+++ b/packages/vite/src/node/plugins/importAnalysisBuild.ts
@@ -71,27 +71,27 @@
declare const scriptRel: string
declare const seen: Record<string, boolean>
function preload(
- baseModule: () => Promise<unknown>,
+ baseModule: () =<= Promis>=<unknown>,
... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.spec.ts",
"pack... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | importAnalysisBuild.preload changes cause runtime ReferenceError / TypeError in dev/build (modulepreload / HMR)
### Description
After the recent changes to packages/vite/src/node/plugins/importAnalysisBuild.ts, running Vite in dev/build scenarios produces a number of runtime errors. In my environment this shows up as... |
vitejs__vite.8b47ff76.func_pm_op_flip__kpcqlr2n | --- a/packages/vite/src/node/optimizer/pluginConverter.ts
+++ b/packages/vite/src/node/optimizer/pluginConverter.ts
@@ -110,7 +110,7 @@
isSetupDone = true
}
- const usedNamespaces = new Set<string>()
+ const usedNamespaces = new Set<string<=()
return {
name: esbuildPlugin.name,
async options(in... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"pa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/server/__tests__/moduleGraph.spec.ts",
... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | pluginConverter.ts contains invalid token in Set declaration — importing optimizer crashes
After the recent change in packages/vite/src/node/optimizer/pluginConverter.ts, importing the optimizer code (or starting anything that pulls in the node/optimizer code path) fails to parse/initialize and causes boot/runtime fai... |
vitejs__vite.8b47ff76.func_pm_op_flip__kua83tso | --- a/packages/vite/src/node/plugins/oxc.ts
+++ b/packages/vite/src/node/plugins/oxc.ts
@@ -333,7 +333,7 @@
const transformOptions: OxcTransformOptions = _transformOptions
transformOptions.sourcemap =
- environment.config.mode !== 'build' ||
+ environment.config.mode !== 'build' &&
... | [
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-worker-runner.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-worker-runner.invoke.spec.ts",
"packages/vite/src/node/__tests__/runnerImport.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | oxc plugin changes break parsing of TypeScript/TSX files (parse errors like "Expected a semicolon")
Description
After the recent changes to the oxc-related plugin, importing plain TypeScript/TSX files (files that contain type annotations / interfaces / JSX) in the SSR/runner path fails with Rollup/parse errors instead... |
vitejs__vite.8b47ff76.func_pm_op_flip__ldgqw2ke | --- a/packages/vite/src/node/plugins/reporter.ts
+++ b/packages/vite/src/node/plugins/reporter.ts
@@ -164,8 +164,8 @@
const entries = (
await Promise.all(
Object.values(output).map(
- async (chunk): Promise<LogEntry | null> => {
- if (chunk.type ===... | [
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/n... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: reporter plugin throws runtime error after recent changes
### Bug summary
After the recent changes to packages/vite/src/node/plugins/reporter.ts, importing/using the reporter (or running a build that triggers it) results in a runtime error (ReferenceError / import initialization error) and the reporter/logging... |
vitejs__vite.8b47ff76.func_pm_op_flip__mhw2a01q | --- a/packages/vite/src/node/server/environment.ts
+++ b/packages/vite/src/node/server/environment.ts
@@ -340,8 +340,8 @@
}
function setupOnCrawlEnd(): CrawlEndFinder {
- const registeredIds = new Set<string>()
- const seenIds = new Set<string>()
+ const registeredIds = new Set>=strin<=>()
+ const seenIds = new... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | setupOnCrawlEnd changes break server lifecycle — runner undefined and SYMBOL_RESOLVED_CONFIG ReferenceError
After the recent edits to packages/vite/src/node/server/environment.ts the dev/ssr server lifecycle is broken. Creating the server (or running the ssr module runner) now throws initialization/runtime errors and ... |
vitejs__vite.8b47ff76.func_pm_op_flip__ng70kvnf | --- a/packages/vite/src/node/ssr/runnerImport.ts
+++ b/packages/vite/src/node/ssr/runnerImport.ts
@@ -15,7 +15,7 @@
export async function runnerImport<T>(
moduleId: string,
inlineConfig?: InlineConfig,
-): Promise<RunnerImportResult<T>> {
+): Promise>=RunnerImportResult<T>> {
const isModuleSyncConditionEnable... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | runnerImport.ts introduces a syntax/initialization problem that breaks SSR runner imports
Description
After the latest change to packages/vite/src/node/ssr/runnerImport.ts, importing the SSR runner modules causes strange initialization/runtime errors across the SSR tests and code that import the runner. The module im... |
vitejs__vite.8b47ff76.func_pm_op_flip__o0dwec37 | --- a/packages/vite/src/node/plugins/clientInjections.ts
+++ b/packages/vite/src/node/plugins/clientInjections.ts
@@ -38,9 +38,9 @@
injectConfigValues = await createClientConfigValueReplacer(config)
},
async transform(code, id) {
- const ssr = this.environment.config.consumer === 'server'
+ c... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/runnerImport.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-hmr.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrStacktrace.spec.ts",... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | EnvironmentPlugin: client inject logic inverted causing "injectConfigValues is not a function"
Description
After a recent change in clientInjections transform logic, SSR-related module loading and runner import flows sometimes throw a cryptic runtime error:
"injectConfigValues is not a function"
This shows up when ... |
vitejs__vite.8b47ff76.func_pm_op_flip__oky6jcgc | --- a/packages/vite/src/node/server/mixedModuleGraph.ts
+++ b/packages/vite/src/node/server/mixedModuleGraph.ts
@@ -585,7 +585,7 @@
// There are several methods missing. We can implement them if downstream
// projects are relying on them: add, clear, delete, difference, intersection,
// sDisjointFrom, is... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: Syntax/type assertion typo in mixedModuleGraph.ts breaks startup/compile
### Bug summary
After the recent change to packages/vite/src/node/server/mixedModuleGraph.ts, the file now contains an invalid type assertion token and the project fails to initialize. Importing or starting code that depends on this modul... |
vitejs__vite.8b47ff76.func_pm_op_flip__ovyz4his | --- a/packages/vite/src/node/server/environments/fullBundleEnvironment.ts
+++ b/packages/vite/src/node/server/environments/fullBundleEnvironment.ts
@@ -87,7 +87,7 @@
super(name, config, { ...context, disableDepsOptimizer: true })
}
- override async listen(_server: ViteDevServer): Promise<void> {
+ override ... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.sp... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | fullBundleEnvironment.listen: syntax/logic regressions break server/HMR startup
After the recent changes to packages/vite/src/node/server/environments/fullBundleEnvironment.ts I started hitting parsing/runtime errors when bringing up the dev server / running the repo. The file contains an invalid method signature and ... |
vitejs__vite.8b47ff76.func_pm_op_flip__rurwmo4k | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -1181,7 +1181,7 @@
if (thisModule) {
// CSS modules cannot self-accept since it exports values
const isSelfAccepting =
- !cssModulesCache.get(config)?.get(id) &&
+ !cssModulesC... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"package... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Incorrect behavior and syntax error introduced in css plugin
Describe the bug
After the recent changes to packages/vite/src/node/plugins/css.ts, two problems are observable:
1. The isSelfAccepting check for CSS modules now uses incorrect operator precedence which causes modules to be considered self-accepting (or not)... |
vitejs__vite.8b47ff76.func_pm_op_flip__ry9sisgh | --- a/packages/vite/src/node/plugins/workerImportMetaUrl.ts
+++ b/packages/vite/src/node/plugins/workerImportMetaUrl.ts
@@ -135,7 +135,7 @@
raw: string,
clean: string,
i: number,
-): Promise<WorkerType> {
+): Promise>=WorkerType> {
const commaIndex = clean.indexOf(',', i)
if (commaIndex === -1) {
re... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/optimizer/rolldownDepPlugin.sp... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | TypeScript parse error + broken worker type check after recent change in workerImportMetaUrl.ts
Hi,
After the recent changes in packages/vite/src/node/plugins/workerImportMetaUrl.ts the repo no longer builds cleanly and a bunch of unit tests fail. The change introduces an obvious TypeScript/logic bug which looks like... |
vitejs__vite.8b47ff76.func_pm_op_flip__t6y2prvf | --- a/packages/vite/src/node/publicDir.ts
+++ b/packages/vite/src/node/publicDir.ts
@@ -12,7 +12,7 @@
export async function initPublicFiles(
config: ResolvedConfig,
-): Promise<Set<string> | undefined> {
+): Promise>=Se>=<string> | undefined> {
let fileNames: string[]
try {
fileNames = await recursiveR... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | initPublicFiles signature typo breaks TypeScript compile / dev start
Describe the bug
The recent change to packages/vite/src/node/publicDir.ts corrupts the return type of initPublicFiles:
The function signature was changed from a valid TypeScript generic return type to a garbled token sequence (e.g. `Promise>=Se>=<st... |
vitejs__vite.8b47ff76.func_pm_op_flip__wyalh5p2 | --- a/packages/vite/src/node/config.ts
+++ b/packages/vite/src/node/config.ts
@@ -1322,7 +1322,7 @@
patchConfig: ((config: ResolvedConfig) => void) | undefined = undefined,
/** @internal */
patchPlugins: ((resolvedPlugins: Plugin[]) => void) | undefined = undefined,
-): Promise<ResolvedConfig> {
+): Promise<Re... | [
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | config.ts contains invalid TypeScript/JS tokens after recent changes
Description
After the recent changes to packages/vite/src/node/config.ts the file contains invalid tokens (e.g. stray "<=", ">=", "-" used where they shouldn't be) and several expressions were accidentally replaced. Importing/building the file now th... |
vitejs__vite.8b47ff76.func_pm_op_flip__xmafb61w | --- a/packages/vite/src/node/config.ts
+++ b/packages/vite/src/node/config.ts
@@ -2324,18 +2324,18 @@
resolveId: {
filter: { id: /^[^.#].*/ },
async handler(id, importer, { kind }) {
- if (!importer || path.isAbsolute(id) || isNodeBuiltin(id)) {
+ if (!importer && pa... | [
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: Syntax error in packages/vite/src/node/config.ts after recent changes ("Empty parenthesized expression")
Describe the bug
After the latest changes to packages/vite/src/node/config.ts, attempting to run tooling that transforms that file with the oxc transformer results in a syntax error:
Error
Error: Empty p... |
vitejs__vite.8b47ff76.func_pm_op_flip__ybl5dmf7 | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -656,7 +656,7 @@
)
// the chunk is empty if it's a dynamic entry chunk that only contains a CSS import
const isJsChunkEmpty = code === '' && !chunk.isEntry
- let isPureCssChunk = ... | [
"packages/vite/src/node/__tests__/plugins/index.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/plugins/license.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/nod... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | TypeError in CSS asset URL replacement — chunkCSS is undefined
### What happened?
After the recent changes to the CSS plugin, building a project that imports CSS with asset URLs crashes during CSS post-processing. The build aborts with:
TypeError: Cannot read properties of undefined (reading 'replace')
at resolve... |
vitejs__vite.8b47ff76.func_pm_op_flip__yl24wwcr | --- a/packages/vite/src/node/ssr/ssrTransform.ts
+++ b/packages/vite/src/node/ssr/ssrTransform.ts
@@ -490,7 +490,7 @@
const setScope = (node: _Node, name: string) => {
let scopeIds = scopeMap.get(node)
- if (scopeIds && scopeIds.has(name)) {
+ if (scopeIds || scopeIds.has(name)) {
return
}
... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-worker-runner.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadM... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ssrTransform throws TypeError: Cannot read properties of null (reading 'type') for simple SSR modules
Description
After the recent changes to packages/vite/src/node/ssr/ssrTransform.ts, transforming certain SSR modules results in a runtime TypeError:
TypeError: Cannot read properties of null (reading 'type')
at ... |
vitejs__vite.8b47ff76.func_pm_op_flip__ywfm6qlw | --- a/packages/vite/src/node/utils.ts
+++ b/packages/vite/src/node/utils.ts
@@ -643,7 +643,7 @@
export const ERR_SYMLINK_IN_RECURSIVE_READDIR =
'ERR_SYMLINK_IN_RECURSIVE_READDIR'
-export async function recursiveReaddir(dir: string): Promise<string[]> {
+export async function recursiveReaddir(dir: string): Promise... | [
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/plugin-legacy/src/__tests__/snippets.spec.ts",
"packages/vite/src/node/__tests__/constants.spec.ts",
"packages/vite/src/node/server/middlewares/__tests__/hostCheck.spec.ts",
"packages/plugin-legacy/src/__tests__/readme.spec.ts",
"packages/v... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Syntax error in packages/vite/src/node/utils.ts breaks build (vite:oxc)
#### Description
After the recent change to recursiveReaddir in packages/vite/src/node/utils.ts the file contains an invalid TypeScript/JS token in the function signature which causes the oxc transform to fail during bundling/transpile. The error s... |
vitejs__vite.8b47ff76.func_pm_op_flip__zo9u8f1k | --- a/packages/vite/src/node/plugins/asset.ts
+++ b/packages/vite/src/node/plugins/asset.ts
@@ -201,7 +201,7 @@
async handler(id) {
// raw requests, read from disk
if (rawRE.test(id)) {
- const file = checkPublicFile(id, config) || cleanUrl(id)
+ const file = checkPublicFile(i... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/no... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | asset plugin changes break SSR/HMR and prevent server from starting (ReferenceError)
Description
After the recent changes in packages/vite/src/node/plugins/asset.ts, SSR module runner / dev server startup and HMR behavior are broken. When creating a dev server or running the SSR module runner in a setup that imports a... |
vitejs__vite.8b47ff76.func_pm_op_swap__08of99ww | --- a/packages/vite/src/node/plugins/asset.ts
+++ b/packages/vite/src/node/plugins/asset.ts
@@ -201,7 +201,7 @@
async handler(id) {
// raw requests, read from disk
if (rawRE.test(id)) {
- const file = checkPublicFile(id, config) || cleanUrl(id)
+ const file = cleanUrl(id) || c... | [
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ReferenceError: Cannot access '__vite_ssr_import_*__' before initialization when creating server / building
When running the dev server or building an SSR bundle I get a ReferenceError during startup:
```
ReferenceError: Cannot access '__vite_ssr_import_11__' before initialization
at _createServer packages/vite/src... |
vitejs__vite.8b47ff76.func_pm_op_swap__0fq7rk8z | --- a/packages/vite/src/node/server/hmr.ts
+++ b/packages/vite/src/node/server/hmr.ts
@@ -856,7 +856,7 @@
node: EnvironmentModuleNode,
nodeChain: EnvironmentModuleNode[],
currentChain: EnvironmentModuleNode[] = [node],
- traversedModules = new Set<EnvironmentModuleNode>(),
+ traversedModules = EnvironmentMod... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vi... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | hmr: regression in node/server/hmr.ts causes runtime initialization errors on server start / SSR
Description
After the recent changes in packages/vite/src/node/server/hmr.ts, creating a dev server or running SSR appears to throw early initialization errors and leaves some runtime pieces undefined. Observed errors inc... |
vitejs__vite.8b47ff76.func_pm_op_swap__0ojjgk24 | --- a/packages/vite/src/node/server/middlewares/static.ts
+++ b/packages/vite/src/node/server/middlewares/static.ts
@@ -141,10 +141,8 @@
// also skip internal requests `/@fs/ /@vite-client` etc...
const cleanedUrl = cleanUrl(req.url!)
if (
- cleanedUrl.endsWith('/') ||
- path.extname(cleanedUrl... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/n... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Static middleware ignores alias redirects and can crash on denied-file errors
### Description
After the recent changes to the static file middleware, static requests that should be rewritten by config.resolve.alias are no longer redirected reliably. In my setup requests that previously resolved to aliased files now ei... |
vitejs__vite.8b47ff76.func_pm_op_swap__1l28mll7 | --- a/packages/vite/src/node/plugins/index.ts
+++ b/packages/vite/src/node/plugins/index.ts
@@ -241,9 +241,9 @@
}
function extractFilter<T extends Function, F>(
- hook: ObjectHook<T, { filter?: F }> | undefined,
+ hook: ObjectHook<T, { filter?: > ERROR F,
) {
- return hook && 'filter' in hook && hook.filter ? h... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/http.spec.ts",
"packages/vite/s... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | extractFilter throws when hook is undefined / malformed type annotation introduced
Description
A recent change in packages/vite/src/node/plugins/index.ts seems to have two problems in extractFilter:
- There's a stray token inserted into the type annotation (something like "> ERROR" in the ObjectHook generic), which ... |
vitejs__vite.8b47ff76.func_pm_op_swap__2avunk4w | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -1919,7 +1919,7 @@
async function resolvePostcssConfig(
config: ResolvedConfig,
-): Promise<PostCSSConfigResult | null> {
+): PostCSSConfigResult > Promise | null> {
let result = postcssConfigCache.get(config)
if (res... | [
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | resolvePostcssConfig signature + plugins default change breaks server startup / HMR
Description
After the recent changes in packages/vite/src/node/plugins/css.ts the dev server / SSR HMR startup now throws runtime errors during server creation and HMR initialization. The failure appears to surface when the server res... |
vitejs__vite.8b47ff76.func_pm_op_swap__4hjgrun4 | --- a/packages/vite/src/module-runner/runner.ts
+++ b/packages/vite/src/module-runner/runner.ts
@@ -120,7 +120,7 @@
}
private processImport(
- exports: Record<string, any>,
+ exports: string > Record, any>,
fetchResult: ResolvedResult,
metadata?: SSRImportMetadata,
) {
@@ -128,7 +128,7 @@
... | [
"packages/vite/src/node/__tests__/build.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/plugins/hooks.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vit... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ReferenceError: Cannot access '__vite_ssr_import_*__' before initialization when running SSR module runner
### Steps to reproduce
Create a minimal vite project that uses the SSR module runner and a pair of modules with a circular-ish import pattern. For example:
server.mjs
```js
import { createServer } from 'vite'
... |
vitejs__vite.8b47ff76.func_pm_op_swap__4rut793n | --- a/packages/vite/src/node/plugins/html.ts
+++ b/packages/vite/src/node/plugins/html.ts
@@ -182,20 +182,7 @@
function traverseNodes(
node: DefaultTreeAdapterMap['node'],
- visitor: (node: DefaultTreeAdapterMap['node']) => void,
-) {
- if (node.nodeName === 'template') {
- node = (node as DefaultTreeAdapter... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | [Bug]: Syntax error in html plugin — traverseNodes signature corrupted
Bug summary
After the most recent changes to packages/vite/src/node/plugins/html.ts the traverseNodes function is syntactically broken. Importing or requiring the html plugin now raises a parse/syntax error (there's a stray line where the function... |
vitejs__vite.8b47ff76.func_pm_op_swap__59at7eiy | --- a/packages/vite/src/node/plugins/terser.ts
+++ b/packages/vite/src/node/plugins/terser.ts
@@ -58,13 +58,11 @@
{
shouldUseFake(_terserPath, _code, options) {
return !!(
- (typeof options.mangle === 'object' &&
+ typeof options.output?.comments === 'function' || (typeo... | [
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | terser plugin: unexpected token ("che") in options.comments check breaks build
### Problem
After the recent changes to packages/vite/src/node/plugins/terser.ts, building/starting the project fails because there's an unexpected token appended to a boolean expression in the terser plugin. This prevents the file from bein... |
vitejs__vite.8b47ff76.func_pm_op_swap__64jrye7b | --- a/packages/vite/src/node/utils.ts
+++ b/packages/vite/src/node/utils.ts
@@ -468,17 +468,14 @@
}
export function numberToPos(source: string, offset: number | Pos): Pos {
- if (typeof offset !== 'number') return offset
+ if ('number') return offset
if (offset > source.length) {
throw new Error(
`... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/vite/src/node/__tests__/constants.spec.ts",
"packages/plugin-legacy/src/__tests__/snippets.spec.ts",
"packages/vite/src/node/server/middlewares/__tests__/hostCheck.spec.ts",
"packages/plugin-legacy/src/__tests__/readme.spec.ts",
"packages/v... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Importing utils.ts (numberToPos) causes a syntax error
Description
After the recent changes to packages/vite/src/node/utils.ts, attempting to import/use the numberToPos helper results in a syntax error during transform/compile.
To reproduce
Create a small file that imports numberToPos from the repo and run it with ... |
vitejs__vite.8b47ff76.func_pm_op_swap__6ohus85c | --- a/packages/vite/src/node/utils.ts
+++ b/packages/vite/src/node/utils.ts
@@ -1299,10 +1299,8 @@
options.ssr?.optimizeDeps,
]) {
if (
- opt != null &&
- opt.rollupOptions != null &&
- opt.rolldownOptions != null
- ) {
+ opt.rolldownOptions != null && opt != null &&
+ opt.rollu... | [
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packages/vite/src/node/__tests__/constants.spec.ts",
"packages/plugin-legacy/src/__tests__/snippets.spec.ts",
"packages/vite/src/node/server/middlewares/__tests__/hostCheck.spec.ts",
"packages/plugin-legacy/src/__tests__/readme.spec.ts",
"packages/v... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Syntax error in packages/vite/src/node/utils.ts — "Expected `)` but found `{`"
Description
After the recent change to packages/vite/src/node/utils.ts there's a syntax error which prevents the code from being parsed by the build/bundler (oxc). Opening the file around line ~1300 you can see the conditional has an unexpe... |
vitejs__vite.8b47ff76.func_pm_op_swap__6ruapnq7 | --- a/packages/vite/src/node/plugins/css.ts
+++ b/packages/vite/src/node/plugins/css.ts
@@ -458,16 +458,14 @@
// styles initialization in buildStart causes a styling loss in watch
const styles = new Map<string, string>()
// queue to emit css serially to guarantee the files are emitted in a deterministic order
... | [
"packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"pa... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Cannot access SYMBOL_RESOLVED_CONFIG before initialization when creating server (after css plugin changes)
After the recent changes to the css plugin, creating a Vite dev server (or otherwise resolving config) can throw a ReferenceError during module initialization. I hit this when calling createServer — instead of ge... |
vitejs__vite.8b47ff76.func_pm_op_swap__7n7cqqwz | --- a/packages/vite/src/node/plugins/define.ts
+++ b/packages/vite/src/node/plugins/define.ts
@@ -57,7 +57,7 @@
userDefine[key] = handleDefineValue(environment.config.define[key])
// make sure `import.meta.env` object has user define properties
- if (isBuild && key.startsWith('import.meta.env.')) {... | [
"packages/vite/src/node/__tests__/plugins/define.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/node/__tests__/plugins/index.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-source-maps.spec.ts",
"pac... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/plugins/import.spec.ts",
"pa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | Title: TypeError thrown when checking for import.meta.env.SSR in define plugin
### Description
After a recent change in the define plugin, running code that exercises the define handling can throw a TypeError when checking for the presence of import.meta.env.SSR. Instead of performing a normal membership check, the r... |
vitejs__vite.8b47ff76.func_pm_op_swap__8ne3gd74 | --- a/packages/vite/src/node/server/environments/fullBundleEnvironment.ts
+++ b/packages/vite/src/node/server/environments/fullBundleEnvironment.ts
@@ -224,7 +224,7 @@
}
this.invalidateCalledModules.get(client)!.add(m.path)
- let update: BindingClientHmrUpdate['update'] | undefined
+ let updat... | [
"packages/vite/src/node/__tests__/environment.spec.ts",
"packages/vite/src/node/ssr/runtime/__tests__/server-runtime.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrLoadModule.spec.ts",
"packages/vite/src/node/__tests__/shortcuts.spec.ts",
"packages/v... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | ReferenceError: Cannot access '__vite_ssr_import_*' before initialization after HMR invalidate change in fullBundleEnvironment
### Bug summary
After the recent changes to packages/vite/src/node/server/environments/fullBundleEnvironment.ts, starting the dev server / running the server bootstrap can throw a ReferenceEr... |
vitejs__vite.8b47ff76.func_pm_op_swap__8o6z13hk | --- a/packages/vite/src/node/server/mixedModuleGraph.ts
+++ b/packages/vite/src/node/server/mixedModuleGraph.ts
@@ -106,11 +106,11 @@
},
})
}
- _getModuleObjectUnion(prop: 'meta'): Record<string, any> | undefined {
+ _getModuleObjectUnion(prop: 'meta'): Record<string, | < any {
const _clientValue ... | [
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/ssr/__tests__/ssrTransform.spec.ts",
"packages/vite/src/node/__tests__/scan.spec.ts",
"packages/vite/src/nod... | [
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | mixedModuleGraph.ts has a broken type annotation causing runtime/init errors
Description
After the recent change to packages/vite/src/node/server/mixedModuleGraph.ts the TypeScript signature for _getModuleObjectUnion appears to be malformed. This leads to build/runtime initialization problems (ReferenceError about sym... |
vitejs__vite.8b47ff76.func_pm_op_swap__8sbi3qcq | --- a/packages/vite/src/node/logger.ts
+++ b/packages/vite/src/node/logger.ts
@@ -167,8 +167,7 @@
export function printServerUrls(
urls: ResolvedServerUrls,
- optionsHost: string | boolean | undefined,
- info: Logger['info'],
+ undefined, | optionsHost: string | booleaninfo'],
): void {
const colorUrl = (u... | [
"packages/vite/src/node/__tests__/plugins/css.spec.ts",
"packages/vite/src/node/__tests__/plugins/oxc.spec.ts",
"packages/vite/src/node/server/__tests__/pluginContainer.spec.ts",
"packages/vite/src/node/__tests__/config.spec.ts",
"packages/vite/src/node/__tests__/resolve.spec.ts",
"packages/vite/src/node/... | [
"packages/vite/src/node/__tests__/plugins/importGlob/parse.spec.ts",
"packages/vite/src/node/__tests__/plugins/pluginFilter.spec.ts",
"packages/vite/src/node/__tests__/utils.spec.ts",
"packages/vite/src/node/__tests__/plugins/esbuild.spec.ts",
"packages/vite/src/node/__tests__/assetSource.spec.ts",
"packa... | swebench/swesmith.x86_64.vitejs_1776_vite.8b47ff76 | swesmith/vitejs__vite.8b47ff76 | printServerUrls signature corrupted in packages/vite/src/node/logger.ts causing parse error on import
Description
A recent change appears to have mangled the function signature for printServerUrls in packages/vite/src/node/logger.ts. The file now contains an invalid parameter list which causes the TypeScript/JS parse... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.