ember install is effectively the combination of two commands:
npm install —save addon-name
ember generate addon-name
# or (when a yarn.lock is present)
yarn add addon-name
ember generate addon-name
Since you have already taken care of the first thing by linking (as long as you have also added the linked addon to package.json), you can run ember generate addon-name to test the addons blueprint.
ember generate command no longer works. It will either fail with the message “The ember generate <entity-name> command requires an entity name to be specified.” (even when overriding normalizeEntityName) or do nothing at all.
I’m trying to reproduce this and I cannot. I’m using the newly released ember-cli 3.2.0, and running an addon’s default blueprint (in my case I ran ember g liquid-fire).