Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

assets/scully-routes.json is NOT generated while using baseFilter and routeFilter

See original GitHub issue

🐞 Bug report

Description

While running ‘npx scully --routeFilter’, scully-routes.json is NOT generated, which leads to “TimeoutError: Navigation timeout of 30000 ms exceeded we will retry rendering this page up to 3 times”.

I have noticed, if scully-routes.json is missing, this issue arises. If the scully-routes.json is present and i run the above command it works perfectly.

I even tried ‘npx scully --scanRoutes --routeFilter’.

The above step is missing which running with routeFilter/baseFilter

🔬 Minimal Reproduction

💻Your Environment

Angular Version:




Angular CLI: 13.0.4
Node: 14.16.0
Package Manager: npm 6.14.11
OS: win32 x64

Angular: 13.0.3
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1300.4
@angular-devkit/build-angular   13.0.4
@angular-devkit/core            13.0.4
@angular-devkit/schematics      13.0.4
@angular/cdk                    12.2.13
@angular/cli                    13.0.4
@schematics/angular             13.0.4
rxjs                            6.6.7
typescript                      4.4.4

Scully Version:




  "@scullyio/init": "^1.1.4",
  "@scullyio/ng-lib": "^1.0.0",
  "@scullyio/scully": "^1.1.1",

🔥 Exception or Error




<html>
<body>


Puppeteer error while rendering "/newsroom/canalys-global-smartphone-market-Q4-2021" TimeoutError: Navigation timeout of 30000 ms exceeded  we will retry rendering this page up to 3 times.
--
265 | Puppeteer error while rendering "/newsroom/global-pc-market-Q4-2021" TimeoutError: Navigation timeout of 30000 ms exceeded  we will retry rendering this page up to 3 times.


</body>
</html>

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

2reactions

Amith278commented, Jan 30, 2022

@SanderElias

Use case is : Generate static page for only new dynamic path. I don’t want to generate static pages for default paths every build. So only for blog/:id

If a new blog/:id is comes in and it’s not present in route-list, the build timesout.

Any work around?

0reactions

WhyINeedToFillUsernamecommented, Jul 12, 2022

Hi, I would like to add my reasoning to this question.

My use-case and expectations are: have a list of events on the main page (route “/”) and their details on separate pages (routes /detail/:id). Run scully build to generate first version of sites, ship it to CDN. Then, when some new event occurs, generate only page for that. I expect that should be done by using npx scully --baseFilter="/detail/newEventId".

This works (= only the new page is generated) but scully doesn’t add this new route to the list of handled routes in the scully-routes.json (I would expect the new route will be added there, or at least to have some option to add it there with a switch). Since the baseFilter switch doesn’t do this, I tried it with the scanRoutes npx scully --scanRoutes --baseFilter="/detail/*", but it also didn’t add it to the list.

Am I missing something? Is there another way to do this? Or should we handle this use case some other way?