Need more documentation about the project structure and deployment with Nest js.

iPhone X not waking up or ringing with incoming phone calls

In the ReadMe.md Deploy section, can you add a link to info on configuring auth for gp-pages?

When manually copying the dist/apps/webapp folder to the root of a GitHub Pages repo, a path starting with localhost:8080 causes the following Javascript error:

localhost:8080/auth/realms/is360/.well-known/openid-configuration:1 
Failed to load resource: net::ERR_CONNECTION_REFUSED

(Manual copying of the dist/apps/webapp folder is my attempted workaround until I get npm run deploy:mock deploying.) #6

Got an error on npm start
ERROR in node_modules/@ngxs/store/src/of-action.d.ts(1,34): error TS2307: Cannot find module 'rxjs/interfaces'.
seems like there is an issue with rxjs-compat
got these rxjs packages versions installed:
[email protected]
[email protected]

ng -v:

Angular CLI: 1.7.3
Node: 8.9.1
OS: win32 x64
Angular: 6.0.0-rc.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

@angular/cdk: 6.0.0-rc.0
@angular/cli: 1.7.3
@angular/flex-layout: 5.0.0-beta.14
@angular/material-moment-adapter: 6.0.0-rc.0
@angular/material: 6.0.0-rc.0
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.4.8
@angular-devkit/schematics: 0.4.8
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.4.8
@schematics/package-update: 0.3.2
typescript: 2.7.2
webpack: 3.11.0

Am I missing a configuration step in order to deploy to gp-pages?
The error occurs after the circular dependency detected warning, but probably something else.

> [email protected] deploy:mock /Library/Sites/ngx-starter-kit-test
> npm run build:mock && ngh --dir dist/apps/webapp

> [email protected] build:mock /Library/Sites/ngx-starter-kit-test
> ng build -c=mock --base-href /ngx-starter-kit/

                                                                              m Date: 2018-06-25T14:42:15.892Z
Hash: 7e8d6a295e358d049930
Time: 47586ms
chunk {0} common.js (common) 7.31 kB  [rendered]
chunk {1} 1.js () 599 kB  [rendered]
chunk {2} 2.js () 47.1 kB  [rendered]
chunk {3} 3.js () 22.2 kB  [rendered]
chunk {4} 4.js () 59.5 kB  [rendered]
chunk {5} 5.js () 28.5 kB  [rendered]
chunk {6} 6.js () 150 kB  [rendered]
chunk {7} 7.js () 121 kB  [rendered]
chunk {8} 8.js () 1.12 MB  [rendered]
chunk {9} 9.js () 4.26 kB  [rendered]
chunk {10} 10.js () 522 kB  [rendered]
chunk {11} 11.js () 95.9 kB  [rendered]
chunk {12} runtime.js (runtime) 1.81 kB [entry] [rendered]
chunk {13} assets/themes/purple-green.css (assets/themes/purple-green) 40.7 kB [initial] [rendered]
chunk {14} assets/themes/pink-bluegrey.css (assets/themes/pink-bluegrey) 40.7 kB [initial] [rendered]
chunk {15} assets/themes/indigo-pink.css (assets/themes/indigo-pink) 40.7 kB [initial] [rendered]
chunk {16} assets/themes/deeppurple-amber.css (assets/themes/deeppurple-amber) 40.6 kB [initial] [rendered]
chunk {17} styles.css (styles) 121 kB [initial] [rendered]
chunk {18} polyfills.js (polyfills) 59.6 kB [initial] [rendered]
chunk {19} main.js (main) 1.21 MB [initial] [rendered]

WARNING in Circular dependency detected:
libs/auth/src/lib/auth.service.ts -> libs/auth/src/lib/auth.state.ts -> libs/auth/src/lib/auth.service.ts

WARNING in Circular dependency detected:
libs/auth/src/lib/auth.state.ts -> libs/auth/src/lib/auth.service.ts -> libs/auth/src/lib/auth.state.ts
An error occurred!
 Error: Unspecified error (run without silent option for detail)
    at /Library/Sites/ngx-starter-kit-test/node_modules/gh-pages/lib/index.js:232:19
    at _rejected (/Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:844:24)
    at /Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:870:30
    at Promise.when (/Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:1122:31)
    at Promise.promise.promiseDispatch (/Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:788:41)
    at /Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:604:44
    at runSingle (/Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:137:13)
    at flush (/Library/Sites/ngx-starter-kit-test/node_modules/q/q.js:125:13)
    at process._tickCallback (internal/process/next_tick.js:172:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] deploy:mock: `npm run build:mock && ngh --dir dist/apps/webapp`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] deploy:mock script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Loren/.npm/_logs/2018-06-25T14_42_17_987Z-debug.log
