Only Use Angular Universal's Server-Side Rendering for Specific Routes

[nestjs]

Only Use Angular Universal's Server-Side Rendering for Specific Routes

[CWSpear]

A few more things I looked into:

Express allows Regular Expressions for their routes. So even tho renderPath is typed as a string for AngularUniversalOptions, if I pass in a RegEx, is will register with Express. This could mean we don't need an explicit white/blacklist. However...

I tried passing in /^\/(?!members).*/--basically all routes except those that start with /members--and that did indeed make it so it only rendered non member routes with SSR... but then it would result in a 404 for /members paths.

There needs to be a fallback that will return templatePath's contents when the renderPath is not matched.

As a workaround for now, I put this high up in my server's main.ts:

export async function bootstrap(): Promise<NestExpressApplication> {
  const expressApp: Express = express();

  expressApp.use(compression());
 
  // this allows us to skip over SSR for members area
  expressApp.get(/^\/members/, (req: Request, res: Response) => {
    const path = join(__dirname, '../client/index.html');
    res.sendFile(path);
  });

  // other code and setting up Nest...
}

It would probably work as a catchall if I registered it last, too with app.get('*', ...) if I combined it with the RegEx renderPath I mentioned above.

It seems like this is something that could be built into this module, maybe?

[fullofcaffeine]

It'd be nice to have selective SSR indeed. Is it something that's planned? At the moment, I have this in my app, but I implemented it myself with React, but I'm considering Angular/Nest for another app.

[kamilmysliwiec]

We don't plan to add more features to this feature as it is supposed to be a tiny wrapper on top of @nguniversal/express-engine. If anyone needs more functionalities, we recommend forking this package and bringing it to the project's codebase.