I have a project that was not created using ng new (rather, I followed the quickstart guide). When I run an angular CLI command in that project (such as n
You should be able to run ng init and follow the prompts. Have a look at this issue if you need some guidance: https://github.com/angular/angular-cli/issues/755
Edit (March 13, 2017):
ng-init was removed from the latest version of the angular cli.
https://github.com/angular/angular-cli/pull/4628
So for now you'll need to resort to mimicking what it tried to accomplish. ie:
Create a new angular project ng new myTemplate
Copy relevant files to your existing project from your new myTemplate project:
.angular-cli.json package.json tslint.json src/polyfills.ts src/styles.css src/tsconfig.json
Depending on the state of your existing application you may want to copy over way more or way less. I guess this is why the feature was removed from the CLI. There isn't really any way for it to know exactly what you want it to do.
ng init was removed from the latest version of the angular CLI but You can use yarn package manager to resolve all the dependencies. In order to use yarn, you have to install it first.
To install yarn in Ubuntu, enter the following command in your terminal:
sudo apt-get update && sudo apt-get install yarn
For Windows you can download yarn installer from here .
After installing yarn, you can run the command yarn install in your project direcotry which will download all the dependencies of your project.
For additional information about yarn check official docs
ng init has been removed. What worked for me was to manually create a .angular-cli.json file in the root folder with the following keys:
{
"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
"project": {
"version": "1.0.0",
"name": "new-cli"
},
"apps": [
{
"root": "src",
"outDir": "dist",
"assets": [
"assets"
],
"index": "index.html",
"main": "main.ts",
"polyfills": "polyfills.ts",
"prefix": "app",
"scripts": [],
"environmentSource": "environments/environment.ts"
}
]
}
You will have to change values according to your setup of course.
Try the below solution may be it could help.
npm install -g angular-cling new project_folder_namecd project_folder_nameng serve (Note: Now on localhost:4200, the demo project will run)src folder of your existing project and replace with the src of your newly created project from project's root folder only.Copy everything from package.json from the existing project. Run npm install again.If it breaks, it probably needs tinker with webpack.config