Build output caching does not work for `@nrwl/next:build` followed by `@nrwl/next:dev-server`

Expected Behavior

Running the @nrwl/next:build command should cache build outputs, so that @nrwl/next:dev-server does not need to build the app again.

Current Behavior

yarn nx run myapp:build:production
# observe: myapp is compiled

yarn nx run myapp:serve:production
# observe: myapp is compiled *again*

Failure Information (for bugs)

Steps to Reproduce

https://github.com/Yolk-HQ/nx-caching-issue-2429

Context

Please provide any relevant information about your setup:

  @nrwl/angular : Not Found
  @nrwl/cli : 8.12.2
  @nrwl/cypress : 8.12.2
  @nrwl/eslint-plugin-nx : Not Found
  @nrwl/express : Not Found
  @nrwl/jest : 8.12.2
  @nrwl/linter : 8.12.2
  @nrwl/nest : Not Found
  @nrwl/next : 8.12.2
  @nrwl/node : Not Found
  @nrwl/react : 8.12.2
  @nrwl/schematics : Not Found
  @nrwl/tao : 8.12.2
  @nrwl/web : 8.12.2
  @nrwl/workspace : 8.12.2
  typescript : 3.5.3

[vsavkin]

Hi folks! This example shows a “workaround”: https://github.com/nrwl/nx-incremental-large-repo. Basically, you can only cache files written to disk. The example shows how to build libraries (write files to disk), and webpack (for linking and chunking). The example uses Angular but there is really nothing Angular-specific about it.

This isn’t ideal because relinking everything takes time, and isn’t really needed for development.

My plan is to for very large apps only use webpack for prod builds and have a simple dev server that can load compiled libs, concat them, and serve them. Google does it this way (just with closure instead of webpack).

Does it make sense?

[vsavkin]

Closing this issue.

Making this a better-supported use case is one of the priorities for H2 2020.