fix(correct-ts-specifiers): don't crash when specifier doesn't resolve (#60)

Author: JakobJingleheimer

recipes/correct-ts-specifiers/src/fexists.test.ts

@@ -137,5 +137,13 @@ describe('fexists', () => {
 			assert.equal(await fexists(parentPath, specifier), false);
 			assert.equal(mock__access.calls[0].arguments[0], specifier, RESOLVED_SPECIFIER_ERR);
 		});
+
+		it('should return `false` when the specifier can’t be resolved', async () => {
+			mock__resolveSpecifier.mockImplementationOnce(function MOCK__resolveSpecifier(_pp, _specifier) {
+				throw Object.assign(new Error('ERR_MODULE_NOT_FOUND'), { code: 'ERR_MODULE_NOT_FOUND' });
+			});
+
+			assert.equal(await fexists(parentPath, 'noexists'), false);
+		});
 	});
 });

recipes/correct-ts-specifiers/src/fexists.ts

@@ -11,7 +11,13 @@ export function fexists(
 	parentPath: FSAbsolutePath | ResolvedSpecifier,
 	specifier: Specifier,
 ) {
-	const resolvedSpecifier = resolveSpecifier(parentPath, specifier) as FSAbsolutePath;
+	let resolvedSpecifier: FSAbsolutePath;
+	try {
+		resolvedSpecifier = resolveSpecifier(parentPath, specifier) as FSAbsolutePath;
+	} catch (err) {
+		if ((err as NodeJS.ErrnoException).code !== 'ERR_MODULE_NOT_FOUND') throw err;
+		return false;
+	}
 
 	return fexistsResolved(resolvedSpecifier);
 }