search

glimmerjs / glimmer-blueprint

[MOVED] This package is now part of the Glimmer.js monorepo
https://github.com/glimmerjs/glimmer.js
25 stars 13 forks source link

ember new -- doesn't work out of the box #77

Closed xpat closed 6 years ago

xpat commented 6 years ago

This is similar to issue #74 (ember s doesn't work out of the box).

The Glimmer quickstart "my-app" instructions never work for me. After reading any number of issues (open and closed), and trying to run the command in the various ways, I still can't figure out what's going wrong. Here's a link to the error message I got when running the command as instructed ($ ember new my-app -b @glimmer/blueprint) error message no flag and a link to the error message I got when using the flag --yarn=false. error message with flag.

mikkopaderes commented 6 years ago

Same here. I think the issue is because it's trying to download https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node which is a broken link.

I'm on:

ember-cli: 2.18.0 node: 8.9.3 npm: 5.5.1 os: win32 x64

xpat commented 6 years ago

Same here. I think the issue is because it's trying to download https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node which is a broken link.

The two error logs that I initially posted don't contain a reference to sass...binding.node, @rmmmp. This one does (from a fresh attempt on another computer): error message 3.

Incidentally, I finally got the elusive glimmer/blueprint quickstart example to work on one of three computers. Here is a link to some related bash history.txt that preceeded the successful runs. Anybody know where to find the log files of a successful run?

mikkopaderes commented 6 years ago

I believe my error would only happen if you don't have yarn installed. When I had yarn, my error was the same with yours. Although I'm seeing in slack that there's some people having the same problem too. I do wonder if this is the right repo to post the issue or to somewhere else.

@xpat, I'm guessing your successful runs aren't on a windows OS?

xpat commented 6 years ago

@rmmmp all my computers are running linux ubuntu 16.04, all with Yarn installed. Sometimes I run the command with the option --yarn=false.

mikkopaderes commented 6 years ago

I tried downgrading to node 6.12.2 and it worked

headquarters commented 6 years ago

Ran into the same problem on macOS Sierra, node 8.2.1, npm 5.5.1, ember-cli 2.18.1. Here is the output log.

The following command consistently failed: ember new glimmer-components -b @glimmer/blueprint However, ember new glimmer-components -b @glimmer/blueprint --yarn=false worked. I'm running yarn v1.3.2.

t-sauer commented 6 years ago

You should upgrade to ember-cli 2.18.2. the problem should be fixed there.