typings/typings

The type definition manager for TypeScript

Felix Becker

@felixfbecker

Also, really ironic that the publisher for DT has custom typings for node-git that are not published to DT

Glen

@glen-84

@unional I tried typings install jspm:aurelia-metadata, but it gives this:

typings ERR! message Unable to read typings for "aurelia-metadata". You should check the entry paths in "package.json" are up to date
typings ERR! caused by ENOENT: no such file or directory, open '..\public\npm:aurelia-metadata@1.0.3\index.d.ts'

Homa Wong

@unional

Do you have jspm install npm:aurelia-metadata ran? Also, are you using jspm@0.16 or 0.17? This feature supports 0.17+

Glen

@glen-84

@unional Hmm, actually it's only a peer dependency in jspm, I guess that is the issue. Thanks.

dewald

@dewwwald

Not having any luck on angular channel. Can anyone tell me why my webpack loader is loading

RROR in [at-loader] node_modules/@types/jasmine/index.d.ts:49:10 
    TS2300: Duplicate identifier 'Expected'.
ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:88:9 
    TS2375: Duplicate number index signature.

ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:129:10 
    TS2300: Duplicate identifier 'CustomEqualityTester'.

ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:136:10 
    TS2300: Duplicate identifier 'CustomMatcherFactory'.

ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:139:9 
    TS2374: Duplicate string index signature.

ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:258:15 
    TS2300: Duplicate identifier 'ExpectationFailed'.

ERROR in [at-loader] node_modules/@types/jasmine/index.d.ts:432:10 
    TS2300: Duplicate identifier 'SpecFunction'.

ERROR in [at-loader] node_modules/@types/lodash/index.d.ts:12898:29 
    TS2304: Cannot find name 'object'.

ERROR in [at-loader] node_modules/@types/lodash/index.d.ts:19638:15 
    TS2428: All declarations of 'WeakMap' must have identical type parameters.

ERROR in [at-loader] node_modules/@types/lodash/index.d.ts:19638:33 
    TS2304: Cannot find name 'object'.

lodash and jasmine types.

I am using typescript 2.1.6

Blake Embrey

@blakeembrey

i'd start with checking the duplicates - maybe you are using typings and @types together? look at where the errors are coming from, it should tell you which files are an issue

the other issue is that typescript 2.1 doesn't support object, so the definition of lodash you're trying to use won't work

Otso Rajala

@otjura

do I still need typings.json at all as I can just do npm install --save-dev @typings/foo now?

Homa Wong

@unional

npm I @types/foo Nope

Burt Harris

@BurtHarris

I type typings search graceful-fs, and get back

NAME        SOURCE HOMEPAGE                                  DESCRIPTION VERSIONS UPDATED
graceful-fs npm    https://www.npmjs.com/package/graceful-fs             1        2016-07-23T03:37:00.000Z
graceful-fs dt     https://github.com/cowboy/graceful-fs                 1        2016-05-10T01:06:27.000Z

OK, so how do I choose between them?

And why doesn't npm install -D @types/graceful-fs get the one from dt?

Blake Embrey

@blakeembrey

it does

all of @types on npm is only definitelytyped

if you look at the readme on typings, how to select it is there (it's the "source", you can either do <source>~<name> or <name> --source <source>)

Burt Harris

@BurtHarris

Thanks Blake. "How do I choose", was more a question of which source to use rather than syntax. Does the npm one indicate it's somehow tied to the actual package and/or author? Would that be preferable to definitions from definitelytyped?

Blake Embrey

@blakeembrey

i'd just use @types/<type> going forward with typescript. although you can continue using typings and it will stay working, i've stopped heavily contributing to typescript because i haven't been able to get movement on third-party definitions. the source for typings was directly related to where you got them from (e.g. from npm, part of the environment, a global, etc)

Blake Embrey

@blakeembrey

i just hit that use-case of wanting two different definitions for the same lib again (e.g. electron). related to TypeStrong/ts-node#353, the user thought they could require electron and get the types but actually in node, it's a string

Blake Embrey

@blakeembrey

@unional @felixfbecker one thing we can also do is publish all our types under @typed and just proxy the require of the definitions to the original module (e.g. module.exports = require('express')). this was a terrible proposal of what typescript could have supported already when we first chatted, but it could be an easy workaround today (no need for @types or installing from github)

Felix Becker

@felixfbecker

what do you mean with proxy?

Homa Wong

@unional

I am thinking about they can just use our type organization and add a bot user to monitor changes in the organization. That bot user can mandate the use of their tool chain (e.g. dtslint) and make sure all test passes. Have a cli to allow user to create new repos and publish.

Blake Embrey

@blakeembrey

that would be fine but i'm not sure someone will build that bot if it's not us - and i'm not doing much extra anymore

@felixfbecker by proxy, i just mean literally create a index.js file that proxying the require('@types/x') call to the real module (x) which is installed as a dependency. it does cause fragmentation, but maybe it's enough for typescript to see it's useful to support more people contributing and they'll enable something for everyone instead. it'd only be a stop-gap until then

Mario Matos

@marioscience

I am using the HTML5 <video> tag which uses the Media API. Is there a type definition for this? I tried searching in https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types but couldn't find anything. Any ideas? (I'm new here, if there's something wrong with the question give me a link where I can learn about the community. be nice please)

Homa Wong

@unional

I don’t think it is available. You can raise this question on DT.

Blake Embrey

@blakeembrey

i am going to go through and archive the @typings repos, and also post deprecation notices this week

work on @types can still continue and that'll be focused on usage with NPM directly (either from github or eventually from NPM if Microsoft supports redirects)

i will keep the registry and api unarchived for now, let me know if you'd like anything else archived /cc @unional for generator stuff

i also disabled greenkeeper on @typings

Homa Wong

@unional

I can transfer it to types or myself and get the v2 ready in the future. Maybe the same for taking-config-typings?

Tslint

Blake Embrey

@blakeembrey

sure, sounds good to me

what do you feel is the pattern for "native modules" - i prefixed the guidelines with an _

should we do that for other @types modules

also, feel free to leave them there but start new projects based on them

whichever you'd prefer - we can archive and deprecate or we can move

Homa Wong

@unional

__ sounds good

I'll move them tomorrow

Homa Wong

@unional

Moved. XD

Blake Embrey

@blakeembrey

cool. feel free to unprefix types as you use them or go to. i'll treat anything prefixed as deprecated going forward, we can probably move them into another org or start archiving them

mypmj

@mypmj

hello , i have an issue with typings.

where i can see typings.d.ts file in node typescript project ?

tsc version 2.4.1

mypmj

@mypmj

i can't see it in src /

rekhaaddula

@rekhaaddula

Hi all,as i am new to nodejs using typescript,anyone can advice if any package is deprecated how do i get equivalent package which i can use in project like Typings is deprecated

and also please advice where i find the Readme for this particular package

Homa Wong

@unional

You basically don’t need any package. If the package you use doesn’t come with typings, you can try finding it under the @type scope. Check out TypeScript github.

Where communities thrive

People

Repo info

Activity