fix: improve isBareSpecifier and isRelativeSpecifier logic for better accuracy

Author: YieldRay

src/specifier.test.ts

@@ -32,13 +32,17 @@ describe("isRelativeSpecifier", () => {
   it("returns true for ./ and ../", () => {
     assert.ok(isRelativeSpecifier("./foo"));
     assert.ok(isRelativeSpecifier("../bar"));
-    assert.ok(isRelativeSpecifier(".hidden"));
   });
 
   it("returns true for absolute paths starting with /", () => {
     assert.ok(isRelativeSpecifier("/abs"));
   });
 
+  it("returns false for dot-prefixed names without slash", () => {
+    assert.ok(!isRelativeSpecifier(".hidden"));
+    assert.ok(!isRelativeSpecifier(".tsconfig.json"));
+  });
+
   it("returns false for bare specifiers and URLs", () => {
     assert.ok(!isRelativeSpecifier("react"));
     assert.ok(!isRelativeSpecifier("https://esm.sh/react"));

src/specifier.ts

@@ -1,7 +1,7 @@
 import ts from "typescript";
 
 export function isBareSpecifier(specifier: string): boolean {
-  if (specifier.match(/^\.*\//)) return false;
+  if (isRelativeSpecifier(specifier)) return false;
 
   try {
     new URL(specifier);
@@ -13,7 +13,11 @@ export function isBareSpecifier(specifier: string): boolean {
 
 /* Helper to check if a specifier is relative, note that it includes both relative paths and absolute paths */
 export function isRelativeSpecifier(specifier: string): boolean {
-  return specifier.startsWith(".") || specifier.startsWith("/");
+  return (
+    specifier.startsWith("./") ||
+    specifier.startsWith("../") ||
+    specifier.startsWith("/")
+  );
 }
 
 export function collectSpecifiers(sourceFile: ts.SourceFile): Set<string> {