Difficulties starting new glimmer app

[glimmerjs]

Difficulties starting new glimmer app

[pittst3r]

The option '--web-component' is not registered with the new command.

This is just a warning, and is related to the fact that one is currently unable to register an option with the new command. But it still works. Sorry for the confusion with that. 😃

$  ember new my-app -b @glimmer/blueprint
Error creating new application. Removing generated directory `./my-app`
Unknown blueprint: @glimmer/blueprint

This looks like you have the wrong version of ember-cli installed globally. What do you get when you do ember -v?

I was unable to get an error with using the beta version of ember-cli:

ember new my-app -b https://github.com/glimmerjs/glimmer-blueprint.git --web-component

Is that the command you used that produced an error?

[julienfitz]

Thankfully, we still have our terminal open, and we happened to have run ember -v right after getting that error. This was the output at that time:

$ ember -v
ember-cli: 2.13.0-beta.3
node: 6.0.0
os: darwin x64

And yeah, the last command you mentioned was the one that triggered the last error we mentioned.

Here is the exact order of what we ran in our terminal and what followed, after we got the last error we mentioned:

Immediately after seeing that error, we ran it again without the --web-component flag:

$ ember new my-app -b https://github.com/glimmerjs/glimmer-blueprint.git

This created a new glimmer project just fine. Then:

$ yarn global remove ember-cli
$ yarn global add ember-cli/ember-cli
$ which ember
/Users/engineering/.nvm/versions/node/v6.0.0/bin/ember
$ npm uninstall -g ember-cli
$ which ember
/Users/engineering/.nvm/versions/node/v6.0.0/bin/ember
$ sudo npm uninstall -g ember-cli
$ which ember
/Users/engineering/.nvm/versions/node/v6.0.0/bin/ember
$ sudo npm uninstall -g ember-cli
$ sudo npm uninstall -g ember
$ which ember
/Users/engineering/.nvm/versions/node/v6.0.0/bin/ember
$ ls -alt /Users/engineering/.nvm/versions/node/v6.0.0/bin/ember
lrwxrwxr-x  1 engineering  staff  58 Apr  5 16:24 /Users/engineering/.nvm/versions/node/v6.0.0/bin/ember -> ../../../../../.yarn-config/global/node_modules/.bin/ember
$ ember -v
ember-cli: 2.13.0-beta.3
node: 6.0.0
os: darwin x64
$ yarn global remove ember-cli
$ ember -v
zsh: command not found: ember
$ which ember
ember not found
$ yarn global add ember-cli/ember-cli
$ ember -v
ember-cli: 2.13.0-beta.3
node: 6.0.0
os: darwin x64

At that point, we ran ember new my-app -b @glimmer/blueprint without issue and were able to create a new project.

That's almost definitely more information than you need to know, but hopefully some of it is helpful! 😛

[tomdale]

@robbiepitts

This is just a warning, and is related to the fact that one is currently unable to register an option with the new command. But it still works. Sorry for the confusion with that. 😃

Err, this seems bad. 😬 What's the plan to fix this?

[pittst3r]

@tomdale Yes, it is bad. Here's the issue for it. I could use some help/advice. I have not yet been able to figure out a solution to this. The problem is that initializeCustomElements gets the Application type from node_modules/@glimmer/web-component/node_modules/@glimmer/application but when you use initializeCustomElements and pass in an instance of Application the type comes from node_modules/@glimmer/application.

[pittst3r]

Oh, I was obviously very confused. Talking about a different error. Anyhow, the error I was talking about has been fixed in @glimmer/[email protected].

The plan for the ember-cli error is TBD. First step is creating an issue for it in ember-cli. According to @rwjblue we are able to register options with the generate command, so I'm hoping the fix will just involve borrowing some code. But I've never gotten into ember-cli internals so I don't really know.

[atrama]

@vaidehijoshi are you still running into this? I also got the error below because my blueprint was installed in a different location than the rest of my global node modules. Moving the blueprint fixed all my issues.

Error creating new application. Removing generated directory `./my-app`
Unknown blueprint: @glimmer/blueprint

[vaidehijoshi]

@atrama We were eventually able to create a new Glimmer app, so that Unknown blueprint: @glimmer/blueprint error ultimately didn't end up being a blocker for us! But, we figured that it was possible someone else would eventually run into this same problem, so we just wanted to flag it for the team so that they'd be aware of it.

[crodriguez1a]

@vaidehijoshi @atrama I also ran into this issue. The remote blueprint workaround worked for me as well. It seems like (for at least this iteration) migrating to a global yarn install of ember-cli may be a pre-requisite for using @glimmer/blueprint.

[locks]

I believe this has been addressed upstream. Thank you!