Turbopack: Emit an issue on unknown module types instead of falling b…

…ack to raw (#7785)

This causes Turbopack to emit an error-level issue when a module doesn’t
have a type set on it. Previously, it fell back to assuming a raw type.


Closes PACK-2802

crates/turbopack/src/lib.rs

@@ -532,7 +532,25 @@ async fn process_default_internal(
         }
     }
 
-    let module_type = current_module_type.unwrap_or(ModuleType::Raw).cell();
+    let module_type = match current_module_type {
+        Some(module_type) => module_type,
+        None => {
+            ModuleIssue {
+                ident,
+                title: StyledString::Text("Unknown module type".to_string()).cell(),
+                description: StyledString::Text(
+                    r"This module doesn't have an associated type. Use a known file extension, or register a loader for it.
+
+Read more: https://nextjs.org/docs/app/api-reference/next-config-js/turbo#webpack-loaders".to_string(),
+                )
+                .cell(),
+            }
+            .cell()
+            .emit();
+
+            return Ok(ProcessResult::Ignore.cell());
+        }
+    }.cell();
 
     Ok(apply_module_type(
         current_source,

crates/turbopack/src/module_options/mod.rs

@@ -330,6 +330,12 @@ impl ModuleOptions {
                 ]),
                 vec![ModuleRuleEffect::ModuleType(ModuleType::Static)],
             ),
+            ModuleRule::new(
+                ModuleRuleCondition::any(vec![ModuleRuleCondition::ResourcePathEndsWith(
+                    ".node".to_string(),
+                )]),
+                vec![ModuleRuleEffect::ModuleType(ModuleType::Raw)],
+            ),
             ModuleRule::new(
                 ModuleRuleCondition::any(vec![ModuleRuleCondition::ResourcePathEndsWith(
                     ".wasm".to_string(),