All Aurelia Typings?

Framework Knowledge
1

Does anyone know where I can find ALL typings for Aurelia, in order to run Typescript? It must be gathered somewhere?

thanks

1 Like
2

Aurelia is written in ts. There is no full typing for Aurelia, but there is d.ts file for every Aurelia npm packages. Just follow the field “typings” path in their package.json file.

1 Like
3

I was under the impression only Aurelia2 was written entirely in TS, and that Aurelia 1 was partially TS? Did Aurelia1 get converted to TS completely?

1 Like
4

Why then in most tsconfig examples they indicate that one should exclude all node_modules from the ts compiler? It is very confusing. This was a tsconfig.json example posted from Aurelia blog ( https://aurelia.io/blog/2015/05/06/getting-started-with-aurelia-and-typescript/) it required pasting in a typings folder.

 "version": "3.8.3",
"compilerOptions": {
    "target": "es5",
    "module": "es2015",
    "moduleResolution": "node",
    "lib": [ "es2017", "dom" ],
    // "importHelpers": true,
    "sourceMap": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "allowSyntheticDefaultImports": true,
},
"filesGlob": [
    "./**/*.ts",
    "!./node_modules/**/*.ts"
],
"files": [
    "./typings/aurelia-dialog/aurelia-dialog.d.ts",
    "./typings/aurelia-dialog/dialog-cancel-error.d.ts",
    "./typings/aurelia-dialog/dialog-close-error.d.ts",
    "./typings/aurelia-dialog/dialog-configuration.d.ts"
1 Like
5

I think so. If it’s not all, it’s at least most important ones. But I cannot recall any package not in ts.

1 Like
6

Even if it is, it doesn’t give you type intellisense out of the box anyway.

1 Like
7

Can you give an example of where the intellisense fails for you? Would be easier that way to check what went wrong

1 Like
8

Wasn’t referencing typings from node_modules.

Having this in tsconfig.json helped

   "typeRoots": ["node_modules/**/*"],
  "include": [
     "./typings/**/*"
  ]
1 Like