Issue 1:
I want to see .d.ts for @types/X package without cloning repo.

But when I open types folder on github I see following error, and X folder is not listed.

Sorry, we had to truncate this directory to 1,000 files. 3,413 entries were omitted from the list.

I want to see what issues already filed for @types/X and file new one.

But when I open issues tab I see >2k entries for all the packages... I wonder how contributors even find issues filed for their definitions (or they don't?).

Why typings do not live in separate repos? Isn't this monorepo a total mess?

Issue 2:
I tried using the @types/swaggerize-express package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @....

Currently both swaggerize-express and swagger-schema-official have complete type definitions for the openAPI specification. However, there are a few slight inconsistencies between the two which make it hard to use them in tandem. For example:

having installed the following:

@types/swaggerize-express@4.0.28

@types/swagger-schema-official@2.0.2

The following issues a compiler error (under typescript@2.2.2):

import * as swaggerize from 'swaggerize-express';
import { Spec } from 'swagger-schema-official';

declare var spec_swagger_schema_official: Spec;
declare var spec_swaggerize_express: swaggerize.Swagger.ApiDefinition;

/**
* type error here, when the object should be of the same type,
* as both should be valid openAPI schema
*/
spec_swagger_schema_official = spec_swaggerize_express;

Specifically,

[ts]
Type 'ApiDefinition' is not assignable to type 'Spec'.
Types of property 'definitions' are incompatible.
Type 'DefinitionsObject | undefined' is not assignable to type '{ [definitionsName: string]: Schema; } | undefined'.
Type 'DefinitionsObject' is not assignable to type '{ [definitionsName: string]: Schema; } | undefined'.
Type 'DefinitionsObject' is not assignable to type '{ [definitionsName: string]: Schema; }'.
Index signatures are incompatible.
Type 'SchemaObject' is not assignable to type 'Schema'.
Types of property 'allOf' are incompatible.
Type 'IJsonSchema[] | undefined' is not assignable to type 'Schema[] | undefined'.
Type 'IJsonSchema[]' is not assignable to type 'Schema[] | undefined'.
Type 'IJsonSchema[]' is not assignable to type 'Schema[]'.
Type 'IJsonSchema' is not assignable to type 'Schema'.
Types of property 'allOf' are incompatible.
Type 'IJsonSchema[] | undefined' is not assignable to type 'Schema[] | undefined'.
Type 'IJsonSchema[]' is not assignable to type 'Schema[] | undefined'.
Type 'IJsonSchema[]' is not assignable to type 'Schema[]'.
Type 'IJsonSchema' is not assignable to type 'Schema'.

My proposal would be to use @types/swagger-schema-official within @types/swaggerize-express so there is only one location to maintain, and we don't run into minor inconsistencies.

Authors of both definitions (@mohsen1 for @types/swagger-schema-official and @MugeSo for @types/swaggerize-express) have any thoughts?