Lorens-MacBook-Pro:ngx-starter-kit-test Loren$ 


Complete log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/Users/Loren/.npm-packages/bin/npm',
1 verbose cli   'run',
1 verbose cli   'deploy:mock' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predeploy:mock', 'deploy:mock', 'postdeploy:mock' ]
5 info lifecycle [email protected]~predeploy:mock: [email protected]
6 info lifecycle [email protected]~deploy:mock: [email protected]
7 verbose lifecycle [email protected]~deploy:mock: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~deploy:mock: PATH: /Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Library/Sites/ngx-starter-kit-test/node_modules/.bin:/anaconda3/bin:/Users/Loren/.node/bin:/Users/Loren/.npm-packages/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:/opt/X11/bin
9 verbose lifecycle [email protected]~deploy:mock: CWD: /Library/Sites/ngx-starter-kit-test
10 silly lifecycle [email protected]~deploy:mock: Args: [ '-c', 'npm run build:mock && ngh --dir dist/apps/webapp' ]
11 silly lifecycle [email protected]~deploy:mock: Returned: code: 1  signal: null
12 info lifecycle [email protected]~deploy:mock: Failed to exec deploy:mock script
13 verbose stack Error: [email protected] deploy:mock: `npm run build:mock && ngh --dir dist/apps/webapp`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:947:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:236:5)
14 verbose pkgid [email protected]
15 verbose cwd /Library/Sites/ngx-starter-kit-test
16 verbose Darwin 17.6.0
17 verbose argv "/usr/local/bin/node" "/Users/Loren/.npm-packages/bin/npm" "run" "deploy:mock"
18 verbose node v10.0.0
19 verbose npm  v6.1.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] deploy:mock: `npm run build:mock && ngh --dir dist/apps/webapp`
22 error Exit status 1
23 error Failed at the [email protected] deploy:mock script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

ng build -c=production will cause following error with latest webpack-sources: 1.3.0

