chore: replace uuid and deep-equal dependencies with Node.js built-ins

chore: bump dependencies

chore: bump dependencies

chore: update Cloud Functions runtime to Node.js 22 chore: ran npm run audit fix chore: add esModuleInterop and skipLibCheck to tsconfig.json

chore: bump dependencies

feat - move to Node.js 20 runtimes

fixed - updated vulnerable dependencies

feature - add custom EventArc events

build - updated depenencies

feature - bump to node 18

feature - bump to nodejs16

fixed - web client now uses the document sub collection for processing shards

fixed - ts errors and updated packages

feature - upgrade extensions to the latest firebase-admin sdk

fixed - generate correct package-lock.json files after lerna bootstrap (#779)

fixed - update validate workflow to use node14

feature - Add Node.js Admin SDK implementation (#687)

feature - add Taiwan and Singapore Cloud Function locations (#729)

feature - added Warsaw (europe-central2) location (#677)

feature - updated Cloud Functions runtime to Node.js 14 (#660)

feature - Added Android client instructions for firestore-counter extension.

feature - addded iOS sample for firestore-counter extension.

feature - convert Firestore Counter to use scheduled functions (#353)

feature - Add new Cloud Functions locations. For more information about locations and their pricing tiers, refer to the location selection guide.

feature - Update Cloud Functions runtime to Node.js 10.

build - Updates the firebase-admin and firebase-functions packages to the latest versions (issue #181).

feature - Limit shards to 100 documents, to optimize performance.

changed - Moves the logic for monitoring the extension's workload from the existing HTTP function to a new Pub/Sub controllerCore function. Now, if called, the HTTP function triggers the new controllerCore function instead. This change was made to accommodate a change in the way Google Cloud Functions handles HTTP functions.

We recommend that you edit your existing Cloud Scheduler job to instead send a message to the extension's Pub/Sub topic which triggers the new controllerCore function (detailed instructions provided in the POSTINSTALL file. Although it's not recommended, if you leave your Cloud Scheduler job calling the HTTP function, your extension will continue to run as expected.

Initial release of the Distributed Counter extension.