Wrong type definitions when using with Ember

[josemarluedke]

Using @glimmer/component version 0.14.0-alpha.3 with Ember (canary) brings the wrong type definitions for TypeScript users.

Current behavior

The types that get used are referent to the glimmer.js implementation of the component.

That implementation is not complaint with Glimmer Components RFC. It includes additional hooks and properties such as didInsertElement, bounds, element, didUpdate on the component class.

This gives wrong type errors when writing components in TS as well wrong auto complete suggestions.

Reproduction

1. Clone this app
2. Open a tool that has TS lang server such as VS code and play around

Expected

Types that reflect actual implementation of Glimmer Components RFC.

[chriskrycho]

I just checked and the correct info is on master (here); we just need another alpha (or beta?) release cut.

[josemarluedke]

I want to clarify that the this issue is referring to the type definitions of the component class.

See following images:

Per Glimmer RFC, we should not have didInsertElement or element. The VS Code auto complete suggests the wrong thing because it is pulling the wrong type for the component.

It uses this file instead of this file.

[rwjblue]

Chatted about this a bit in discord, for now the easiest fix is to override in tsconfig.json.

@chriskrycho / @josemarluedke - Could one of y'all paste the snippet?

[chriskrycho]

In your tsconfig.json's compilerOptions hash:

    "paths": {
      "@glimmer/component": [
        "node_modules/@glimmer/component/addon"
      ]
    },

[jamescdavis]

This should be fixed in @glimmer/component 2.0

See : #235

[locks]

PR mentioned above has been merged.