ng generate error #10653

nginx17 · 2018-05-04T21:36:49Z

Versions

Angular CLI: 6.0.0
Node: 8.9.1
OS: linux x64
Angular: 6.0.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, http, language-service, material, platform-browser
... platform-browser-dynamic, platform-server, router

Package Version

angular-devkit/architect 0.6.0
angular-devkit/build-angular 0.6.0
angular-devkit/build-optimizer 0.6.0
angular-devkit/core 0.6.0
angular-devkit/schematics 0.6.0
ngtools/webpack 6.0.0
schematics/angular 0.6.0
schematics/update 0.6.0
rxjs 6.1.0
typescript 2.7.2
webpack 4.6.0

Repro steps

ng g component home

Could not find an NgModule. Use the skip-import option to skip importing in NgModule.

ng g component home --skip-import (same as generate everything)

Success generate component but wrong path not inside "src" but create new folder in root "home/user/PATH/app-id/home/home.component.*

WillsXiao · 2018-05-05T10:11:12Z

I have met the same issue.

TedCorleone · 2018-05-05T10:40:55Z

@nginx17 @WillsXiao , try to restart the terminal, issue caused by new thread.

WillsXiao · 2018-05-05T12:24:06Z

@TedCorleone I've tried it. It didn't work

wdev1980 · 2018-05-05T15:13:21Z

I have the same issue on OSX.

nginx17 · 2018-05-05T15:46:03Z

@TedCorleone same as @WillsXiao didn't work
I tried to restart the terminal and restart my computer but it still didn't work

matheusdavidson · 2018-05-06T00:13:00Z

same here on OSX, not only generates in the project root folder, but with all the path down to my project root folder.

My project:
/var/www/project/

When i generate, for example, home module:
/var/www/project/var/www/project/home/

matheusdavidson · 2018-05-06T00:32:56Z

