Ufdjrw

List *all* the tuples!

The logistics of corpse disposal

3 doors, three guards, one stone

Why are Kinder Surprise Eggs illegal in the USA?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

Why is "Consequences inflicted." not a sentence?

Are two submodules (where one is contained in the other) isomorphic if their quotientmodules are isomorphic?

Overriding an object in memory with placement new

Dating a Former Employee

English words in a non-english sci-fi novel

How would the world control an invulnerable immortal mass murderer?

Is it true that "carbohydrates are of no use for the basal metabolic need"?

Bete Noir -- no dairy

Identify plant with long narrow paired leaves and reddish stems

How to tell that you are a giant?

Why didn't this character "real die" when they blew their stack out in Altered Carbon?

How does the particle を relate to the verb 行く in the structure「A を + B に行く」?

What is a non-alternating simple group with big order, but relatively few conjugacy classes?

Can a USB port passively 'listen only'?

Seeking colloquialism for “just because”

porting install scripts : can rpm replace apt?

What's the purpose of writing one's academic biography in the third person?

Is the Standard Deduction better than Itemized when both are the same amount?

Output the ŋarâþ crîþ alphabet song without using (m)any letters

How can I work around a bug in a published type declaration file

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I'm using the excellent react-mapbox-gl library in a TypeScript project. It's written in TypeScript and published on NPM with typings.

Unfortunately there's a bug in the typings which prevents them from being used in projects on TypeScript 3.2 or later:

/node_modules/react-mapbox-gl/lib/map.d.ts
(82,13): Subsequent property declarations must have the same type.
 Property 'transformRequest' must be of type 'TransformRequestFunction',
 but here has type 'RequestTransformFunction'.

This is what the problematic declaration looks like:

declare global 
 namespace mapboxgl 
 interface MapboxOptions 
 failIfMajorPerformanceCaveat?: boolean;
 transformRequest?: RequestTransformFunction;
 
 

You can use module augmentation to fix incomplete type declarations, but is it possible to address this sort of issue from within my project's code? Disabling type checking for this module also doesn't seem to be an option since the (broken) type declarations are bundled with the implementation (rather than in @types).

typescript

share|improve this question

asked Mar 8 at 17:21

danvkdanvk

8,88324061

add a comment | 

0

I'm using the excellent react-mapbox-gl library in a TypeScript project. It's written in TypeScript and published on NPM with typings.

Unfortunately there's a bug in the typings which prevents them from being used in projects on TypeScript 3.2 or later:

/node_modules/react-mapbox-gl/lib/map.d.ts
(82,13): Subsequent property declarations must have the same type.
 Property 'transformRequest' must be of type 'TransformRequestFunction',
 but here has type 'RequestTransformFunction'.

This is what the problematic declaration looks like:

declare global 
 namespace mapboxgl 
 interface MapboxOptions 
 failIfMajorPerformanceCaveat?: boolean;
 transformRequest?: RequestTransformFunction;
 
 

You can use module augmentation to fix incomplete type declarations, but is it possible to address this sort of issue from within my project's code? Disabling type checking for this module also doesn't seem to be an option since the (broken) type declarations are bundled with the implementation (rather than in @types).

typescript

share|improve this question

asked Mar 8 at 17:21

danvkdanvk

8,88324061

add a comment | 

I'm using the excellent react-mapbox-gl library in a TypeScript project. It's written in TypeScript and published on NPM with typings.

Unfortunately there's a bug in the typings which prevents them from being used in projects on TypeScript 3.2 or later:

/node_modules/react-mapbox-gl/lib/map.d.ts
(82,13): Subsequent property declarations must have the same type.
 Property 'transformRequest' must be of type 'TransformRequestFunction',
 but here has type 'RequestTransformFunction'.

This is what the problematic declaration looks like:

declare global 
 namespace mapboxgl 
 interface MapboxOptions 
 failIfMajorPerformanceCaveat?: boolean;
 transformRequest?: RequestTransformFunction;
 
 

You can use module augmentation to fix incomplete type declarations, but is it possible to address this sort of issue from within my project's code? Disabling type checking for this module also doesn't seem to be an option since the (broken) type declarations are bundled with the implementation (rather than in @types).

typescript

share|improve this question

asked Mar 8 at 17:21

danvkdanvk

8,88324061

/node_modules/react-mapbox-gl/lib/map.d.ts
(82,13): Subsequent property declarations must have the same type.
 Property 'transformRequest' must be of type 'TransformRequestFunction',
 but here has type 'RequestTransformFunction'.

declare global 
 namespace mapboxgl 
 interface MapboxOptions 
 failIfMajorPerformanceCaveat?: boolean;
 transformRequest?: RequestTransformFunction;
 
 

share|improve this question

asked Mar 8 at 17:21

danvkdanvk

8,88324061

share|improve this question

asked Mar 8 at 17:21

danvkdanvk

8,88324061

asked Mar 8 at 17:21

danvkdanvk

8,88324061

asked Mar 8 at 17:21

danvkdanvk

8,88324061