-
Notifications
You must be signed in to change notification settings - Fork 99
Install ec-typescript as a dependency for addons #623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
We've been EmberConf-ing and traveling back from that; one of us will get back to you in the next few (work) days! |
@ro0gr this seems like a great idea, do you mind rebasing this and we'll iterate forward with you on it? |
@chriskrycho sure, will do. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9c3c768
to
560b565
Compare
I've just updated docs and tests, rebased and squashed. According to Azure there is a test failure:
But that doesn't seem like related one. At least I can see the same failure on a sibling PRs |
Thanks again for doing this! On Wednesday (after we've finally fully cleared our backlog of built-up PRs), would you mind rebasing this? We'll coordinate with you to get it polished and integrated! Sorry about the delay. 😅 |
|
||
```sh | ||
ember install ember-cli-typescript@latest | ||
``` | ||
|
||
### In addons | ||
|
||
To work properly, Ember addons must declare this library as a `dependency`, not a `devDependency`. **This is a *change* from ember-cli-typescript v1.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as in the README.
Seems like ember-cli-typescript isn't supposed to work when installed as a dev dep to the host addon. I've just got a blank screen due to missing assets in my case.
In the build output I've seen a warning:
which was great cause it finally led me to a fix. But the question is whether we should convert it to error? Seems like nothing works anyways with
ec-ts
in the addon dev deps..Also I've found I just wasn't careful enough, cause there are special installation instructions for addon case:
However, I feel it still can be better if we take care of this installation difference in the blueprint. Which would to allow install this addon by simply running
ember install ember-cli-typescript
.At the moment I'd like to know if the feature makes sense here?