Skip to content
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
This repository was archived by the owner on Nov 22, 2024. It is now read-only.

Support schematics in @nguniversal/express-engine #968

@vikerman

Description

@vikerman
  • I'm submitting a ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
  • What modules are related to this Issue?
- [ ] aspnetcore-engine
- [ ] common
- [x] express-engine
- [] hapi-engine
- [ ] module-map-ngfactory-loader
  • What is the current behavior?
    Copy and paste code to setup a working node server serving SSR app.

  • What is the expected behavior?
    ng add @nguniversal/express-engine should

  • Add the npm dependencies
  • Create server.ts entry point for the the express engine based Node server
  • Create webpack config to build server.ts
  • (Optionally) Add entries into scripts of package.json with commands to build and run the SSR version of the app
  • (Optionally) Provide ng g transfer-http to setup the HTTP cache transfer module
  • What is the motivation / use case for changing the behavior?
    Make it easier to get started with Angular SSR

(Though we should probably display a warning that this is just a simplified setup and they would want to do something more tuned for production themselves)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions