Based on the information provided in the README:
The package creates a global object called JobCollection
that is accessible on both the client and server sides.
In simple terms, you don't have to import the package after installation. You can directly use JobCollection
in your application. This aligns with what the instructions mentioned:
Sometimes a package may not have exports but instead have side effects when added to your app. In such cases, importing the package is unnecessary after installation.
It's unclear whether there is a specific reason for using globals in this package or if it's just not adhering to proper module practices.
EDIT:
As noted in the comments, TypeScript definitions are missing from this library. You could create your own (and contribute them back as a pull request) or use the following code snippet in your application to prevent errors:
declare var JobCollection: any;
I typically store these small snippets of definition code in a file named definitions.d.ts
in all my TypeScript projects.