fix build, grossly

Author: morganchen12

firestore-next/test.firestore.js

@@ -2,6 +2,7 @@
 // [SNIPPETS_SEPARATION enabled]
 
 const { expect } = require('chai');
+import { or } from "firebase/firestore";
 
 // [START city_custom_object]
 class City {

firestore-next/test.solution-geoqueries.js

@@ -29,6 +29,9 @@ async function addHash(done) {
   done();
 }
 
+// tsc complains `center` can have more or fewer than 2 elements, but
+// since this is a js file there's no way of more accurately specifying
+// `center`'s type.
 async function queryHashes(done) {
   // [START fs_geo_query_hashes]
   const { collection, query, orderBy, startAt, endAt, getDocs } = require('firebase/firestore');
@@ -40,6 +43,7 @@ async function queryHashes(done) {
   // Each item in 'bounds' represents a startAt/endAt pair. We have to issue
   // a separate query for each pair. There can be up to 9 pairs of bounds
   // depending on overlap, but in most cases there are 4.
+  // @ts-ignore
   const bounds = geofire.geohashQueryBounds(center, radiusInM);
   const promises = [];
   for (const b of bounds) {
@@ -63,6 +67,7 @@ async function queryHashes(done) {
 
       // We have to filter out a few false positives due to GeoHash
       // accuracy, but most will match
+      // @ts-ignore
       const distanceInKm = geofire.distanceBetween([lat, lng], center);
       const distanceInM = distanceInKm * 1000;
       if (distanceInM <= radiusInM) {