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'
jspm install npm:aurelia-metadata
ran? Also, are you using jspm@0.16 or 0.17? This feature supports 0.17+
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'.
object
, so the definition of lodash you're trying to use won't work
npm install -D @types/graceful-fs
get the one from dt?
@types
on npm is only definitelytyped
<source>~<name>
or <name> --source <source>
)
@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)
@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)
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
_