White screen after splashscreen, Ionic2, android device - ionic2

I am currently developing Ionic2 app. I face a problem that after Splash screen, there is a white screen for 6-7 seconds, before app home screen.
I tried some googling but nothing works. My last attempt to solve is
hideSplashScreen() {
if(Splashscreen){
setTimeout(() => {
Splashscreen.hide();
},100)
}
};//
<preference name="SplashMaintainAspectRatio" value="true"/>
<preference name="FadeSplashScreenDuration" value="300"/>
Please help me in this issue;
EDIT:: My ionic info is
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.4
Ionic CLI Version: 2.1.17
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.47
ios-deploy version: 1.8.6
OS: OS X El Capitan
Node Version: v6.3.1
Xcode version: Xcode 7.2 Build version 7C68

By default, the splash screen is hidden after 3 seconds (see https://github.com/apache/cordova-plugin-splashscreen#configxml). But it could be that at this moment your app is not ready.
Therefore I add always the following preference to my config.xml:
<preference name="AutoHideSplashScreen" value="false"/>
Instead, I hide it manually, as soon as the app is ready:
this.platform.ready().then(() => {
Splashscreen.hide();
});
This is working on iOS as well as on Android.

Updating Ionic project and change some preferences did the trick for me.
Here the changelog and infos.
1 - Update to the latest version of the Ionic CLI, Cordova and Typescript:
npm uninstall -g ionic cordova typescript
npm install -g ionic cordova typescript
2 - Update your package.json to match the following dependencies, remove existing node_modules directory, and then run npm install:
"scripts": {
"build": "ionic-app-scripts build",
"clean": "ionic-app-scripts clean",
"ionic:build": "ionic-app-scripts build",
"ionic:serve": "ionic-app-scripts serve"
},
"dependencies": {
"#angular/common": "4.0.2",
"#angular/compiler": "4.0.2",
"#angular/compiler-cli": "4.0.2",
"#angular/core": "4.0.2",
"#angular/forms": "4.0.2",
"#angular/http": "4.0.2",
"#angular/platform-browser": "4.0.2",
"#angular/platform-browser-dynamic": "4.0.2",
"#ionic-native/core": "3.6.1",
"#ionic-native/in-app-browser": "3.6.1",
"#ionic-native/splash-screen": "3.6.1",
"#ionic-native/status-bar": "3.6.1",
"#ionic/storage": "2.0.1",
"ionic-angular": "3.1.1",
"ionicons": "3.0.0",
"rxjs": "5.1.1",
"sw-toolbox": "3.4.0",
"zone.js": "0.8.9"
},
"devDependencies": {
"#ionic/app-scripts": "1.3.6",
"typescript": "2.3.2"
}
3 - Update your config.xlm with these preferences (live review is ok):
<preference name="loadUrlTimeoutValue" value="700000"/>
<preference name="webviewbounce" value="false"/>
<preference name="UIWebViewBounce" value="false"/>
<preference name="DisallowOverscroll" value="true"/>
<preference name="android-minSdkVersion" value="16"/>
<preference name="BackupWebStorage" value="none"/>
<preference name="StatusBarStyle" value="default"/>
<preference name="SplashScreen" value="screen"/>
<preference name="orientation" value="default"/>
<preference name="SplashMaintainAspectRatio" value="true"/>
<preference name="FadeSplashScreenDuration" value="300"/>
<preference name="ShowSplashScreenSpinner" value="false"/>
<preference name="AutoHideSplashScreen" value="false"/>
<preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine"/>
<preference name="SplashScreenDelay" value="3000"/>
4 - Then I have copy/pasted some code that had been modified recently from here into my project (Ionic 2 demo and up to date app - Check the Github).
Now the application starts successfully without long splashscreen.
ps:
livereview: ionic run android -l
production: ionic run android --prod --release
Remember that you have to hide manually the splashscreen (like #Markus Wagner said) in your app.component.ts: this.platform.ready().then(() => { Splashscreen.hide(); });
EDIT: Update to Ionic v3.1.1 (2017-04-28)

Add the --prod flag during any of the following CLI commands:
// If iOS
ionic emulate ios --prod
ionic build ios --prod
ionic run ios --prod
// If Android
ionic emulate android --prod
ionic build android --prod
ionic run android --prod
More info of build (prepare + compile) an Ionic project for a given platform
https://ionicframework.com/docs/cli/cordova/build/

I’ve solved that issue by setting the correct parameters on config.xml
<preference name="AutoHideSplashScreen" value="false" />
<preference name="SplashScreenDelay" value="10000" />
<preference name="FadeSplashScreenDuration" value="1000" />
<preference name="SplashScreen" value="screen" />
<preference name="ShowSplashScreen" value="true" />
<preference name="ShowSplashScreenSpinner" value="false" />
<preference name="SplashShowOnlyFirstTime" value="false" />
<preference name="FadeSplashScreen" value="true" />
Then, on my platform.ready() instruction all I do is Splashscreen.hide();

Related

How to make Nav.Link href work with gh-pages

I am trying to learn react and after learning the basics, I followed some video online on how to create a webapp. Now everything is looking well on my local. But I want to publish it on github pages and so I installed gh-pages and followed the steps in : https://github.com/gitname/react-gh-pages
So my page is up in https://alvincabayan.github.io/amc-webapp/, only problem is the links are not working.
package.json :
{
"name": "amc-webapp",
"version": "0.1.0",
"private": true,
"dependencies": {
"bootstrap": "^4.3.1",
"react": "^16.8.6",
"react-bootstrap": "^1.0.0-beta.6",
"react-dom": "^16.8.6",
"react-particles-js": "^2.6.0",
"react-router-dom": "^5.0.0",
"react-scripts": "3.0.0",
"styled-components": "^4.2.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject",
"predeploy": "npm run build",
"deploy": "gh-pages -d build"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
},
"devDependencies": {
"gh-pages": "^2.0.1"
},
"homepage": "http://alvincabayan.github.io/amc-webapp"
}
NavigationBar.js:
import React from 'react';
import { Nav, Navbar } from 'react-bootstrap';
import styled from 'styled-components';
const Styles = styled.div`
.navbar {
background-color: #222;
}
a, .navbar-brand, .navbar-nav .nav-link {
color: #bbb;
&:hover {
color: white;
}
}
`;
export const NavigationBar = () => (
<Styles>
<Navbar expand="lg">
<Navbar.Brand href="/">AMC</Navbar.Brand>
<Navbar.Toggle aria-controls="basic-navbar-nav" />
<Navbar.Collapse id="basic-navbar-nav">
<Nav className="ml-auto">
<Nav.Item>
<Nav.Link href="/">Home</Nav.Link>
</Nav.Item>
<Nav.Item>
<Nav.Link href="/about">About</Nav.Link>
</Nav.Item>
<Nav.Item>
<Nav.Link href="/contact">Contact</Nav.Link>
</Nav.Item>
</Nav>
</Navbar.Collapse>
</Navbar>
</Styles >
)
App.js
import React from 'react';
import {BrowserRouter as Router, Route, Switch} from 'react-router-dom';
import {Home} from './components/Home';
import {About} from './components/About';
import {Contact} from './components/Contact';
import {NoMatch} from './components/NoMatch';
import {Layout} from './components/Layout';
import {NavigationBar} from './components/NavigationBar';
import {HomeJumbotron} from './components/HomeJumbotron';
function App() {
return (
<React.Fragment>
<Router>
<NavigationBar/>
<HomeJumbotron/>
<Layout>
<Switch>
<Route exact path="/" component={Home} />
<Route path="/about" component={About} />
<Route path="/contact" component={Contact} />
<Route component={NoMatch} />
</Switch>
</Layout>
</Router>
</React.Fragment>
);
}
export default App;
Shouldn't the codes:
<Nav.Link href="/">Home</Nav.Link>
<Nav.Link href="/about">About</Nav.Link>
<Nav.Link href="/contact">Contact</Nav.Link>
point to:
https://alvincabayan.github.io/amc-webapp/
https://alvincabayan.github.io/amc-webapp/about
https://alvincabayan.github.io/amc-webapp/contact
I can see that the corresdponding js are loaded when I inspected the page but trying to show them by dragging them into the browser results in 404.
Please help.
Thanks.
In your routes's path you have to put the name of the repo.
As you can see, right now when you click on a Link the name of the repo disapear.
So you can do for home page :
<Route exact path="amc-webapp/" component={Home} />
I had the same issue, posted on SO without answer. It might not be the best things to do but it works.
React router allows you to set a basename used for all routes. Just use this https://github.com/ReactTraining/react-router/blob/master/packages/react-router-dom/docs/api/BrowserRouter.md#basename-string

Illegal Operation on a Directory with Unknown Broccoli Plugin

Output from ember version --verbose && npm --version:
ember-cli: 2.12.1
http_parser: 2.7.0
node: 6.10.2
v8: 5.1.281.98
uv: 1.9.1
zlib: 1.2.11
ares: 1.10.1-DEV
icu: 58.2
modules: 48
openssl: 1.0.2k
os: darwin x64
3.10.10
When I try ember s I have the following error,
Livereload server on http://localhost:49153
Serving on http://localhost:4200/
The Broccoli Plugin: [object Object] failed with:
Error: EISDIR: illegal operation on a directory, read
at Error (native)
at Object.fs.readSync (fs.js:732:19)
at tryReadSync (fs.js:487:20)
at Object.fs.readFileSync (fs.js:535:19)
at /Users/li-xinyang/Desktop/XX_MemoCycle_Firebase/node_modules/broccoli-flatiron/index.js:33:16
at Array.forEach (native)
at readDirectory (/Users/li-xinyang/Desktop/XX_MemoCycle_Firebase/node_modules/broccoli-flatiron/index.js:28:31)
at /Users/li-xinyang/Desktop/XX_MemoCycle_Firebase/node_modules/broccoli-flatiron/index.js:21:15
at tryCatch (/Users/li-xinyang/Desktop/XX_MemoCycle_Firebase/node_modules/rsvp/dist/rsvp.js:539:12)
at invokeCallback (/Users/li-xinyang/Desktop/XX_MemoCycle_Firebase/node_modules/rsvp/dist/rsvp.js:554:13)
The broccoli plugin was instantiated at:
undefined
Below is a list of devDependencies,
package.json File
{
"name": "memo-cycle",
"version": "0.0.0",
"description": "A study tool for serious learner",
"license": "MIT",
"author": "",
"directories": {
"doc": "doc",
"test": "tests"
},
"repository": "",
"scripts": {
"build": "ember build",
"start": "ember server",
"test": "ember test"
},
"devDependencies": {
"broccoli-asset-rev": "^2.4.5",
"ember-ajax": "^2.4.1",
"ember-cli": "2.12.1",
"ember-cli-app-version": "^2.0.0",
"ember-cli-babel": "^5.1.7",
"ember-cli-dependency-checker": "^1.3.0",
"ember-cli-eslint": "^3.0.0",
"ember-cli-gravatar": "^3.8.1",
"ember-cli-htmlbars": "^1.1.1",
"ember-cli-htmlbars-inline-precompile": "^0.3.6",
"ember-cli-inject-live-reload": "^1.4.1",
"ember-cli-qunit": "^3.1.0",
"ember-cli-sass": "^6.1.2",
"ember-cli-shims": "^1.0.2",
"ember-cli-sri": "^2.1.0",
"ember-cli-uglify": "^1.2.0",
"ember-export-application-global": "^1.0.5",
"ember-in-viewport": "^2.1.1",
"ember-inline-svg": "^0.1.10",
"ember-load-initializers": "^0.6.0",
"ember-paper": "^1.0.0-alpha.19",
"ember-power-select": "^1.6.1",
"ember-power-select-with-create": "^0.3.1",
"ember-resolver": "^2.0.3",
"ember-route-action-helper": "^2.0.2",
"ember-simple-auth": "^1.2.2",
"ember-source": "~2.12.0",
"loader.js": "^4.2.3"
},
"engines": {
"node": ">= 4"
},
"private": true
}
It was working fine before my last to commit. What I have done in the last two commits are I remove all .DS_Store files in the last commit and added Firebase deploy config files and install cloud function dependencies via Yarn in the last second commit.
What I have tried to resolve the issues, but the issue persists.
1) Delete all node modules via rm -rf node_modules and re-install them npm install (dependencies were installed via Yarn)
2) Remove the project and clone from the origin
3) Revert back to early commit (issue persists even I revert back to the initial commit and re-install all the dependencies of course)
4) Restart Mac 😅
5) Update .ember-cli file and re-run ember init setup process
The issues is caused by
That plugin looks like it was built for an older version of broccoli, but the basic problem seems that its write function doesn't handle symlinks to directories.
See this GitHub issue for more details
https://github.com/ember-cli/ember-cli/issues/6981

