fix formatting and linting issues

Author: jd1378

Diff for: .vscode/launch.json

@@ -52,7 +52,7 @@
         "--allow-all",
         "--allow-env"
       ],
-      "outputCapture": "std",
+      "outputCapture": "std"
     }
   ]
-}
+}

Diff for: .vscode/settings.json

@@ -2,15 +2,15 @@
   "deno.enable": true,
   "[typescript]": {
     "editor.defaultFormatter": "denoland.vscode-deno",
-    "editor.formatOnSave": true,
+    "editor.formatOnSave": true
   },
   "[typescriptreact]": {
-    "editor.defaultFormatter": "denoland.vscode-deno",
+    "editor.defaultFormatter": "denoland.vscode-deno"
   },
   "deno.unstable": true,
   "deno.lint": true,
   "debug.javascript.unmapMissingSources": true,
   "deno.import_intellisense_origins": {
     "https://deno.land": true
-  },
-}
+  }
+}

Diff for: CHANGELOG.md

@@ -1,4 +1,3 @@
-
 # Changelog
 
 ## v4.1.0
@@ -24,7 +23,8 @@ Thanks @jonasb
 ## v4.0.0
 
 - BREAKING CHANGE: implement rfc6265 path matching properly and add test.
-- change `CookieJar.getCookieString()` to use `Cookie.canSendTo` function filtering cookies for a url
+- change `CookieJar.getCookieString()` to use `Cookie.canSendTo` function
+  filtering cookies for a url
 
 ## v3.0.0
 
@@ -57,7 +57,8 @@ Thanks @jonasb
 
 ## v2.2.2
 
-- `CookieJar.setCookie()`: set cookie path from url's pathname if path is not defined inside cookie string (or Cookie). (it was already done for domain.)
+- `CookieJar.setCookie()`: set cookie path from url's pathname if path is not
+  defined inside cookie string (or Cookie). (it was already done for domain.)
 
 ## v2.2.1
 
@@ -73,14 +74,17 @@ Thanks @jonasb
 
 ## v2.1.0
 
-- add `fetchFn` to wrap options. this allows you to wrap your fetch multiple times to add other helpers.
+- add `fetchFn` to wrap options. this allows you to wrap your fetch multiple
+  times to add other helpers.
 
 ## v2.0.1
 
 - fix headers not merged correctly and add test
 
 ## v2.0.0
 
-- now `value`, `secure`, `httpOnly`, `maxAge`, `expires`, `sameSite` props will only be strictly checked only if
-  when retrieving the cookies using `CookieOptions`, which means if you pass a cookie,
-  it will only be checked if `name`, `path` and `domain` match. This should solve issue of replacing cookies.
+- now `value`, `secure`, `httpOnly`, `maxAge`, `expires`, `sameSite` props will
+  only be strictly checked only if when retrieving the cookies using
+  `CookieOptions`, which means if you pass a cookie, it will only be checked if
+  `name`, `path` and `domain` match. This should solve issue of replacing
+  cookies.

Diff for: README.md

@@ -1,15 +1,21 @@
 # deno-another-cookiejar
 
-This library offers a fetch wrapper that retain cookies. This library also provides a simple cookiejar;
+This library offers a fetch wrapper that retain cookies. This library also
+provides a simple cookiejar;
 
-Why the name ? because I didn't want to reserve the cookiejar name, since this library may not be good at it. (But I hope you like it)
+Why the name ? because I didn't want to reserve the cookiejar name, since this
+library may not be good at it. (But I hope you like it)
 
 ## usage
 
 you can import `Cookie`, `CookieJar`, `wrapFetch` from `mod.ts` file.
 
 ```js
-import { Cookie, CookieJar, wrapFetch} from 'https://deno.land/x/[email protected]/mod.ts';
+import {
+  Cookie,
+  CookieJar,
+  wrapFetch,
+} from "https://deno.land/x/[email protected]/mod.ts";
 ```
 
 ### wrapFetch
@@ -30,8 +36,8 @@ const fetch = wrapFetch({ cookieJar });
 fetch("http://example.com");
 // and you can read your cookies from the jar
 cookieJar.getCookie({
-  name: 'cookieName',
-})?.value // your cookie value
+  name: "cookieName",
+})?.value; // your cookie value
 ```
 
 You can play around with it too see what it has to offer!
@@ -47,14 +53,14 @@ you can create cookies in two ways:
 ```js
 // first: using Cookie constructor with CookieOptions
 const cookie = new Cookie({
-  name: 'foo',
-  value: 'bar'
+  name: "foo",
+  value: "bar",
 });
 ```
 
 ```js
-// second: 
-const cookie = Cookie.from('foo=bar;'); // any string from Set-Cookie header value is also valid.
+// second:
+const cookie = Cookie.from("foo=bar;"); // any string from Set-Cookie header value is also valid.
 ```
 
 ### CookieJar
@@ -71,42 +77,42 @@ const cookieJar = new CookieJar(cookiesArray); // cookiesArray: Array<Cookie> |
 
 #### Note on retrieving cookies (+v2.0.0)
 
-You can get cookies using either `CookieOptions` or a `Cookie` itself.
-The difference is if you use `CookieOptions`, it will strictly check any prop that is passed against the cookie.
-But if you use a `Cookie` object, it will only check `name`, `path` and `domain`.
+You can get cookies using either `CookieOptions` or a `Cookie` itself. The
+difference is if you use `CookieOptions`, it will strictly check any prop that
+is passed against the cookie. But if you use a `Cookie` object, it will only
+check `name`, `path` and `domain`.
 
 ### JSON serializing `Cookie`
 
 Each cookie object is easily serialized and deserialized. Example:
 
 ```js
