Usages regex is not comprehensive enough when types are invovled

[marcins]

When updating our codebase to TypeScript we found instances where the usages regex was not comprehensive enough to find all usages. While ideally we would move to an AST based approach, in the meantime @MonicaOlejniczak provided a patch that enhanced the regex to cover more usages.

react-loosely-lazy/packages/plugins/parcel-transformer/src/utils.ts

Lines 58 to 59 in 2a9cbc6

	// This is going to assume you call the library, with an optional generic type parameter, and no whitespace...
	const usageStartRe = new RegExp(`${importSpecifier}(?:<.+>)?\\(`);

-    const usageStartRe = new RegExp(`${importSpecifier}(?:<.+>)?\\(`);
+    const usageStartRe = new RegExp(`${importSpecifier}(?:<[^>]+[>\s]+)?\\(`);