Sam4Sc - a migration assistant for Angular to SCAM (Single Angular Component Modules) and Standalone Components

The tool report 17 SCAM components

Skipping 17 SCAM component(s):

but I havent set any components as SCAM components yet

also I get skipping 19 undeclared components but these components are in modules

after fixing the imports, removing index.ts files and cleaning up my application I now get

RangeError: Maximum call stack size exceeded at Observable._trySubscribe (/workspace/xxx/node_modules/rxjs/internal/Observable.js:55:25)

CLI was 13.2.5 and now upgrade to 14.0 next 6 and still same issue

also updated rxjs6 to 7

{
                path: 'user',
                loadChildren: () =>
                    import(/* webpackChunkName: "user" */ '../core/modules/user/user.module').then((m) => m.UserModule),
                data: { preload: false, delay: false },
            },

how do we deal with lazy loaded routes?

RFC says the following is possible, do we need to add this in?

RouterModule.forRoot([
  {
      path: '/some/route/to/standalone', 
      loadComponent: () => import('./standalone.cmp').then(m => m.StandaloneRouteCmp)
  },
  {
      path: '/some/route/to/standalone/with/default/export', 
      loadComponent: () => import('./default-standalone.cmp')
  }
]);

I now have 350 files that I need to go in set imports for

can't find anything on vscode for importing from inline html, did try IntelliJ IDE but I prefer vscode, its going to be a repetive and boring task however we could auto import based on inline html

e.g if tag <mat-card found then import MatCardModule if [[formGroup] found then import ReactiveFormsModule

and so on

users could define their own matching criteria

it wouldnt sort every component but would help the repetive task

if you have index.ts files that has an export then tool fails

import {        
    XXXComponent,
} from './index';
``

the tool fails to find the component

if you use https://github.com/ngneat/until-destroy

and setup components as

`` @UntilDestroy()

@Component({ ``

then you get a couldn't find component, I guess the checking is assuming nothing is sitting above @Component

if an app uses absolute paths i.e by configuring tsconfig to use a base url then we get errors as

cannot find component AppComponent in module /src/app/app.module.ts

on

import { AppComponent } from 'app/app.component';

we could go in and change all these but the tool should really accomodate this as apps may contain a mixture of relatives and absolute. changing my imports to continue testing the tool

if components are declared as follows

const components = [
    xxTablesPageComponent,
    xxFormComponent,
    
];
@NgModule({
    imports: [CommonModule, SharedModule, InpatientSharedModule],
    exports: [components],
    declarations: [components],
})

then we get Cannot find components declared in NgModule, I have swapped them out to continue testing the tool but we should accomodate for such scenarios