workaround: lock "webpack-sources": "1.0.1" by setting resolutions in package.json

  "resolutions": {
    "webpack-sources": "1.0.1"
  }

 ng build -c=production 
 93% after chunk asset optimization SourceMapDevToolPlugin 0-es5.f6c71fd8551f3b4ec570.js generate SourceMapUnhandled rejection Error: original.line and original.column are not numbers -- you probably meant to omit the original mapping entirely and only map the generated position. If so, pass null for the original mapping instead of an object with empty or null values.
    at SourceMapGenerator_validateMapping [as _validateMapping] (/Developer/Work/SPA/ngx-starter-kit/node_modules/source-map/lib/source-map-generator.js:276:15)
    at SourceMapGenerator_addMapping [as addMapping] (/Developer/Work/SPA/ngx-starter-kit/node_modules/source-map/lib/source-map-generator.js:110:12)
    at /Developer/Work/SPA/ngx-starter-kit/node_modules/source-map/lib/source-map-generator.js:72:17
    at Array.forEach (<anonymous>)
    at BasicSourceMapConsumer.SourceMapConsumer_eachMapping [as eachMapping] (/Developer/Work/SPA/ngx-starter-kit/node_modules/source-map/lib/source-map-consumer.js:157:14)
    at Function.SourceMapGenerator_fromSourceMap [as fromSourceMap] (/Developer/Work/SPA/ngx-starter-kit/node_modules/source-map/lib/source-map-generator.js:48:24)
    at SourceMapSource.node (/Developer/Work/SPA/ngx-starter-kit/node_modules/webpack-sources/lib/SourceMapSource.js:32:35)
    at SourceMapSource.proto.sourceAndMap (/Developer/Work/SPA/ngx-starter-kit/node_modules/webpack-sources/lib/SourceAndMapMixin.js:30:18)
    at getTaskForFile (/Developer/Work/SPA/ngx-starter-kit/node_modules/webpack/lib/SourceMapDevToolPlugin.js:37:30)
    at /Developer/Work/SPA/ngx-starter-kit/node_modules/webpack/lib/SourceMapDevToolPlugin.js:136:20
    at Array.forEach (<anonymous>)
    at /Developer/Work/SPA/ngx-starter-kit/node_modules/webpack/lib/SourceMapDevToolPlugin.js:130:12
    at SyncHook.eval [as call] (eval at create (/Developer/Work/SPA/ngx-starter-kit/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:13:1)
    at SyncHook.lazyCompileHook (/Developer/Work/SPA/ngx-starter-kit/node_modules/tapable/lib/Hook.js:154:20)
    at /Developer/Work/SPA/ngx-starter-kit/node_modules/webpack/lib/Compilation.js:1315:42
    at eval (eval at create (/Developer/Work/SPA/ngx-starter-kit/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:18:1)

When cloning the package and simply run

yarn install

the following file (./.npmrc) throws an error..

This is because the comment in the ./.npmrc file should be # and not // i guess?!

All the best

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

I am struggling to debug (use breakpoints and inspect the application flow) using vscode. Can someone share me how to configure the debug. I have tried multiple solutions available after googling. But all of them are not in Nx Workspace or with Angular.

Can some one share the launch.json / nodemon-debug.json or other related files for debugging?

Thanks

vs code save at a time need how much time？

I've tried dropping my project into nx in the same amount of time as a normal ng-cli.

• cli: 45s
• nx: 45s

If I use a compiled libs and load it into my app, ng-cli will compile much faster than nx.

• cli: 5-10s
• nx: 45s

The npm package @ngx-starter-kit/ngx-utils does not exist anymore.
Can you restore npm package please?

First of all, I want to say that this kit you put together here its AWESOME and I have learned a lot about many packages and architectural points using it, THANK YOU!

I wanted to mention an issue I was having though and it is related the this command:

yarn commit

Once you enter all the information it never completed the first step of lint-stage. It never complete this command:

yarn affected:lint --uncommitted --parallel

If I run it separately it runs correctly but not when called using lint-stage. Do I need to setup anything before run this command?

This link to the default keycloak sample configuration is broken.., can you pls. provide an updated link?

-- https://github.com/xmlking/ngx-starter-kit/tree/52f7292aece716a8a79b02c43a45465561ce327e/docs/.deploy/keycloak/realm-manual-import.json

The devDependency @angular-devkit/build-angular was updated from 0.802.0-rc.0 to 0.802.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular-devkit/build-angular is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The optionalDependency @semantic-release/github was updated from 5.4.1 to 5.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/github is a optionalDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/jest was updated from 24.0.15 to 24.0.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• chore(deps): update dependency typescript to v4.7.4
• chore(deps): update dependency typescript to v4.7.4

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• chore(deps): update commitlint monorepo to v17.0.3 (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency @semantic-release/github to v8.0.5
• chore(deps): update dependency @types/passport to v1.0.9
• chore(deps): update dependency angular-cli-ghpages to v1.0.3
• chore(deps): update dependency chart.js to v3.8.2
• chore(deps): update dependency immer to v9.0.15
• chore(deps): update dependency intersection-observer to v0.12.2
• chore(deps): update dependency keycloak-js to v18.0.1
• chore(deps): update dependency lint-staged to v13.0.3
• chore(deps): update dependency mini-css-extract-plugin to v2.6.1
• chore(deps): update dependency nodemailer to v6.7.7
• chore(deps): update dependency nodemon to v2.0.19
• chore(deps): update dependency rxjs to v7.5.6
• chore(deps): update dependency rxjs to v7.5.6
• chore(deps): update dependency screenfull to v6.0.2
• chore(deps): update dependency supertest to v6.2.4
• chore(deps): update dependency ts-jest to v28.0.7
• chore(deps): update dependency ts-loader to v9.3.1
• chore(deps): update dependency typeorm to v0.3.7
• chore(deps): update dependency webpack-dev-server to v4.9.3
• chore(deps): update font awesome (@fortawesome/angular-fontawesome, @fortawesome/fontawesome-svg-core, @fortawesome/free-brands-svg-icons, @fortawesome/free-solid-svg-icons)
• chore(deps): update jest monorepo (@types/jest, jest)
• chore(deps): update nest monorepo (@nestjs/common, @nestjs/passport)
• chore(deps): update ngx-formly monorepo to v5.12.6 (@ngx-formly/core, @ngx-formly/material, @ngx-formly/schematics)
• fix(deps): update dependency @godaddy/terminus to v4.11.1
• fix(deps): update dependency @nestjs/axios to v0.1.0
• fix(deps): update dependency cache-manager to v4.1.0
• fix(deps): update dependency core-js to v3.24.0
• fix(deps): update dependency cypress to v10.3.1
• fix(deps): update dependency date-fns to v2.29.1
• fix(deps): update dependency helmet to v5.1.1
• fix(deps): update dependency jest-preset-angular to v12.2.0
• fix(deps): update dependency ng-packagr to v14.1.0
• fix(deps): update dependency ngx-quicklink to v0.3.0
• fix(deps): update dependency prettier to v2.7.1
• fix(deps): update dependency swagger-ui-express to v4.5.0
• fix(deps): update dependency ts-node to v10.9.1
• fix(deps): update dependency ua-parser-js to v0.8.1
• fix(deps): update dependency webpack to v5.74.0
• fix(deps): update helm values alpine to v3.16
• fix(deps): update helm values docker.io/bitnami/postgresql to v14.4.0
• fix(deps): update helm values nginxinc/nginx-unprivileged to v1.23.1
• fix(deps): update nrwl packages to v14.4.3 (@nrwl/angular, @nrwl/nest, @nrwl/workspace)
• feat(deps): update actions/cache action to v3
• feat(deps): update actions/checkout action to v3
• feat(deps): update actions/setup-node action to v3
• feat(deps): update dependency @nestjs/cqrs to v9
• feat(deps): update dependency @nestjs/swagger to v6
• feat(deps): update dependency @nestjs/typeorm to v9
• feat(deps): update dependency commitizen to v4
• feat(deps): update dependency docker.elastic.co/elasticsearch/elasticsearch to v8
• feat(deps): update dependency docker.elastic.co/kibana/kibana to v8
• feat(deps): update dependency ini to v3
• feat(deps): update dependency jose to v4
• feat(deps): update dependency ngx-deploy-npm to v4
• feat(deps): update dependency ngx-page-scroll to v9
• feat(deps): update dependency ngx-page-scroll-core to v9
• feat(deps): update dependency source-map-loader to v4
• feat(deps): update dependency ua-parser-js to v1
• feat(deps): update dependency yargs-parser to v21
• feat(deps): update github/codeql-action action to v2
• feat(deps): update nest monorepo to v9 (major) (@nestjs/common, @nestjs/core, @nestjs/microservices, @nestjs/passport, @nestjs/platform-express, @nestjs/platform-socket.io, @nestjs/schematics, @nestjs/terminus, @nestjs/testing, @nestjs/websockets)
• feat(deps): update node.js to v18

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency terser to 5.14.2 [security]
• fix(deps): roll back dependency @xmlking/ngx-knob to ^1.1.1
• chore(deps): update dependency glob-parent to v6.0.2
• chore(deps): update dependency underscore to v1.13.4
• chore(deps): update helm values jboss/keycloak to v16.1.1
• fix(deps): update angular monorepo (@angular/animations, @angular/common, @angular/compiler, @angular/compiler-cli, @angular/core, @angular/forms, @angular/language-service, @angular/localize, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router, @angular/service-worker, angular-in-memory-web-api, zone.js)
• fix(deps): update angular-cli monorepo to v14.1.0 (@angular-devkit/build-angular, @angular/cli)
• fix(deps): update angularmaterial monorepo (@angular/cdk, @angular/material)
• fix(deps): update dependency docker.elastic.co/elasticsearch/elasticsearch to v7.17.5
• fix(deps): update dependency docker.elastic.co/kibana/kibana to v7.17.5
• fix(deps): update dependency jose to v3.20.3
• fix(deps): update dependency postgres to v14.4
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• feat(deps): update dependency d3 to v7
• feat(deps): update dependency d3-selection to v3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

My Webstorm editor warns that combineLatest in router.state.ts (line 42) is deprecated ....

angular/angular#31791

Hey @xmlking ,

i was just wondering, if it would be benefitial to have dedicated package.json files in each \libs and \apps folder (i.e., each app handles their own dependencies). Is there a specific reason, why you don't follow this approach?

All the best and thanks a lot for your time and effort

Running

yarn install

on an "empty" project takes forever..

Done in 1031.48s.

thats about 15 minutes ;)

How can i speed up this process?

All the best

When trying to use the InViewportModule I get this error when trying to compile --aot

Module not found: Error: Can't resolve 'date-fns/esm' in '/Users/joe/projects/mr/node_modules/@ngx-starter-kit/ngx-utils/fesm5'

The dependency filepond was updated from 4.3.1 to 4.3.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

filepond is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Dear @xmlking ,

first of all - from what i have seen from the code, this looks f*cking amazing! WOW! 🎉
Unfortunately i was not able to see it in action - the demo link is constantly loading. Further, it shows some errors in the console..

All the best!

No matter what I try, I can't seem to generate a new application in the repo. There is no error or any other output and no files are created. When creating a workspace from scratch seems to work fine, until I update angular core. Does that mean that I need to wait for a fix from nx or add it manually just like issue #8 ?

(Love the repo btw, learning a lot from it. )

env:
window7-64
nodejs: v8.11.3
npm: 5.6.6
Angular CLI: 6.1.5

add new lib by :
ng g lib settings --routing --lazy --prefix=ngx --parent-module=libs/dashboard/src/lib/dashboard.module.ts --tags=child-module

get error when start:
settings.module.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include'

detail:

ERROR in F:/sgglxt/ngrx/ngx-starter-kit-master/libs/settings/src/lib/settings.module.ts
Module build failed: Error: F:\sgglxt\ngrx\ngx-starter-kit-master\libs\settings\src\lib\settings.module.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include'
property.
at AngularCompilerPlugin.getCompiledFile (F:\sgglxt\ngrx\ngx-starter-kit-master\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:749:23)
at plugin.done.then (F:\sgglxt\ngrx\ngx-starter-kit-master\node_modules@ngtools\webpack\src\loader.js:41:31)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

Hi,
I'm using the InViewport directive in my app, but when I run it on Safari the browser is freezed and I can only Force quit. I tried to use IntersectionObserver polyfill, as written in the doc, but it does not resolve the issue.

The devDependency @nrwl/workspace was updated from 8.0.1 to 8.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@nrwl/workspace is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

What is this

@import 'var';
in scss files ?

Hi, these aren't issues with your code. The following are hurdles I've hit while trying to set up a copy of the grid module.

1. I'm successfully displaying a bike share vehicles list locally using the Coord.co API with the following repo:

https://github.com/DirectoryBuilder/ngx-project/blob/master/notes.md

I moved the grid folder content into libs/home/src/lib/containers/vehicles and renamed account to vehicle throughout.

The grid card view works locally with the Coord API (but the list view doesn't show specific data. It does however repeat, indicating the data is reaching the list).

2. In a forked repo, I copied "libs/grid" to "libs/gridmap"
and replaced "account" with "vehicle".

https://github.com/DirectoryBuilder/ngx-starter-kit

Adding gridmap to dashboard.module.ts is causing this error:

Error: Uncaught (in promise): Error: Cannot find module '@ngx-starter-kit/gridmap'
Error: Cannot find module '@ngx-starter-kit/gridmap'

Were would I define the new gridmap module?

menu-data.ts (line 44) returns a 404 page for /dashboard/vehilcles.

Using 'gridmap' in dashboard.module.ts animation (line 49) also causes the error:

ERROR in Could not resolve module @ngx-starter-kit/gridmap relative to /Library/Sites/ngx-starter-kit/libs/dashboard/src/lib/dashboard.module.ts

Thanks for any pointers you can provide!

Dear @xmlking ,

thanks again for this really (!) awesome (!) starter package. This is a piece of art 😆

I recently added my own package to the libs folder and it worked like a charm. Then i started to write tests. In this context, however, i stumbled upon a few questions. Maybe you can help me with the latter?

1) Running tests via IDE:

Consider, for example, the following "dummy" test-case:

describe('Something', () => {
  it('should be ok', () => {
    expect(true).toBeTruthy();
  });
});

Obviously, this test should pass. As I use IntelliJ WebStorm, i see the green "run" buttons next to describe() and it() to specifically run one specific test or an entire suite. However, when clicking this button, it errors with:

ts-jest[config] (WARN) TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):

if i run the test via console

ng test libraryName

it runs all tests and they pass.

2) Configuration & Schemantics

