# At a complete loss with Addons

**URL:** <https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478>\
**Category:** Ember CLI\
**Created:** [August 26, 2016, 1:39pm UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478 "2016-08-26T13:39:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tsteuwer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/tsteuwer/32/10887_2.png) [@tsteuwer](https://discuss.emberjs.com/u/tsteuwer)\
**Post date:** [August 26, 2016, 1:39pm UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478/1 "2016-08-26T13:39:11Z")

</div>

I want to preface this with I’ve read so many tutorials. I have several issues:

1. When I create an addon, I don’t understand how you view the test dummy app. I’ve visited localhost:4200 (which all I see is the basic hello world with the ember chipmunk. I’ve also gone to /tests/dummy and all I get are running tests in the browser. **I found out you have to remove the welcome addon. I wish this were a part of the guides documentation.**
2. I’ve made a /blueprints/my-addon/index.js and it is not getting called in a consuming application. Even after running ember g my-addon it always says `installing my-addon The `ember generate <entity-name>` command requires an entity name to be specified. For more details, use `ember help`.`

---

<div class="post-metadata">

**Author:** ![lightblade](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/lightblade/32/15632_2.png) [@lightblade](https://discuss.emberjs.com/u/lightblade)\
**Post date:** [August 28, 2016, 4:04am UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478/2 "2016-08-28T04:04:23Z")

</div>

1. You run `ember s` to view the dummy app just like your regular app. Yes, you do need to remove the welcome app, but that is part of the guide that shows up when you are at `localhost:4200`.
2. The default blueprint is only called as part of the addon install process. This specifically means that addon is installed via `ember install <addon-name>`. Any other methods won’t trigger this blueprint (`npm install`, `bower install`). [Read more about it here](https://ember-cli.com/extending/#default-blueprint)

---

<div class="post-metadata">

**Author:** ![sheriffderek](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/sheriffderek/32/10619_2.png) [@sheriffderek](https://discuss.emberjs.com/u/sheriffderek)\
**Post date:** [August 30, 2016, 9:52pm UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478/3 "2016-08-30T21:52:23Z")

</div>

When you create the application.hbs template, the welcome screen will desist on a normal app, but I think for the last addon I was working on, that was not the case for the dummy app.

Your problem is vague from my view. Maybe you can make a simplified version and post a git repo, or get more detailed with the steps you have taken. There are also a bunch of awesome Ember developers on [CodeMentor](https://www.codementor.io/) and you could probably save some time by throwing a little cash at it - and get some quality 1 on 1 help.

Good luck!

---

<div class="post-metadata">

**Author:** ![fraggle](https://avatars.discourse-cdn.com/v4/letter/f/34f0e0/32.png) [@fraggle](https://discuss.emberjs.com/u/fraggle)\
**Post date:** [July 5, 2018, 6:02pm UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478/4 "2018-07-05T18:02:30Z")

</div>

Ember is a joke. As usual, the documentation is wrong. Backwards compatibility is constantly being broken. Addons blueprints can no longer be run, and there is no way to get the functionality back.

---

<div class="post-metadata">

**Author:** ![acorncom](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/acorncom/32/12198_2.png) [@acorncom](https://discuss.emberjs.com/u/acorncom)\
**Post date:** [July 7, 2018, 2:27am UTC](https://discuss.emberjs.com/t/at-a-complete-loss-with-addons/11478/5 "2018-07-07T02:27:58Z")

</div>

Sorry to hear that things are frustrating. As far as I know addon blueprints are working fine, is there something specifically that you’re having trouble with? Would love to see it get addressed …
