ClarityModule is not an NgModule #220
Comments
|
Hi @BugsyFTW. Does this happen when you use Angular-CLI version of the clarity-seed? cc: @Shijir. It looks like an issue being raised over here: angular/angular-cli#3426 |
|
Hi @adityarb88. I'm the lead on the Angular-CLI project. Basically this error likely happens because you did not publish To generate these files, follow these steps: https://angular.io/docs/ts/latest/cookbook/aot-compiler.html (basically running Cheers! |
Fixes vmware-archive#62, vmware-archive#220. Here's a refactoring of our project to support AoT compilation. Some notable changes are: - Code changes to make our components AoT compatible: - make all inputs and outputs public - removed usage of our animation functions in components; the code is still there but not being used; for now the animation is hard-coded into the components (the ngc compiler couldn't statically analyze the functions passed into the component decorator; filed an issue to investigate separately: vmware-archive#273) - other minor edits to get ngc compiler to compile - Moved demo components to under app (we previously had it nested under each component which required a lot of renaming and shifting things around to produce the npm packages) - Reduced some of the "automagic" in our build flow: - renamed `src/clarity` to `src/clarity-angular` - no more auto re-exporting in `src/clarity-angular/index.ts` in favor of explicitly adding export statements for new components - Now in dev mode, we no longer inline the templates for demo components (had to re-add module.id in most components to support this). this allows for the typescript compilation to not depend on sass compilation on watch tasks. Clarity components will always be inlined, even in dev mode. - Added build step to compile our components with ngc compiler. Our clarity-angular npm package will change to include es2015 compiled code (for AoT compilation) along with `metadata.json` files, original source code in `src` folder (as before), and `clarity-angular.min.js` in register format (as before). We are now producing an additional `clarity-angular.umd.js` file. Apps using systemjs will need to update their config to use Clarity components after 0.8.0. - No more demo npm package. Signed-off-by: Jeeyun Lim <jeeyun.lim@gmail.com>
|
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed issues after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
Select one ... (check one with "x")
Expected behavior
When using ng serve it should compile the app.
Actual behavior
When i type ng serve it says that the ClarityModule is not an NgModule, i've followed correctly the tutorial on installation.
The text was updated successfully, but these errors were encountered: