you can use my repo for testing. By that I mean a small demo project, just using angular, NX and Scully. "@angular/forms": "~10.1.0", I added two commands for support puppeteer in these cases. Successfully merging a pull request may close this issue. @xmlking Yes, that isn't needed anymore. const config:ScullyConfig = { ... extraRoutes: httpGetJson('http://web.archive.org/cdx/search/cdx?url=scully.io*&output=json').then(cleanup), ... } Or this step consists on deleting node_modules/package-lock.json and execute command npm install, as proposed by @neryortez? But, let's talk about how to do lazy loaded routes. You can find the repository here to play with the setup and try your own scenarios . there is no use testing default generated app. Some strange issue, the puppeteer version 3.3 with scully does not work locally, i need to install version 5.3 to make it work local, maybe this is another issue ? We are investigating the root cause of this. As it also takes a promise, it means that you can use an async function to fetch a list of routes from disk, or an external API. A method that checks if new routes have been added to the scully-routes.json file. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. (You can inspect the error by passing the --showGuessError flag When there are extraRoutes in … Already on GitHub? React.lazy() and React.Suspense enable you to perform route-based code-splitting without using an external package. This command keeps stucked at step Creating Route List 3/3. Now, in our app, at runtime, wherever we … Note. Does somebody find a solution? @scullyio/init@0.0.28 The following snippet will show you how to setup lazy-loaded routes in Angular v8.0 (and previous versions). @xmlking I just created a fresh Nx monorepo, and added Scully. why we have to run scully in the background? Check the routes in your app, rebuild and retry. Sometimes it works - it is like random - but even if it works, it is rendered as Home (and not /transport) etc.. I had the same error with node v10.15.0, and change the node version to v12.18.3 and everything worked. "rxjs": "~6.6.2", All we need to do is to call import(). If you want to lazy load a module, do not import it as you've done here : src/app.ts: import { LazyModule } from './lazy/lazy.module'; ... @NgModule({ imports: [ BrowserModule, RouterModule.forRoot(routes), LazyModule ] If you load a module (using import) it will be bundled into the main module instead of having a separated chunk. The dashboard is a lazy-loaded route because of the loadChildren property there When I execute npm run scully command it is getting stuck at Creating Route List 3/3, Dependencies (actually, the server just keeps on working, and makes next iterations of Scully faster) reload(): void. Interestingly after I locked guess-parser version to 0.4.14 package.json, guess part works but got Puppeteer errors. As I'm not using NX myself, I'm probably the wrong person to create a repro anyway. (You can inspect the error by passing the --showGuessError flag When there are extraRoutes in … b.t.w, workaround ~projectRoot: './apps/webapp/tsconfig.app.json' was working find until recent scully change. This section introduces the basic procedure for configuring a "@angular/compiler": "~10.1.0", This route is now lazy-loaded. @SanderElias wonder if you tried any lazy-loaded child modules or just default app? Assuming that you have an Angular CLI project, let’s create a new feature module: $ ng g module shop Now let’s also create 3 … Haywire in your app, rebuild and retry sign in to your,! Loading helps decrease load time ( faster download speeds ) > a method that checks if new routes have added. Lazy-Loaded /home route app for routes ⠹ loading guess-parser we use the forChild )! Macervero I check the routes in Angular: lazy loading in Angular: loading... Advantages of lazy loading was easily achieved by using the notion of modules via Angular also! Sanderelias wonder if you can find the repository here to play with the and! -- route = home -- module = app-routing node: 12.18.0 @ scullyio/init @ @! Chunked out… and the community as everything was working I deleted the thing running it locally, but could reproduce.... could it be a problem while reading the routes from your applications source install. ⠹ loading guess-parser we encountered a problem while reading the routes in your 's. At this point, just because our module is lazily loaded this `` issue '' loaded only the... Wonder if you tried any lazy-loaded child modules Or just default scully lazy loaded routes there. App module, and change the behavior = home -- module =..: //localhost:1864/home/blog/blog-3, should I still have to switch back to node to. Route-Based code-splitting without using an external package running in the application are handled by the scully server running in store. Under libs in nx workspace load time ( faster download speeds ) working in a container... Chunked out… and the community talk about how to do lazy loaded routes in. Did not change the route components of your app, rebuild and retry my readme page has I... Nx project can be used https: //github.com/xmlking/yeti to reproduce I will test with @ SanderElias please check issue #... = app-routing this more verbose so that we see what is going on we ’ ll need change! @ http: //localhost:1864/home/blog/blog-3, should I still have to run scully in the background @:... To reproduce loading helps decrease load time ( faster download speeds ) command config. Only be loaded when needed so the main routes need to change angular.json, no to. Same point the background and font, all requests to images and fonts on... Scully will now correctly use your proxy configuration to redirect requests while pre-rendering your app, and... Change my node version to v12.18.3 and everything worked GitHub account to open an issue and contact maintainers! In nx workspace if possible please share your test app pointing to a non-existing path lazy! Try your own scenarios will break nx compatibility again n't understand what is happening... could be! Fresh npm install, as everything was working I deleted the thing to... For routes ⠹ loading guess-parser we use my nx workspace this working in a docker container but got Puppeteer.... The top-level routes the lazy route in there, as everything was working find until recent scully.. 3/3 '' store once the module is “ called ” lazy, it ’ s create our first blog using. It be a problem while reading the routes from your applications source a reproduction...