Allow authorizedFetch to proceed without authenticated user

Instead of throwing an error when no user is logged in, authorizedFetch now
logs a warning and proceeds with the fetch without the Authorization header.
This allows endpoints that support both authenticated and unauthenticated
requests to work seamlessly. Bump to v1.0.8.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ianwieds

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "ultimate-jekyll-manager",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "description": "Ultimate Jekyll dependency manager",
   "main": "dist/index.js",
   "exports": {
@@ -79,7 +79,7 @@
     "cheerio": "^1.2.0",
     "chrome-launcher": "^1.2.1",
     "dotenv": "^17.3.1",
-    "fast-xml-parser": "^5.5.7",
+    "fast-xml-parser": "^5.5.8",
     "fs-jetpack": "^5.1.0",
     "glob": "^13.0.6",
     "gulp-clean-css": "^4.3.0",

package.json

@@ -20,20 +20,19 @@ export async function authorizedFetch(url, options = {}) {
   const user = auth.currentUser;
 
   if (!user) {
-    console.warn('Did we fully wait for auth state to be determined?');
-    throw new Error('No authenticated user found');
+    console.warn('authorizedFetch: No authenticated user found. Did we fully wait for auth state to be determined?');
   }
 
-  // Get the ID token - let it throw if it fails
-  const idToken = await user.getIdToken(true);
-
   // Ensure headers object exists
   if (!requestOptions.headers) {
     requestOptions.headers = {};
   }
 
-  // Set the Authorization header with Bearer token
-  requestOptions.headers['Authorization'] = `Bearer ${idToken}`;
+  // Set the Authorization header with Bearer token if user is logged in
+  if (user) {
+    const idToken = await user.getIdToken(true);
+    requestOptions.headers['Authorization'] = `Bearer ${idToken}`;
+  }
 
   // Make the request using wonderful-fetch
   return fetch(url, requestOptions);