feat: add numberOfSecretBytes parameter to Payload and adjust related functionality

Added optional numberOfSecretBytes parameter to the Payload interface to specify the number of authenticator secret bytes (default: 20).

Added the numberOfSecretBytes parameter in the config to use the value from the Payload or fallback to the default.

Adjusted and added corresponding test cases to validate the new parameter and ensure compatibility with existing behavior.

This change provides greater flexibility in configuring the number of secret bytes for the authenticator while maintaining backward compatibility.

Author: FinotiLucas

lib/secret.ts

@@ -48,8 +48,9 @@ export async function generateSecret(
   const config = {
     name: encodeURIComponent(payload?.name ?? "App"),
     account: payload.account ? encodeURIComponent(`:${payload.account}`) : "",
-    counter: strategy === "HOTP" ? (payload.counter ?? 0).toString() : undefined,
-    numberOfBytes: payload.numberOfSecretBytes ?? 20
+    counter:
+      strategy === "HOTP" ? (payload.counter ?? 0).toString() : undefined,
+    numberOfBytes: payload.numberOfSecretBytes ?? 20,
   } as const;
 
   const secret = authenticator.generateSecret(config.numberOfBytes);

tests/hotp.spec.ts

@@ -6,7 +6,7 @@ const { secret } = await generateSecret({
   name: "App",
   account: "exemple@exemple.com",
   counter: 0,
-  numberOfSecretBytes: 20
+  numberOfSecretBytes: 20,
 });
 
 const counter = 0;

tests/totp.spec.ts

@@ -7,7 +7,7 @@ const { secret } = await generateSecret(
     name: "App",
     account: "exemple@exemple.com",
     counter: 0,
-    numberOfSecretBytes: 20
+    numberOfSecretBytes: 20,
   },
   "HOTP",
 );