chore: cleanup

vitejs · Jan 11, 2024 · f8c39e1 · f8c39e1
1 parent 9948f85
commit f8c39e1
Showing 1 changed file with 3 additions and 9 deletions.
diff --git a/packages/vite/src/node/ssr/runtime/runtime.ts b/packages/vite/src/node/ssr/runtime/runtime.ts
@@ -194,10 +194,10 @@ export class ViteRuntime {
   // usually import locations are already resolved by Vite during transformation, so it _should_ be fine
   // TODO: is it a good idea? what if id has a query string? do we want to remove &t= like in vite-node? do we want to allow extendin it?
   private async cachedModule(
-    id: string,
+    rawId: string,
     importer?: string,
   ): Promise<ResolvedResult> {
-    id = unwrapId(id)
+    const id = unwrapId(rawId)
     const file = this.idToFileMap.get(id)
     if (file) {
       const mod = this.moduleCache.get(file)
@@ -219,13 +219,7 @@ export class ViteRuntime {
 
   private async directRequest(
     id: string,
-    {
-      file,
-      externalize,
-      code: transformed,
-      type,
-      id: moduleId,
-    }: ResolvedResult,
+    { file, externalize, code: transformed, id: moduleId }: ResolvedResult,
     _callstack: string[],
     metadata?: SSRImportMetadata,
   ): Promise<any> {