Stanimira Vlaeva

Hi @kdmakwana43, Does your project have a dependency on `@angular/cli`? The `@nativescript/schematics` package tries to require a utility function from `@schematics/angular`. `@schematics/angular` is a dependency of `@angular/cli`. To fix the...

Hey @tjvantoll! Thanks for the suggestion! The mobile app-wide css file is named `app.css` because the default webpack build is configured to use that name. Unfortunately, there is no easy...

Hey @gummibjorn, probably the issue is caused by invalid typescript configuration. Can you share the contents of the following files? - **tsconfig.json** (the common TS configuration) - **tsconfig.tns.json** (the {N}...

Hi @iMarwan-k, sorry for the delay. Can you post the error that you're getting when running the web build?

Hi @zHaytam, could you answer the following questions to help me understand better your workflow? - Do you download the application from the `NativeScript Playground` and then run it? -...

Hi @RoyiNamir! We're looking into that issue now. I don't have access to the attached files. Can you upload them somewhere else?

We'll consider adding this to the next release. It may be a good idea for the value to be customizable instead of locked down to 4096 as in the typescript...

Hey @progressify, did you register the non-lazy components as routes as well? If the answer is yes - can you share your routing configuration?

@progressify, which NgModule declares the `header-menu` and `footer-menu` components?

@progressify, currently, the components are declared in the root NgModule - AppModule. That's why the lazily loaded module cannot use them. You may have to move these components to a...