Just generated a new angular 6 project and tried to generate a module or a component and had the same issue, i`m using the latest version:

Angular CLI: 6.0.0
Node: 9.10.1
OS: darwin x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

stewones · 2018-05-06T12:55:32Z

Same here

sandangel · 2018-05-06T14:02:33Z

the generated file should be put in the default project. For now, you must specify the project name with --project projectName

nginx17 · 2018-05-06T15:59:02Z

@sandangel still doesn't work

sandangel · 2018-05-06T16:17:16Z

@nginx17 notice that your project must be placed in the projectRoot folder configued in angular.json

ng g c home --project example
CREATE projects/example/src/app/home/home.component.css (0 bytes)
CREATE projects/example/src/app/home/home.component.html (23 bytes)
CREATE projects/example/src/app/home/home.component.spec.ts (614 bytes)
CREATE projects/example/src/app/home/home.component.ts (257 bytes)
UPDATE projects/example/src/app/app.module.ts (442 bytes)

nginx17 · 2018-05-06T17:04:37Z

@sandangel i try

what i missed, angular.json default generated, not change

matheusdavidson · 2018-05-06T17:37:05Z

@sandangel, still not working

It says there is no ngModule because its looking in the wrong place, what OS are you using?

matheusdavidson · 2018-05-06T17:41:24Z

If i try to create a module for example, it looks like it creates in the right place:

but it doesn't:

nginx17 · 2018-05-06T17:47:48Z

@matheusdavidson i think this is not about OS, you used OSX and i used Linux, but problem is same. i don't know how about windows

johren02 · 2018-05-06T19:36:44Z

I am also having this problem.

tdenkler0002 · 2018-05-06T21:49:57Z

Samesies. Having the problem as well. With brand new project generation -- default angular.json.

sandangel · 2018-05-06T22:04:27Z

hi everyone, try this:

ng new newproj
ng g app example #generate another app
ng g c home --project example #generate component in example app

I guess your global ng cli was not updated to v6 or ng v6 does not recognize project not placed in "projects" folder.
mine work fine:

ng new newproj               
CREATE newproj/README.md (1024 bytes)
CREATE newproj/angular.json (3408 bytes)
CREATE newproj/package.json (1311 bytes)
CREATE newproj/tsconfig.json (384 bytes)
CREATE newproj/tslint.json (2805 bytes)
CREATE newproj/.editorconfig (245 bytes)
CREATE newproj/.gitignore (503 bytes)
CREATE newproj/src/environments/environment.prod.ts (51 bytes)
CREATE newproj/src/environments/environment.ts (631 bytes)
CREATE newproj/src/favicon.ico (5430 bytes)
CREATE newproj/src/index.html (294 bytes)
CREATE newproj/src/main.ts (370 bytes)
CREATE newproj/src/polyfills.ts (3194 bytes)
CREATE newproj/src/test.ts (642 bytes)
CREATE newproj/src/assets/.gitkeep (0 bytes)
CREATE newproj/src/styles.css (80 bytes)
CREATE newproj/src/browserslist (375 bytes)
CREATE newproj/src/karma.conf.js (964 bytes)
CREATE newproj/src/tsconfig.app.json (194 bytes)
CREATE newproj/src/tsconfig.spec.json (282 bytes)
CREATE newproj/src/tslint.json (314 bytes)
CREATE newproj/src/app/app.module.ts (314 bytes)
CREATE newproj/src/app/app.component.css (0 bytes)
CREATE newproj/src/app/app.component.html (1141 bytes)
CREATE newproj/src/app/app.component.spec.ts (986 bytes)
CREATE newproj/src/app/app.component.ts (207 bytes)
CREATE newproj/e2e/protractor.conf.js (752 bytes)
CREATE newproj/e2e/src/app.e2e-spec.ts (299 bytes)
CREATE newproj/e2e/src/app.po.ts (208 bytes)
CREATE newproj/e2e/tsconfig.e2e.json (213 bytes)

> fsevents@1.2.3 install /Users/sand/Downloads/newproj/node_modules/fsevents
> node install

[fsevents] Success: "/Users/sand/Downloads/newproj/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> node-sass@4.9.0 install /Users/sand/Downloads/newproj/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/sand/.npm/node-sass/4.9.0/darwin-x64-57_binding.node

> node-sass@4.9.0 postinstall /Users/sand/Downloads/newproj/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/sand/Downloads/newproj/node_modules/node-sass/vendor/darwin-x64-57/binding.node
Testing binary
Binary is fine

> @angular/cli@6.0.0 postinstall /Users/sand/Downloads/newproj/node_modules/@angular/cli
> node ./bin/ng-update-message.js

added 1146 packages from 1269 contributors in 20.672s
    Successfully initialized git.

##################################################################################
ng g c home --project newproj
CREATE src/app/home/home.component.css (0 bytes)
CREATE src/app/home/home.component.html (23 bytes)
CREATE src/app/home/home.component.spec.ts (614 bytes)
CREATE src/app/home/home.component.ts (261 bytes)
UPDATE src/app/app.module.ts (388 bytes)

johren02 · 2018-05-06T22:19:41Z

@sandangel what do you mean by "ng v6 does not recognize project not placed in "projects" folder"? are you in a projects directory in your example? I assume all commands are run from the same directory level in your example

sandangel · 2018-05-06T22:30:58Z

@johren01 I mean with a newly created project, cli will generate app files under "src" folder, but if we generate a new app, by ng g app, generated files will be placed under "projects" folder. So I think when using ng g c home --project projName, if the projName is not placed under "projects" folder, the generated path might be wrong. I have tried but mine works fine for both project under "src" folder and "projects" folder. So I think may be your global cli version was not upgraded to 6. That what I guess based on your provided information. I can't reproduce your issue now on my macOS machine

johren02 · 2018-05-06T22:34:57Z

you are correct, I have correctly fixed my issue following your directions. thank you!

…

On May 6, 2018, at 6:31 PM, San Nguyen ***@***.***> wrote: @johren01 <https://github.com/johren01> I mean with a newly created project, cli will generate it under "src" folder, but if we generate a new app, by ng g app, generated files will be placed under "projects" folder. So I think when using ng g c home --project projName, if the projName is not placed under "projects" folder, the generated path might be wrong. I have tried but mine works fine for both project under "src" folder and "projects" folder. So I think may be your global cli version was not upgraded to 6. That what I guess based on your provided information. I can't reproduce your issue now on my macOS machine — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10653 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARtB_VmdanzzhnuL1FWMVSgd2EylZE_Aks5tv3m5gaJpZM4TzTZc>.

tdenkler0002 · 2018-05-06T22:38:02Z

Haha my issue was much more of a noob mistake. Upgraded my ng cli globally, but did not exit terminal for it to refresh (my guess) because now it seems to work just fine. :)

WillsXiao · 2018-05-08T10:06:07Z

I've solved my issued on my computer. My problems are below:

Because my working path is too deep, so I used command line $ ln -s to create the link on my root path.
I go to my project use the link which I created. When I use the command line $ pwd to get the path that is /Users/admin/angular/newProject. But my original path is /Users/admin/Desktop/localDisk/04-www/angular/newProject.

Solve the problem

Go to the project through original path

The angular results are below:

Mac:day01 admin$ ng g c components/header
CREATE src/app/components/header/header.component.css (0 bytes)
CREATE src/app/components/header/header.component.html (25 bytes)
CREATE src/app/components/header/header.component.spec.ts (628 bytes)
CREATE src/app/components/header/header.component.ts (269 bytes)
UPDATE src/app/app.module.ts (481 bytes)

Here is my angular info

Angular CLI: 6.0.0
Node: 9.4.0
OS: darwin x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

matheusdavidson · 2018-05-08T13:41:55Z

@WillsXiao, It shoudn’t be so difficult do generate things, that may be a workaround, not a solution.

nginx17 · 2018-05-08T14:38:56Z

@sandangel Problem solved, my case is same as @WillsXiao

fixes angular/angular-cli#10653

fixes #10653

rfuhrer · 2018-06-06T22:04:13Z

It looks like this was released in devkit 6.0.8 (CLI 6.0.8) but I'm still having the same problem:

PS C:\git\PrimeCore\Prime.Core> ng --version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 6.0.8
Node: 10.3.0
OS: win32 x64
Angular: 6.0.4
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cdk                      6.2.0
@angular/cli                      6.0.8
@angular/flex-layout              6.0.0-beta.15
@angular/material                 6.2.0
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.6.8
rxjs                              6.2.0
typescript                        2.7.2
webpack                           4.8.3

PS C:\git\PrimeCore\Prime.Core> ng g c shared/components/job-info
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
PS C:\git\PrimeCore\Prime.Core> ng g c /shared/components/job-info
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
PS C:\git\PrimeCore\Prime.Core> ng g c app/shared/components/job-info
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
PS C:\git\PrimeCore\Prime.Core> ng g c /app/shared/components/job-info
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
PS C:\git\PrimeCore\Prime.Core> ng g c /app/shared/components/job-info --path ClientApp
Could not find an NgModule. Use the skip-import option to skip importing in NgModule.
PS C:\git\PrimeCore\Prime.Core> ng g c shared/components/job-info --path ClientApp/app
CREATE ClientApp/app/shared/components/job-info/job-info.component.html (27 bytes)
CREATE ClientApp/app/shared/components/job-info/job-info.component.spec.ts (636 bytes)
CREATE ClientApp/app/shared/components/job-info/job-info.component.ts (278 bytes)
CREATE ClientApp/app/shared/components/job-info/job-info.component.scss (0 bytes)
UPDATE ClientApp/app/shared/shared.module.ts (1773 bytes)

and the angular.json which hasn't changed since upgrading to 6.0.0:

{
  "$schema": "./node_modules/@angular/cli/lib/config/schema.json",
  "version": 1,
  "newProjectRoot": "projects",
  "projects": {
    "prime-core-cli": {
      "root": "",
      "sourceRoot": "ClientApp",
      "projectType": "application",
      "architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
...

Timvdv · 2018-06-10T16:28:51Z

I also have this problem. Not sure if it helps but it looks like it's looking in the wrong directory for the NgModule. I think it's looking in the e2e directory instead of the src

darinclark · 2018-06-11T22:28:17Z

Still broken; though maybe broken in a different way. It seems to be ignoring the 'defaultProject' setting, and instead yanking the last project out of the list of projects. If I reorder my angular.json file such that the -e2e project is first, and the standard project is second, then generation of a new component goes into the correct location, instead of attempting to drop into -e2e.

rfuhrer · 2018-06-11T22:41:20Z

@darinclark Nailed it! I just tested by reordering my angular.json projects listing to put the e2e project first and the main project 2nd and then everything started working.

I found this already reported: #11111

dtekchandani · 2018-06-17T11:47:25Z

After upgrading cli to 6.0.8, cli is generating everything inside e2e folder.

durbonas · 2018-06-18T16:16:07Z

@rfuhrer That worked for me!! Thanks.

Just pasting it here for others. Very simple fix for now.

It appears to just grab the last project in your angular.json. So if you have a main project and then a e2e project, reorder them so the main project is last and your default generate commands will go to the main project instead of e2e. If you need to generate something to the e2e project then you can use the --path e2e override

beiatisi · 2018-06-19T09:40:13Z

You can use "ng new you_project_name" copy angular.json paste to your original project directory.

grimace · 2018-06-24T17:50:58Z

this is still happening on 6.0.8.

This also still happened to me after moving the non e2e project after the others. And this happened to me because I ran 'ng update' on my project.

found the answer here:
https://github.com/angular/angular-cli/issues/11111

basically, find the 'project name'-e2e
set:
"root": "e2e/",
and remove:
"sourceRoot": "e2e",

srkt · 2018-06-25T17:04:07Z

Worked by moving the e2e project in angular.json to top of the project list

grimace · 2018-06-25T17:39:38Z

That didn't work for me, hence more digging and now works without moving projects in angular.json.

dkteam · 2018-06-26T10:02:19Z

Fix here, everyone.

https://github.com/rafasantos/matchandtrade-web-ui/commit/a5e6b6085157285900c6a3cfdc5e0ceccda3a9fa

ivyblossom · 2018-06-26T14:53:27Z

Thanks @dkteam 👏
It worked for me 🎉

ZdebK · 2018-06-27T08:56:44Z

For me worked that I changed the path. I was in src folder.
cd ../
fixed this :D

PawelOwczarekFalcon · 2018-07-03T17:53:37Z

@grimace works fine :)

agroupp · 2018-07-09T12:21:01Z

@grimace was very helpful, thanks

chrisBosse · 2018-07-17T14:53:00Z

Very much like @grimace 's workaround above.

For me, I was able to leave the project order the same in angular.json and only change the e2e project's"root" path.

{
  "projects": {
    "myGreatApp": {
      "root": ""
    },
    "myGreatApp-e2e": {
      "root": "e2e"
      }
  }
}

"projects"."myGreatApp-e2e"."root" changes from "" to "e2e" allowing the ng g module test command to build the module in the correct location. We don't use e2e so I don't know what else this breaks. Easy enough, as a workaround, to change and put back just before building an new module.

Angular 6.0.6
Angular CLI 6.0.8
angular-devkit/schematics 0.6.8

jgswiss · 2018-07-25T16:54:12Z

Deleting the "e2e" in angular.json under:
"app-e2e": {
"root": "",
"sourceRoot": "e2e",
"projectType": "application"

to

"app-e2e": {
"root": "",
"sourceRoot": "",
"projectType": "application",

fixed my problem!

Eternal21 · 2018-07-27T12:56:16Z

Same problem on Windows, after upgrading to the latest cli (6.1.1). The solution that worked for me was suggested by @srkt

Open angular.json (it should be right in the root of your app)
Find "projects" property.
Inside the project property you will see two children properties:
"yourappname-app" and "yourappname-app-e2e"
Switch their order (cut the "yourname-app-e2e" property and their children, and place them above "yourappname-app" property)
I had to restart VS Code for it to start working (you may need to restart your terminal or whatever you're using)

gremo · 2018-07-28T09:40:30Z

I'm not having any problem changing the root folder from src to client with CLI version 6.1 (installed globally) on Windows 10 x64. Here is what I did:

ng new ng-test --style scss --skip-install

Save the patch file root-change.diff:

diff --git a/angular.json b/angular.json
index 56f7e2e..2d30500 100644
--- a/angular.json
+++ b/angular.json
@@ -5,7 +5,7 @@
   "projects": {
     "ng-test": {
       "root": "",
-      "sourceRoot": "src",
+      "sourceRoot": "client",
       "projectType": "application",
       "prefix": "app",
       "schematics": {
@@ -18,16 +18,16 @@
           "builder": "@angular-devkit/build-angular:browser",
           "options": {
             "outputPath": "dist/ng-test",
-            "index": "src/index.html",
-            "main": "src/main.ts",
-            "polyfills": "src/polyfills.ts",
-            "tsConfig": "src/tsconfig.app.json",
+            "index": "client/index.html",
+            "main": "client/main.ts",
+            "polyfills": "client/polyfills.ts",
+            "tsConfig": "client/tsconfig.app.json",
             "assets": [
-              "src/favicon.ico",
-              "src/assets"
+              "client/favicon.ico",
+              "client/assets"
             ],
             "styles": [
-              "src/styles.scss"
+              "client/styles.scss"
             ],
             "scripts": []
           },
@@ -35,8 +35,8 @@
             "production": {
               "fileReplacements": [
                 {
-                  "replace": "src/environments/environment.ts",
-                  "with": "src/environments/environment.prod.ts"
+                  "replace": "client/environments/environment.ts",
+                  "with": "client/environments/environment.prod.ts"
                 }
               ],
               "optimization": true,
@@ -71,17 +71,17 @@
         "test": {
           "builder": "@angular-devkit/build-angular:karma",
           "options": {
-            "main": "src/test.ts",
-            "polyfills": "src/polyfills.ts",
-            "tsConfig": "src/tsconfig.spec.json",
-            "karmaConfig": "src/karma.conf.js",
+            "main": "client/test.ts",
+            "polyfills": "client/polyfills.ts",
+            "tsConfig": "client/tsconfig.spec.json",
+            "karmaConfig": "client/karma.conf.js",
             "styles": [
-              "src/styles.scss"
+              "client/styles.scss"
             ],
             "scripts": [],
             "assets": [
-              "src/favicon.ico",
-              "src/assets"
+              "client/favicon.ico",
+              "client/assets"
             ]
           }
         },
@@ -89,8 +89,8 @@
           "builder": "@angular-devkit/build-angular:tslint",
           "options": {
             "tsConfig": [
-              "src/tsconfig.app.json",
-              "src/tsconfig.spec.json"
+              "client/tsconfig.app.json",
+              "client/tsconfig.spec.json"
             ],
             "exclude": [
               "**/node_modules/**"
@@ -128,4 +128,4 @@
     }
   },
   "defaultProject": "ng-test"
-}
\ No newline at end of file
+}
diff --git a/client/tsconfig.app.json b/client/tsconfig.app.json
index 8ea061e..7e02a41 100644
--- a/client/tsconfig.app.json
+++ b/client/tsconfig.app.json
@@ -5,7 +5,7 @@
     "types": []
   },
   "exclude": [
-    "src/test.ts",
+    "client/test.ts",
     "**/*.spec.ts"
   ]
 }

Apply the patch file and install vendor:

git apply root-change.diff
npm i

All the following commands works:

ng serve --open
ng build --prod
ng test
ng e2e

Component generation will correctly generate the component in the new root folder:

ng g c home --dry-run
CREATE client/app/home/home.component.html (23 bytes)
CREATE client/app/home/home.component.spec.ts (614 bytes)
CREATE client/app/home/home.component.ts (262 bytes)
CREATE client/app/home/home.component.scss (0 bytes)
UPDATE client/app/app.module.ts (388 bytes)

$ ng g m core --dry-run
CREATE client/app/core/core.module.spec.ts (259 bytes)
CREATE client/app/core/core.module.ts (188 bytes)

zachgoll · 2018-09-15T16:18:23Z

My fix was fairly simple:

Problem: I was running the command ng generate component components/home (create the "home" component in the components directory) from the location of angular-project/src/.

Solution: Back out into the root of your angular project and specify the path you want the component to generate in like so:

ng generate component src/components/home

The above command should create a "home" component in the components/ directory inside the src/ directory.

Hope that helps!

angular-automatic-lock-bot · 2019-09-08T15:41:15Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

matheusdavidson mentioned this issue May 6, 2018

NG CLI 6: ng generate put files in wrong place #10672

Closed

matheusdavidson mentioned this issue May 6, 2018

Can't use ng CLI to genereate a component in a library project #10674

Closed

matheusdavidson mentioned this issue May 7, 2018

The "ng generate" command does not work with custom "sourceRoot" property in "angular.json" #10702

Closed

clydin added the comp: cli/generate label May 8, 2018

clydin mentioned this issue May 8, 2018

CLI v6.0.0 failing to generate components - unable to locate module #10725

Closed

hansl closed this as completed in angular/devkit#990 Jun 5, 2018

hansl pushed a commit to angular/devkit that referenced this issue Jun 5, 2018

fix(@schematics/angular): Fix usage of sourceRoot configuration value

524c7cf

fixes angular/angular-cli#10653

hansl pushed a commit that referenced this issue Jun 6, 2018

fix(@schematics/angular): Fix usage of sourceRoot configuration value

63d5b43

fixes #10653

hansl pushed a commit that referenced this issue Jun 6, 2018

fix(@schematics/angular): Fix usage of sourceRoot configuration value

698ed0e

fixes #10653

hansl pushed a commit that referenced this issue Jun 6, 2018

fix(@schematics/angular): Fix usage of sourceRoot configuration value

486c153

fixes #10653

rfuhrer mentioned this issue Jun 11, 2018

bug: not generate files to the defaultProject #11111

Closed

zachgoll unassigned Brocco Sep 15, 2018

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019

ng generate error #10653

ng generate error #10653

Comments

nginx17 commented May 4, 2018

Versions

Package Version

Repro steps

WillsXiao commented May 5, 2018

TedCorleone commented May 5, 2018

WillsXiao commented May 5, 2018

wdev1980 commented May 5, 2018

nginx17 commented May 5, 2018 • edited Loading

matheusdavidson commented May 6, 2018 • edited Loading

matheusdavidson commented May 6, 2018

stewones commented May 6, 2018

sandangel commented May 6, 2018

nginx17 commented May 6, 2018

sandangel commented May 6, 2018

nginx17 commented May 6, 2018

matheusdavidson commented May 6, 2018 • edited Loading

matheusdavidson commented May 6, 2018

nginx17 commented May 6, 2018

johren02 commented May 6, 2018

tdenkler0002 commented May 6, 2018

sandangel commented May 6, 2018 • edited Loading

johren02 commented May 6, 2018

sandangel commented May 6, 2018 • edited Loading

johren02 commented May 6, 2018 via email

tdenkler0002 commented May 6, 2018

WillsXiao commented May 8, 2018 • edited Loading

I've solved my issued on my computer. My problems are below:

Solve the problem

The angular results are below:

Here is my angular info

matheusdavidson commented May 8, 2018

nginx17 commented May 8, 2018 • edited Loading

rfuhrer commented Jun 6, 2018 • edited Loading

Timvdv commented Jun 10, 2018

darinclark commented Jun 11, 2018

rfuhrer commented Jun 11, 2018

dtekchandani commented Jun 17, 2018

durbonas commented Jun 18, 2018

beiatisi commented Jun 19, 2018

grimace commented Jun 24, 2018 • edited Loading

srkt commented Jun 25, 2018

grimace commented Jun 25, 2018

dkteam commented Jun 26, 2018

ivyblossom commented Jun 26, 2018

ZdebK commented Jun 27, 2018 • edited Loading

PawelOwczarekFalcon commented Jul 3, 2018

agroupp commented Jul 9, 2018

chrisBosse commented Jul 17, 2018 • edited Loading

jgswiss commented Jul 25, 2018

Eternal21 commented Jul 27, 2018

gremo commented Jul 28, 2018 • edited Loading

zachgoll commented Sep 15, 2018

angular-automatic-lock-bot bot commented Sep 8, 2019

nginx17 commented May 5, 2018 •

edited

Loading

matheusdavidson commented May 6, 2018 •

edited

Loading

matheusdavidson commented May 6, 2018 •

edited

Loading

sandangel commented May 6, 2018 •

edited

Loading

sandangel commented May 6, 2018 •

edited

Loading

WillsXiao commented May 8, 2018 •

edited

Loading

nginx17 commented May 8, 2018 •

edited

Loading

rfuhrer commented Jun 6, 2018 •

edited

Loading

grimace commented Jun 24, 2018 •

edited

Loading

ZdebK commented Jun 27, 2018 •

edited

Loading

chrisBosse commented Jul 17, 2018 •

edited

Loading

gremo commented Jul 28, 2018 •

edited

Loading