Ionic serve gives typescript errors when updating to ionic-native v3

I get Typescript errors for every item from the native imports, when running ionic serve. This is after I updated to ionic-native v3. All the items from the new #ionic-native are not recognised by Typescript. I updated typescript to different v2 versions but can't get it to work.
I dit not changed any of my other code. It is not only related to the SplashScreen. All my references to the objects I used to import through 'ionic-native' (old style) and now import through #ionic-native/{plugin-name} give these Typescript Errors.
Can anybody please help? Can't serve or build my app at this moment
For example:
property hide does not exist on type typeof SplashScreen
I changed my imports to
import { LocalNotifications } from '#ionic-native/local-notifications';
import { SplashScreen } from '#ionic-native/splash-screen';
import { StatusBar } from '#ionic-native/status-bar';
My ionic info:
ordova CLI: 6.5.0
Ionic Framework Version: 2.2.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.0.0
Xcode version: Not installed
My ionic plugin ls
cordova-plugin-app-event 1.2.0 "Application Events"
cordova-plugin-app-version 0.1.9 "AppVersion"
cordova-plugin-camera 2.4.0 "Camera"
cordova-plugin-compat 1.1.0 "Compat"
cordova-plugin-console 1.0.6 "Console"
cordova-plugin-device 1.1.5 "Device"
cordova-plugin-fcm 2.1.1 "FCMPlugin"
cordova-plugin-nativestorage 2.2.1 "NativeStorage"
cordova-plugin-splashscreen 4.0.2 "Splashscreen"
cordova-plugin-statusbar 2.2.2 "StatusBar"
cordova-plugin-whitelist 1.3.2 "Whitelist"
cordova-plugin-x-socialsharing 5.1.6 "SocialSharing"
de.appplant.cordova.plugin.local-notification 0.8.4 "LocalNotification"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-barcodescanner 6.0.5 "BarcodeScanner"
My package.json
"dependencies": {
"#angular/common": "2.4.8",
"#angular/compiler": "2.4.8",
"#angular/compiler-cli": "2.4.8",
"#angular/core": "2.4.8",
"#angular/forms": "2.4.8",
"#angular/http": "2.4.8",
"#angular/platform-browser": "2.4.8",
"#angular/platform-browser-dynamic": "2.4.8",
"#angular/platform-server": "2.4.8",
"#ionic/storage": "2.0.0",
"#ionic-native/core": "^3.1.0",
"ionicons": "3.0.0",
"ionic-angular": "2.2.0",
"rxjs": "5.0.1",
"zone.js": "0.7.2",
"sw-toolbox": "3.5.1",
"babel-core": "^6.24.0",
"d": "^1.0.0",
"ng2-translate": "^4.0.0",
"#ionic-native/barcode-scanner": "^3.1.0",
"#ionic-native/local-notifications": "^3.1.0",
"#ionic-native/native-storage": "^3.1.0",
"#ionic-native/social-sharing": "^3.1.0",
"#ionic-native/splash-screen": "^3.1.0",
"#ionic-native/status-bar": "^3.1.0"
},
"devDependencies": {
"#ionic/app-scripts": "^1.1.4",
"#ionic/cli-build-ionic-angular": "0.0.3",
"#ionic/cli-plugin-cordova": "0.0.9",
"typescript": "2.0.9"
}
tsc -v
Version 2.2.1
According to the updated docs here, you need to inject Splashscreen in the constructor.
constructor(private splashScreen: SplashScreen) { }
this.splashscreen.hide();
In previous versions you would use the Splashscreen that was imported directly to call the methods.