When creating a new lib in the project via ng g lib NAME it automatically modifies the .\angular.json file. In this context, it creates a key in projects.NAME, where some basic configuration stuff is located.
However, i noticed, that in my "own generated" libs the key projects.NAME.architect.test.options.setupFile is missing. Further, the referenced file (e.g., libs/NAME/src/test-setup.ts) is also missing / not generated!

3) "Hiding" Test Classes in Packages

In order to test certain functionality, i created some dummy classes (e.g,. a Book and Author class). Respective classes are, for example, located in libs/NAME/test/mocks/book.ts.

Of course, these classes are only vital for this specific library and does not need to be available in other. How can i "hide" them in other packages (e.g., disable the "intelli sense" auto-completion) for such "test classes"? Is this possible?

Thank you so much for this awesome project! You rock!
All the best from Germany

with typescript 3.2.2, we see following ignorable error when API server is started ng serve api

[email protected] works fine, [email protected] show error

ERROR in undefined(undefined,undefined):
TS2321: Excessive stack depth comparing types 'any' and 'FindConditions<T>'.
Version: typescript 3.2.2

Depends on:
microsoft/TypeScript#21592

nrwl/nx#2147

The error occurs when running either npm run build:prod or npm run deploy:mock.
No other changes were made. Occurs before and after running npm audit fix.
To install, I ran npm install before npm run start
(Would be good to include npm install in the README.md steps.)