-const exampleOption = { name: 'foo' , value: 'bar' };
+const exampleOption = { name: "foo", value: "bar" };
 
 const myCookie = new Cookie(exampleOption);
 
-new Cookie ( 
+new Cookie(
   JSON.parse(
-    JSON.stringify(myCookie)
-  )
+    JSON.stringify(myCookie),
+  ),
 ).toString() === myCookie.toString(); // true
-
 ```
 
 ### JSON serializing `CookieJar`
 
 You can even easily serialize your `CookierJar`. Example:
 
 ```js
-const exampleOption = { name: 'foo' , value: 'bar' };
+const exampleOption = { name: "foo", value: "bar" };
 
 const myCookie = new Cookie(exampleOption);
 
 const cookieJar = new CookieJar([myCookie]);
 
-new CookieJar (
+new CookieJar(
   JSON.parse(
-    JSON.stringify(cookieJar)
-  )
+    JSON.stringify(cookieJar),
+  ),
 ).cookies[0].toString() === myCookie.toString(); // true
 ```
 
@@ -118,8 +124,10 @@ run with `deno test --allow-net`
 
 ## notes
 
-This library is only tested lightly. you can contribute to this if you want to make it better, but I probably won't add much feature/test anymore.
+This library is only tested lightly. you can contribute to this if you want to
+make it better, but I probably won't add much feature/test anymore.
 
-This library does not strictly follow the specs, but does try to follow it loosely. just keep it in mind when using so you don't get surprises.
+This library does not strictly follow the specs, but does try to follow it
+loosely. just keep it in mind when using so you don't get surprises.
 
 does not support handling of `__Secure-` and `__Host-` cookies.

Diff for: cookie_jar.ts

@@ -60,7 +60,7 @@ const MAX_TIME = 2147483647000; // 31-bit max
 /**
  *  Cookies with longer paths are listed before cookies with
  *  shorter paths.
- * 
+ *
  *  Among cookies that have equal-length path fields, cookies with
  *  earlier creation-times are listed before cookies with later
  *  creation-times."
@@ -101,10 +101,10 @@ export class CookieJar {
   }
 
   /**
-   * Sets or replaces a cookie inside the jar. 
+   * Sets or replaces a cookie inside the jar.
    * Only sets new cookies if cookie is valid and not expired.
    * Validation and expiration checks are not run when replacing a cookie.
-   * @param url - the url that this cookie from received from. mainly used by the fetch wrapper. 
+   * @param url - the url that this cookie from received from. mainly used by the fetch wrapper.
    *              will automatically set domain and path if provided and it was not found inside Cookie/cookiestring.
    */
   setCookie(cookie: Cookie | string, url?: string | Request | URL) {
@@ -143,7 +143,7 @@ export class CookieJar {
     this.cookies.sort(cookieCompare);
   }
 
-  /** 
+  /**
    * Gets the first cooking matching the defined properties of a given Cookie or CookieOptions.
    * returns undefined if not found or expired. `creationDate` prop is not checked.
    * Also removes the cookie and returns undefined if cookie is expired.
@@ -208,8 +208,8 @@ export class CookieJar {
   }
 
   /**
-   * Removes first cookie that matches the given option. 
-   * 
+   * Removes first cookie that matches the given option.
+   *
    * Returns the deleted cookie if found or undefined otherwise.
    */
   removeCookie(options: CookieOptions | Cookie): Cookie | undefined {
@@ -223,13 +223,13 @@ export class CookieJar {
   /**
    * Removes all cookies that matches the given option.
    * If options is not given, all cookies will be deleted.
-   * 
+   *
    * Returns the deleted cookies if found or undefined otherwise.
    */
   removeCookies(options?: CookieOptions | Cookie): Array<Cookie> | undefined {
     if (options) {
       const deletedCookies: Cookie[] = [];
-      this.cookies = this.cookies.filter((cookie, index) => {
+      this.cookies = this.cookies.filter((cookie) => {
         if (cookieMatches(options, cookie)) {
           deletedCookies.push(cookie);
           return false;

Diff for: fetch_wrapper_test.ts

@@ -17,7 +17,7 @@ handlers = [];
 
 async function handleServer1() {
   await delay(100);
-  server1 = serve({ hostname: "0.0.0.0", port: 54933 });
+  server1 = serve({ hostname: "localhost", port: 54933 });
   for await (const request of server1) {
     if (request.url === "/") {
       const bodyContent = request.headers.get("cookie") || "";
@@ -34,7 +34,7 @@ async function handleServer1() {
 
 async function handleServer2() {
   await delay(100);
-  server2 = serve({ hostname: "0.0.0.0", port: 54934 });
+  server2 = serve({ hostname: "localhost", port: 54934 });
   for await (const request of server2) {
     if (request.url === "/") {
       const bodyContent = request.headers.get("cookie") || "";