Angular 2 karma setup issue -- Karma starts but doesn't run tests

In brief,
I'm creating a project starting with the Plunker code for the Angular
2 "Routing" example (access through the Angular 2 Advanced Tutorial
for Routing link). That source doesn't have the Karma or Jasmine
configuration baked in.
I've been trying unsatisfactorily to add this to the existing
project. My current setup runs karma but doesn't see any tests, either .js or .ts.
14 01 2017 19:16:44.080:WARN [karma]: No captured browser, open http://localhost:9876/
14 01 2017 19:16:44.112:INFO [karma]: Karma v1.4.0 server started at http://0.0.0.0:9876/
14 01 2017 19:16:44.112:INFO [launcher]: Launching browser Chrome with unlimited concurrency
14 01 2017 19:16:44.268:INFO [launcher]: Starting browser Chrome
14 01 2017 19:16:46.895:INFO [Chrome 55.0.2883 (Windows 10 0.0.0)]: Connected on socket [SNIP]
First I started with the the Angular 2 Advanced Tutorial for Testing link. That says I should create /app/1st.spec.ts:
describe('lst tests', () => {
it('true is true', () => expect(false).toBe(true));
});
I then ran npm test, but found I had no Karma capability. Since then I've installed a variety of packages, based on advice from a programmer's blog. My installations have become:
npm install karma –save-dev
npm install karma-jasmine jasmine-core –save-dev
npm install karma-chrome-launcher –save-dev
npm install karma-cli
npm install angular-mocks
npm install requirejs karma-requirejs
I ran "karma init" and answered questions best I could. My current karma.conf.js is (condensed):
module.exports = function(config) {
config.set({
basePath: '',
frameworks: ['jasmine', 'requirejs'],
files: [
{pattern: 'app/*.js', included: false},
{pattern: 'app/*.spec.js', included: false},
{pattern: 'app/**/*.js', included: false}
],
exclude: [ ],
preprocessors: { },
reporters: ['progress'],
port: 9876,
colors: true,
logLevel: config.LOG_INFO,
autoWatch: true,
browsers: ['Chrome'],
singleRun: false,
concurrency: Infinity
})
}
My package.json is:
{
"name": "MyProgram",
"version": "0.1.0",
"license": "MIT",
"description": "MyProgram description",
"scripts": {
"start": "gulp copy-jit && concurrently \"npm run tsc:w\" \"npm run lite\" ",
"lite": "lite-server",
"tsc": "tsc",
"tsc:w": "tsc -w",
"aot": "ngc -p tsconfig-aot.json",
"rollup": "rollup -c rollup-config.js",
"start-aot": "npm run aot && npm run rollup && gulp copy-aot && npm run lite",
"test": "karma start karma.conf.js"
},
"dependencies": {
"#angular/common": "~2.2.4",
"#angular/compiler": "~2.2.4",
"#angular/compiler-cli": "~2.2.4",
"#angular/core": "~2.2.4",
"#angular/forms": "~2.2.4",
"#angular/http": "~2.2.4",
"#angular/platform-browser": "~2.2.4",
"#angular/platform-browser-dynamic": "~2.2.4",
"#angular/platform-server": "^2.2.4",
"#angular/router": "~3.2.4",
"#angular/upgrade": "~2.2.4",
"angular-in-memory-web-api": "~0.1.5",
"core-js": "^2.4.1",
"reflect-metadata": "^0.1.8",
"rxjs": "5.0.0-beta.12",
"systemjs": "0.19.39",
"zone.js": "^0.6.25"
},
"devDependencies": {
"#types/core-js": "^0.9.34",
"#types/jasmine": "^2.5.35",
"#types/node": "^6.0.45",
"#types/selenium-webdriver": "^2.53.32",
"concurrently": "^3.0.0",
"del": "^2.2.2",
"gulp": "^3.9.1",
"gulp-gzip": "^1.4.0",
"gulp-load-plugins": "^1.3.0",
"gulp-rename": "^1.2.2",
"gulp-task-listing": "^1.0.1",
"gulp-util": "^3.0.7",
"jasmine-core": "^2.5.2",
"karma": "^1.4.0",
"karma-chrome-launcher": "^2.0.0",
"karma-jasmine": "^1.1.0",
"karma-requirejs": "^1.1.0",
"lite-server": "^2.2.2",
"rollup": "^0.36.1",
"rollup-plugin-commonjs": "^5.0.4",
"rollup-plugin-node-resolve": "^2.0.0",
"rollup-plugin-uglify": "^1.0.1",
"typescript": "^2.0.3"
}
}
The things I hope to resolve through your responses are:
A proper Angular 2 project configuration for Karma and Jasmine
testing.
The ability to create Typescript source code tests and have them detected and run in Karma.
Thanks,
Jerome.
I too was trying to go thru the process. I know that if you do ng new using the Angular CLI it will create a project for you with all the Karma stuff setup correctly.
ng test is similar to npm test but seems to spin up far faster too.
The package.json "scripts" section controls the "test" command line option.
I attempted to copy it into the Tour Of Heroes part 6 and managed to successfully do the 1st.spec.ts and get Karma to launch and flip true = true to true = false.
But at the point it said you could load up 1st.spec.ts in Chrome things wouldn't work for me either (Point 5 here).
I documented the way to copy files across here.
You also have the added nuisance that Karma used a version of Node that is behind the times using the LTS release cycle. So it's wise to setup nvm. See here

