Fix: Template Literal Syntax in Error Handling for Asset File Paths in Metro

[fredrikburmester]

Hi! 👋

Today, I used patch-package to patch metro@0.80.6 for the project I'm working on.

While working, I noticed an issue with asset file path error handling in metro. The error message was not formatting the file path correctly, making debugging more difficult. To resolve this, I applied a small patch that corrects the template literal syntax for error messages.

Here is the diff that solved my problem:

diff --git a/node_modules/metro/src/node-haste/lib/AssetPaths.js b/node_modules/metro/src/node-haste/lib/AssetPaths.js
index 7d44292..4a2577a 100644
--- a/node_modules/metro/src/node-haste/lib/AssetPaths.js
+++ b/node_modules/metro/src/node-haste/lib/AssetPaths.js
@@ -41,7 +41,7 @@ function tryParse(filePath, platforms) {
 function parse(filePath, platforms) {
   const result = tryParse(filePath, platforms);
   if (result == null) {
-    throw new Error("invalid asset file path: `${filePath}");
+    throw new Error(`invalid asset file path: ${filePath}`);
   }
   return result;
 }

This change ensures that the error message correctly includes the file path, aiding in troubleshooting and enhancing the developer experience. I believe this might be beneficial for others facing similar issues.

[robhogan]

Hi, thanks! That looks good to me - would you like to submit a PR?

[fredrikburmester]

@robhogan I submitted a PR here.