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.

Refresh throws 404 when using @nrwl/web:file-server

See original GitHub issue

Current Behavior

When using @nrwl/web:file-server I get a 404 on browser refresh for any route other than the root. This does not happen when using @angular-devkit/build-angular:dev-server

        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "test-app:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "test-app:build:production"
            }
          }
        },
        "serve-nx": {
          "builder": "@nrwl/web:file-server",
          "options": {
            "buildTarget": "test-app:build",
            "browserTarget": "test-app:build",
            "withDeps": true,
            "parallel": true
          },
          "configurations": {
            "production": {
              "buildTarget": "test-app:build:production",
              "browserTarget": "test-app:build:production"
            }
          }
        },

Issue Analytics

State:
Created 2 years ago
Reactions:9
Comments:10 (1 by maintainers)

Top GitHub Comments

2reactions

Maximaximumcommented, Apr 12, 2021

This is quite an annoying bug. One of the main reasons that made me decide to migrate to Nx was to speed up the builds. Unfortunately, computational caching is not enabled by default, so I had to spend almost a day to find out how to turn it on.

And now I realize that the feature is completely unusable due to this bug.

I hope this will be fixed sooner than the majority of bugs at angular 😃

0reactions

Maximaximumcommented, Dec 28, 2021

I believe this issue should not be closed unless it’s fixed. Everyone is just using a workaround, as far as I understand