Could not find module `simple-auth-devise/configuration`

I've just been trying to install ember-cli-simple-authand ember-cli-simple-auth-devise.
I went through the exact same process last week and it worked fine. However, since then, Ember CLI has been updated and the install:addon command has been deprecated.
So instead of:
ember install:addon ember-cli-simple-auth
ember install:addon ember-cli-simple-auth-devise
I am using:
ember install ember-cli-simple-auth
ember install ember-cli-simple-auth-devise
However, at the end of each of these commands I get:
The ember generate command requires an entity name to be specified.
For more details, use ember help.
I tried running these commands manually, based upon the "old instructions" found here
ember generate ember-cli-simple-auth
ember generate ember-cli-simple-auth-devise
but then when I start the server I get the following error:
loader.js:110 Uncaught Error: Could not find module simple-auth-devise/configuration imported from bazmics/initializers/simple-auth-devise
and the app refuses to load.
The only way I'm able to get the app working again is to remove:
"ember-cli-simple-auth": "^0.8.0-beta.1",
"ember-cli-simple-auth-devise": "^0.8.0-beta.1",
from my packages.json, run npm install and then restart my server.
Just for good measure, I tried using npm install... rather than ember install... and then running the installers. No errors, but the same end result.
My versions:
DEBUG: -------------------------------
ember.debug.js:5197DEBUG: Ember : 1.11.1
ember.debug.js:5197DEBUG: jQuery : 1.11.2
ember.debug.js:5197DEBUG: -------------------------------
VM11004:66 Ember Inspector Active
Update: 8/4/2015
I've just tried running the following:
npm install --save-dev ember-cli-simple-auth
npm install --save-dev ember-cli-simple-auth-devise
generate ember-cli-simple-auth
generate ember-cli-simple-auth-devise
I don't get any errors, but the same thing is happening when I run ember server (nothing past the page body renders).
After the above commands the contents of my package.json is:
{
"name": "enerlytics",
"version": "0.0.0",
"description": "Small description for enerlytics goes here",
"private": true,
"directories": {
"doc": "doc",
"test": "tests"
},
"scripts": {
"start": "ember server",
"build": "ember build",
"test": "ember test"
},
"repository": "",
"engines": {
"node": ">= 0.10.0"
},
"author": "",
"license": "MIT",
"devDependencies": {
"broccoli-asset-rev": "^2.0.2",
"broccoli-sass": "^0.6.4",
"ember-cli": "0.2.3",
"ember-cli-app-version": "0.3.3",
"ember-cli-babel": "^5.0.0",
"ember-cli-bootstrap-sass": "^0.2.11",
"ember-cli-content-security-policy": "0.4.0",
"ember-cli-dependency-checker": "0.0.8",
"ember-cli-htmlbars": "0.7.4",
"ember-cli-ic-ajax": "0.1.1",
"ember-cli-inject-live-reload": "^1.3.0",
"ember-cli-qunit": "0.3.10",
"ember-cli-simple-auth": "^0.8.0-beta.1",
"ember-cli-simple-auth-devise": "^0.8.0-beta.1",
"ember-cli-uglify": "1.0.1",
"ember-data": "1.0.0-beta.16.1",
"ember-export-application-global": "^1.0.2"
}
}
The contents of my node_modules folder is:
broccoli-asset-rev
broccoli-sass
ember-cli
ember-cli-app-version
ember-cli-babel
ember-cli-bootstrap-sass
ember-cli-content-security-policy
ember-cli-dependency-checker
ember-cli-htmlbars
ember-cli-ic-ajax
ember-cli-inject-live-reload
ember-cli-qunit
ember-cli-simple-auth
ember-cli-simple-auth-devise
ember-cli-uglify
ember-data
ember-export-application-global
The contents of my bower.json is:
{
"name": "enerlytics",
"dependencies": {
"ember": "1.11.1",
"ember-cli-shims": "ember-cli/ember-cli-shims#0.0.3",
"ember-cli-test-loader": "ember-cli-test-loader#0.1.3",
"ember-data": "1.0.0-beta.16.1",
"ember-load-initializers": "ember-cli/ember-load-initializers#0.1.4",
"ember-qunit": "0.3.1",
"ember-qunit-notifications": "0.0.7",
"ember-resolver": "~0.1.15",
"jquery": "^1.11.1",
"loader.js": "ember-cli/loader.js#3.2.0",
"qunit": "~1.17.1",
"bootstrap-sass-official": "~3.3.4",
"ember-simple-auth": "0.8.0-beta.1"
}
}
and the contents of my bower_components folder is:
bootstrap-sass-official
ember
ember-cli-shims
ember-cli-test-loader
ember-data
ember-load-initializers
ember-qunit
ember-qunit-notifications
ember-resolver
ember-simple-auth
jquery
loader.js
qunit
qunit-notifications
The error you're seeing ("The ember generate command requires an entity name to be specified. For more details, use ember help.
") is actually irrelevant as it doesn't prevent the actually important tasks from running and will be fixed in the next version of Ember CLI probably.
For now you can safely ignore it.