ERROR: Error during template compile of 'SharedModule' Function calls are not supported in decorators but 'FlexLayoutModule' was called.

Complete log of run:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/Users/Loren/.npm-packages/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build:prod' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild:prod', 'build:prod', 'postbuild:prod' ]
5 info lifecycle [email protected]~prebuild:prod: [email protected]
6 info lifecycle [email protected]~build:prod: [email protected]
7 verbose lifecycle [email protected]~build:prod: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~build:prod: PATH: /Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Library/Sites/ngx-starter-kit/node_modules/.bin:/anaconda3/bin:/Users/Loren/.node/bin:/Users/Loren/.npm-packages/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:/opt/X11/bin
9 verbose lifecycle [email protected]~build:prod: CWD: /Library/Sites/ngx-starter-kit
10 silly lifecycle [email protected]~build:prod: Args: [ '-c', 'ng build -c=production' ]
11 silly lifecycle [email protected]~build:prod: Returned: code: 1  signal: null
12 info lifecycle [email protected]~build:prod: Failed to exec build:prod script
13 verbose stack Error: [email protected] build:prod: `ng build -c=production`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/Users/Loren/.npm-packages/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:947:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:236:5)
14 verbose pkgid [email protected]
15 verbose cwd /Library/Sites/ngx-starter-kit
16 verbose Darwin 17.6.0
17 verbose argv "/usr/local/bin/node" "/Users/Loren/.npm-packages/bin/npm" "run" "build:prod"
18 verbose node v10.0.0
19 verbose npm  v6.1.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] build:prod: `ng build -c=production`
22 error Exit status 1
23 error Failed at the [email protected] build:prod script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

