Contributing section instructions missing webpack step #764

New Issue

fergalmoran · 2025-08-09T17:17:35Z

fergalmoran commented

2025-08-09 17:17:35 +00:00

Originally created by @ferrx on 5/13/2017

From https://github.com/aspnet/JavaScriptServices#contributing

If you're interested in contributing to the various packages, samples, and project templates in this repo, that's great! You can run the code in this repo just by:

Cloning the repo
Running dotnet restore at the repo root dir
Going to whatever sample or template you want to run (for example, cd templates/Angular2Spa)
Restoring NPM dependencies (run npm install)
Launching it (dotnet run)

You can reproduce this error by following the current directions.

After performing these steps, the wwwroot directory is empty (except for a favicon). The step to bundle js/css is never performed. You will get an error when navigating to localhost:5000 with logs showing that the bundled js/css requests are coming back with 404 errors.

Either include a step for dotnet publish which performs the required webpack commands AND npm install, or explicitly include the two webpack commands as steps. I think the difference would be that dotnet publish will set the environment to production whereas it may be in development by default. If going with the former, removing the npm install direction in the contributor notes would be possible.

*Originally created by @ferrx on 5/13/2017* From https://github.com/aspnet/JavaScriptServices#contributing ``` If you're interested in contributing to the various packages, samples, and project templates in this repo, that's great! You can run the code in this repo just by: Cloning the repo Running dotnet restore at the repo root dir Going to whatever sample or template you want to run (for example, cd templates/Angular2Spa) Restoring NPM dependencies (run npm install) Launching it (dotnet run) ``` You can reproduce this error by following the current directions. After performing these steps, the wwwroot directory is empty (except for a favicon). The step to bundle js/css is never performed. You will get an error when navigating to localhost:5000 with logs showing that the bundled js/css requests are coming back with 404 errors. Either include a step for `dotnet publish` which performs the required webpack commands AND npm install, or explicitly include the two webpack commands as steps. I think the difference would be that `dotnet publish` will set the environment to `production` whereas it may be in `development` by default. If going with the former, removing the `npm install` direction in the contributor notes would be possible.

fergalmoran closed this issue

2025-08-09 17:17:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#764