fix bug with too many "/" after a ipfs:// protocol

Author: Metroxe

src/resolve.ts

@@ -104,7 +104,7 @@ async function resolve(uri: string, options?: ResolveOptions): Promise<ResolveOu
     // check to see if the link has the ipfs:// or ipns:// protocol/scheme
     else if ((uri as string).startsWith("ipfs://") || (uri as string).startsWith("ipns://")) {
 
-        const cidWithOptionalPath = (uri as string).substring(8);
+        const cidWithOptionalPath = (uri as string).substring(7);
 
         // check to see if the CID after the ipfs protocal/scheme is valid
         if (!isIPFS.cid(cidWithOptionalPath) && !isIPFS.cidPath(cidWithOptionalPath)) {

src/test.ts

@@ -31,12 +31,12 @@ describe("Tests the ipfs-race library.", () => {
     });
 
     it("ipfs protocol with no path", async () => {
-        const {response, urlResolvedFrom} = await resolve(`ipfs:///${testCidWithNoPath}`);
+        const {response, urlResolvedFrom} = await resolve(`ipfs://${testCidWithNoPath}`);
         expect(await response.json(), urlResolvedFrom).to.deep.equal(testCidWithNoPathResult)
     });
 
     it("ipfs protocol with path", async () => {
-        const {response, urlResolvedFrom} = await resolve(`ipfs:///${testCidWithPath}`);
+        const {response, urlResolvedFrom} = await resolve(`ipfs://${testCidWithPath}`);
         expect(await response.json(), urlResolvedFrom).to.deep.equal(testCidWithPathResult)
     });