AS a developer I WANT TO have a better Webpack + HMR configuration IN ORDER TO have a better development environment.

WARNING in Circular dependency detected:
libs\auth\src\auth.service.ts -> libs\auth\src\auth.state.ts -> libs\auth\src\auth.service.ts

WARNING in Circular dependency detected:
libs\auth\src\auth.state.ts -> libs\auth\src\auth.service.ts -> libs\auth\src\auth.state.ts

There have been updates to the fortawesome monorepo:

• • The dependency @fortawesome/fontawesome-svg-core was updated from 1.2.19 to 1.2.20.

• The dependency @fortawesome/free-solid-svg-icons was updated from 5.9.0 to 5.10.0.
• The dependency @fortawesome/free-brands-svg-icons was updated from 5.9.0 to 5.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the fortawesome group definition.

fortawesome is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency filepond-plugin-image-preview was updated from 4.1.1 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

filepond-plugin-image-preview is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Please re-publish also 0.0.3 version. We have a dependency on that version because we maintain all the previous version of our software and the latest one (0.0.7) is not compatible with angular 7.2.6.

Anyway consider that removing something from npm is considered a bad practice because people can depend on any version published (https://docs.npmjs.com/cli/unpublish).

Thanks

Originally posted by @GianlucaMaggio in #156 (comment)