igniteui-angular-samples icon indicating copy to clipboard operation
igniteui-angular-samples copied to clipboard

Published 20 hours ago • verified publisher icon IgniteUI

Not able to run angular samples

Open Aleksandyr opened this issue 4 years ago • 1 comments

Description

Not able to run angular samples with simple npm run start command

Assumptions

It may lead to a massive load time because of the enormous amount of defined modules.

Steps to reproduce

  1. Navigate to igniteui-angular-samples repo
  2. try to execute npm run start
  3. The execute process hangs at some point

Result

The samples are not run

Expected result

The samples should be run locally

Aleksandyr avatar Sep 23 '20 11:09 Aleksandyr

The problem comes from the big volume of components that we have in the projects.

A solution for this problem will be a process that will load the sample application:

  • [ ] based on designated modules
  • [ ] based on designated components
  • [ ] based on designated modules and components

For example

npm run start --modules=data-entries, lists --components=grid--grid-sorting, tree-grid--grid-sorting

And this must load the sample browser with the components defined in the data-entries and lists modules, the grid sorting compoent and the tree grids sorting component

HristoP96 avatar Oct 08 '20 13:10 HristoP96