I'm unsure why my ember does not start. When I type ember server, I see
PS C:\Users\lzc\Ember-Prototype> ember s
version: 0.2.3
A new version of ember-cli is available (0.2.7). To install it, type ember update.
Livereload server on port 35729
Serving on http://localhost:4200/
PS C:\Users\lzc\Ember-Prototype>
I'm pretty sure its not the outdated CLI, because it was working very well for the pas week. When I type ember build, it instantly reads 'Building...` then finishes. Normally my builds are 60 to 80 seconds. I can't identify whether this is a compile issue or settings flaw. Shouldn't Ember-CLI give an error message if something went wrong like this?
Has anyone experienced this before?
Can't run `--verbose', no command in CLI. Issue was when liquid modal tried to register transitions, one of the path strings was incorrect. No error messages given.
Related
Livereload
I'm having problems getting Ember CLI (1.13.15) to detect changes. When I create a new application with
ember init
And run the development server with
ember serve
The project compiles and I see the page. When I change something, the server detects changes in the console, but nothing happens even if I refresh page. The changes become visible only after I rerun the ember serve
Slow build
Also on an empty app it takes 30 sec to build app on Samsung 850 Pro SSD & i7 2600k with admin rights and after ember-cli-windows run. (the build on half slower MacBook Air is almost instantaneous).
Versions
Windows 10 with all the updates
ember-cli: 1.13.15
node: 4.2.6
npm: 2.14.10
I just encountered this as well -- seemingly out of nowhere, at once, on several different projects. Making sure I had this in .ember-cli was a winning fix:
"liveReload": true,
"watcher": "polling"
[Update]
I already had liveReload: true, so adding the watcher setting seems to be what was needed. Furthermore the projects that I implemented this for were using ember-cli at 1.13.13, 2.2.0-beta.6 and 2.3.0-beta.1, with the following system config:
node: 4.2.4
npm: 2.14.10
os: darwin x64
There's currently a known issue in ember-cli where the open port for livereload isn't detected correctly (https://github.com/ember-cli/ember-cli/pull/5391). You should be able to get around this for now by running ember serve --host 0.0.0.0.
For now, the best solution seems to be sticking to the old versions. Also there seems to be an issue with latest sass plugin not recognizing changes so I recommend downgrading both to:
ember-cli: 1.13.8,
ember-cli-sass: 4.2.1
I'm new to ember and doing a introductory tutorial to build a simple app. When I create a new app and start server, I try visiting the localhost page (http://localhost:4200/) in my browser but the page is blank. The browser window title is of my app name but there is no "Welcome to Ember" text as their should be. Also the ember inspector says "Ember application not detected!" although the little ember icon appears in the address bar of Firefox indicating that there is an ember app.
I have tried to restart the tutorial 3 times now and come up with same results. I have followed all set-up steps provided here. The only thing I did different or in addition to the turorial is I had to run sudo chown -R $USER /usr/localbecause of permissions issues.
All I have done so far is install node, npm, bower, ember-cli 2.2.0-beta.2., and then run these few commands:
ember new ember2-blog
cd ember2-blog
ember server
The terminal gives me a "Build successful - 7016ms." message but I go to http://localhost:4200/ and see the blank page... The inspector says "no ember app detected". Seems like I'm missing something simple but can't figure it out. Is it something to do with permissions? Please and thank you for your help.
This is a bug due to a new version of jQuery. For now you can change the following line in your bower.json file. Then run bower install and it should work.
"jquery": "^1.11.3",
to
"jquery": "1.11.3",
A new version of ember.js is imminent which should fix this.
I have installed the plugin for 'ember-cli-blanket', using command:
ember install:addon ember-cli-blanket0
But when I run the tests using "http://localhost:4200/tests", nothing is loading I am getting just a blank page, no error in console also.
When I referred in some online tutorials, they asked to pass "data-cover" with the <script></script> tag. But no progress.
If i uninstall the plugin and run the tests it is working fine.
Can anyone tell what am I doing wrong or any more settings needs to be done?
I've been trying to use Ember CLI to set up a new ember install, but the process keeps dying when trying to install ember-cli-qunit. I'm relatively new to using npm, bower, and ember so maybe this could just be an issue with me being dumb. Here is the dump I get when running
ember new webapp
I've been working on this for a few hours and can't really figure out how to fix the issue.
Thanks in advance
You must have ran bower as root at some point, and that would've changed the permissions of bower's cache files in your home directory (as per the error in the EACCESS line). Simply changing the permissions back to your own user (as root of course) should fix the problem.
Because of similar sudo problems driving me crazy (and the system's nodejs package being dated) I switched my setup to nvm: node version manager which installs everything to my own home directory instead and I never need to use root again for node-related installations.
I'm currently digging into Ember.js, using Yeoman as an automation tool for project deployment. Since Grunt is already included in Yeoman, I'm using it to fire up a Grunt Server everytime I'm working on my project.
I just started my very first Ember.js project using Yeoman when I realized, that Chrome's Ember Inspector Extension isn't able to detect my application as an Ember.js app when I'm running my Grunt Server at localhost. I've already checked the "Allow access to file URLs" option within the Extension settings, still no detection.
When I work on the project without running the Grunt Server, Ember Inspector detects my application immediately.
Any solution how I can use the Inspector while running Grunt?
Change your grunt to run on port 80.
Honestly it might be a problem localhost not being allowed with the extension, but I have a hard time believing that. Can't connect to localhost from Chrome extension