jest-extended | Additional Jest matchers | Assertion library

I am using custom matchers from two external libraries jest-dom/extend-expect and jest-extended. Both libraries defines a matcher named toBeEmpty, but with different behaviour. One expects a string/array/object/iterable to be empty, the other expects a DOM element to be empty.

My feeling is that the order in jest configuration impacts which matcher is actually used in test:

I'm trying to make a game with EaselJS, and since it's [current year], I'm using TypeScript. There are "official" types that I'm using from here, but I can't get it working together with parceljs. If I import the types, parcel fails. If I import without types, parcel is happy (and my build works), but I've got no types in VS Code.

Here's my import, which works for the parcel build:

I have a function to handle connecting to Cloud Firestore through the Admin SDK. I know the function works fine, as the app connects and allows writing to the database.

Now I am trying to test this function with Jest. To avoid testing outside the scope of this function, I am mocking the firebase-admin Node module. However, my test is failing with the error "TypeError: admin.firestore is not a function".

My function and tests are both written in TypeScript, run via ts-jest, but I don't think this is a TypeScript error, as VS Code has no complaints. I believe this is an issue with Jest's automatic mocking.

admin.firebase() is a valid call. The TypeScript definition file defines it as function firestore(app?: admin.app.App): admin.firestore.Firestore;

I've read over the Jest docs, but I'm not understanding how to fix this.

This is my function:

When I run jest --coverage jest only collects coverage from JavaScript files, but not my vue files. The folder structure is correct. jest.config.js is in the root folder, just like /components and /lib. For me, there is no logical explanation why coverage is collected from JavaScript files but not from vue files.

Here is my jest.config.js