Can't find routes that are spread into the Route config

I have a fresh Angular application, with a routes.ts file and the following content:

export const routes: Routes = [
	{
		path: '',
		component: SiteFrameComponent,
		children: [
			{
				path: 'a',
				loadChildren: () => ...
			},
			{
				path: 'b',
				loadChildren: () => ...
			},
			{
				path: '404',
				component: NotFoundComponent,
			},
		],
	},
	{ path: '**', redirectTo: '/404' },
];

This is then imported in the AppModule into RouterModule.forRoot(routes)

This is pretty straightforward and common, and it works perfectly.

However, as soon as I want to move out some routes to a separate variable, and then spread it back into the config, scully can’t follow:

export const mainPages: Routes = [
	{
		path: 'a',
		loadChildren: () => ...,
	},
	{
		path: 'b',
		loadChildren: () => ...,
	},
];

export const routes: Routes = [
	{
		path: '',
		component: SiteFrameComponent,
		children: [
			...mainPages,
			{
				path: '404',
				component: NotFoundComponent,
			},
		],
	},
	{ path: '**', redirectTo: '/404' },
];

I separated some routes because I imported it elsewhere to render out links to these routes with an ngFor. So I would get new links by just adding a new route.

I get the following error from guess:

Finding all routes in application.
traversing app for routes
⠸ Loading guess-parser TypeError: Cannot read property 'values' of undefined
    at getObjectProp (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:444:32)
    at Object.exports.readLoadChildren (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:471:16)
    at Object.exports.getLazyEntryPoints (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:400:26)
    at collectEntryPoints (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:921:30)
    at Array.forEach (<anonymous>)
    at collectEntryPoints (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:925:31)
    at visitTopLevelRoutes (<project-folder>/node_modules/guess-parser/dist/guess-parser/index.js:909:13)
    at visitNodes (<project-folder>/node_modules/typescript/lib/typescript.js:27858:30)
    at Object.forEachChild (<project-folder>/node_modules/typescript/lib/typescript.js:28032:24)
    at NodeObject.forEachChild (<project-folder>/node_modules/typescript/lib/typescript.js:146142:23)

Versions:

	"@angular/core": "11.2.12",
	"@scullyio/ng-lib": "^1.1.1",
	"@scullyio/scully": "^1.1.1",

[SanderElias]

@mgechev The question of @AlexAegis was: Why does this work:

export const mainPages: Routes = [
	{path: 'a',  loadChildren: ...	},
	{path: 'blog', loadChildren: ...	},
];

const otherPages: Routes = [
	{path: '404',  component: NotFoundComponent },
];

export const routes: Routes = [
	{
		path: '',
		component: SiteFrameComponent,
		children: mainPages.concat(otherPages),
	},
	{ path: '**', redirectTo: '/404' },
];

while this doesn’'t:

export const mainPages: Routes = [
	{path: 'a',  loadChildren: ...	},
	{path: 'blog', loadChildren: ...	},
];

const otherPages: Routes = [
	{path: '404',  component: NotFoundComponent },
];

export const routes: Routes = [
	{
		path: '',
		component: SiteFrameComponent,
		children: [...mainPages, ...otherPages, {path:'xxx', component: yyy}],
	},
	{ path: '**', redirectTo: '/404' },
];

Both of them seem to be statically analyzable?

[SanderElias]

given the answer from @mgechev

We can’t know what’s in the user’s localStorage. To simplify the parsing algorithm, we’re also not interpreting expressions in route definitions. There is nothing actionable left in here, so I’m going to close this