moment-range | Fancy date ranges for Moment.js | Date Time Utils library

I think it is case sensitive, ie. change the D to a d, change moduleIDs to moduleIds.

You need to compare each input slot with each of your standard time slots and compute their overlapping - thus you will automatically split the bigger input slots.

Ultimately, the problem you are experiencing is not the cause of an issue, but the symptom of improper Cloud Function lifecycle management. To understand what I mean, I'll give you a quick walkthrough of what is happening.

Contrary to popular belief, while admin.initializeApp(); is a synchronous line of code, it starts an asynchronous process that makes it ready for use later.

When you call initializeApp(), it parses the configuration object that you passed to it or the one that it assembles from the environment variables GOOGLE_APPLICATION_DEFAULT and FIREBASE_CONFIG which are prepopulated by Cloud Functions.

Once the configuration is parsed, it starts the process of negotiating its access tokens using the credentials from the configuration object in the background. If this process fails in any way, you will usually end up with a "app/invalid-credential" error that looks like:

Credential implementation provided to initializeApp() via the "credential" property failed to fetch a valid Google OAuth2 access token with the following error: ...

When a Cloud Function completes its body of work, it is marked inactive, any resources are severely throttled and any network requests may be disconnected or blocked. The local Cloud Functions emulators don't simulate this behaviour so you should make sure you are completing all the work your Cloud Function needs to do before saying your function has completed (by chaining Promises properly or only calling res.end()/res.send()/etc once everything has finished).

A tell-tale sign that this is occurring is if you see this log message before other messages:

Function execution took ... ms, finished with ...

Importantly, when in this "inactive" state, even the requests used to negotiate the Admin SDK's access token will be interrupted which will lead to a "app/invalid-credential" error.

You need to work through your notifyWorks function and look for any function calls that returns a Promise that you don't use await with or return to the caller.

To start out, here are a few things that I can see in the code you shared.

This Promise constructor call is confusing (as console.log() returns void (undefined)):

Weird, it seems OK,

remove the .iml and re-import the project. Let us know if this does the Job!

Your query seems to find records that either start or end in a given day. As week is a range of consecutive days, this really translates to a query for records that either start in that week, or end in that week.

So you could remove the for loop, and define startDay and endDay as the start/end of the week, as follows:

Try updating your

You might want to try sourcing from one of the CDN

I'm guessing there's something wrong with your package version? I can't replicate your issue, and I tried the CDN's js file.