Fix panic when compiling webpack by handling ElementAccessExpression in Node.Text()

internal/ast/utilities.go

@@ -1311,6 +1311,11 @@ func GetElementOrPropertyAccessName(node *Node) string {
 	if name == nil {
 		return ""
 	}
+	// If we get back the original node and it's an ElementAccessExpression,
+	// it means it had a non-literal argument, so return empty string
+	if name == node && node.Kind == KindElementAccessExpression {
+		return ""
+	}
 	return name.Text()
 }
 

testdata/tests/cases/compiler/elementAccessExpressionInJS.ts

@@ -0,0 +1,26 @@
+// @ts-check
+// @checkJs: true
+
+// Create an object with properties
+const obj = { staticKey: "value", 0: "numeric" };
+
+// Use ElementAccessExpression with string literal (should work)
+const value1 = obj["staticKey"];
+
+// Use ElementAccessExpression with numeric literal (should work)
+const value2 = obj[0];
+
+// Use ElementAccessExpression with variable (would trigger the panic before fix)
+const dynamicKey = "dynamicKey";
+const value3 = obj[dynamicKey]; 
+
+// Nested ElementAccessExpression (common in webpack code)
+const nestedObj = { inner: { deep: "value" } };
+const innerKey = "inner";
+const deepKey = "deep";
+const nestedValue = nestedObj[innerKey][deepKey];
+
+// Create an array and access with ElementAccessExpression
+const arr = ["first", "second", "third"];
+const idx = 1;
+const arrValue = arr[idx];