-
Notifications
You must be signed in to change notification settings - Fork 30.6k
Closed
Description
Is something wrong with CI or publishing infrastructure?
- Check the Infrastructure status updates thread for known issues.
- Leave a message on the DefinitelyTyped channel in the TypeScript Community Discord.
If you know how to fix the issue, make a pull request instead.
- I tried using the
@types/xxxxpackage and had problems. - I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript
- I understand that
@typespackage versions do not follow SemVer. - I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).
- Mention the authors (see
Definitions by:inindex.d.ts) so they can respond.- Authors: @bondz
@bondz - I'm not sure if this is in your control or not. I looked at your original PR but I can't see any reference to dependencies on @types/mongoose. It would be good to add this as an optional peerdep if possible.
For anyone who is having mongoose type conflicts relating to this:
Mongoose@5.11.0now includes its own types that are incompatible with@types/mongoose@5.10.5. This means you either need to pin your version to5.10.9in pkg json or remove@types/mongooseas a dependency.- Because
@types/mongoose-geojson-schemahas a dependency on@types/mongooseyou'll experience errors. The way around this is to remove@types/mongoose-geojson-schemaand copy the contents of@types/mongoose-geojson-schemaindex.d.ts to aglobal.d.tsinside yoursrc
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels