akveo / akveo/ngx-admin-bundle-support
errors npm run build:prod by default
- Dominant language
- TypeScript
- Stars
- 56
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
after running the command npm run build:prod on version 3.1.2(even the previous version) we are get three errors
the first one is the following error :
ERROR in : Cannot determine the module for class SampleLayoutComponent in
(project name)/src/app/@theme/layouts/sample/sample.layout.ts! Add SampleLayoutComponent to the NgModule to fix it.
Cannot determine the module for class EvaIconsPipe in
(project name)/src/app/@theme/pipes/eva-icons.pipe.ts! Add EvaIconsPipe to the NgModule to fix it.
Cannot determine the module for class TeamComponent in
(project name)/src/app/pages/dashboard/team/team.component.ts! Add TeamComponent to the NgModule to fix it.
After adding and fixing these errors then the next error :
SampleLayoutComponent, EvaIconsPipe to theme.modules.ts and TeamComponent to dashboard.modules.ts then
second round of errors start they are from the teamcomponent
ERROR in Module build failed (from ./node_modules/sass-loader/lib/loader.js):
undefined
^
Argument `$color` of `rgba($color, $alpha)` must be a color
in(project location)\src\app\pages\dashboard\team\team.component.scss (line 29, column 32)
this gets resolved by commenting out line no 29 from the team.component.scss
third error is
ERROR in : Can't bind to 'position' since it isn't a known property of 'ngx-header'.
1. If 'ngx-header' is an Angular component and it has 'position' input, then verify that it is part of this module.
2. If 'ngx-header' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component. ("ter]="layout.id === 'center-column'" windowMode>
][position]="sidebar.id === 'start' ? 'normal': 'inverse'">
")
: 'ngx-theme-settings' is not a known element:
1. If 'ngx-theme-settings' is an Angular component, then verify that it is part of this module.
2. If 'ngx-theme-settings' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message. ("
fixed
[end]="sidebar.id !== 'end'">
[ERROR ->]
")
: 'ngx-toggle-settings-button' is not a known element:
1. If 'ngx-toggle-settings-button' is an Angular component, then verify that it is part of this module.
2. If 'ngx-toggle-settings-button' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message. ("
[ERROR ->]
")
so to solve this we need to
comment out line number 27 from sample.layout.ts
line number 58
and finally line number 61
The point of this issue is so that other can solve this problems fast ,
also for the developers of the bundle to test the code for build:prod in the future release of the bundle before release
apart from the errors there are multiple number of warnings like
WARNING: Nebular Theme: `nb-theme()` cannot find value for key `sidebar-header-gap` for theme `dark`
on line 59 of node_modules/@nebular/theme/styles/core/theming/_get-value.scss, in function `nb-theme`
from line 56 of stdin, in mixin `@content`
from line 116 of node_modules/@nebular/theme/styles/core/theming/_install.scss, in mixin `@content`
from line 97 of node_modules/@nebular/theme/styles/core/theming/_install.scss, in mixin `nb-install-component-with-scss-vars`
from line 115 of node_modules/@nebular/theme/styles/core/theming/_install.scss, in mixin `nb-install-component`
from line 11 of stdin
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.