dotnet / dotnet/aspnetcore

SpaProxy should not inject middleware with ASPNETCORE_HOSTINGSTARTUPASSEMBLIES

Open
#46,780 3 comments 2 reactions 0 assignees View on GitHub
area-ui-rendering feature-spa
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

I wanted to post in this bug: https://github.com/dotnet/aspnetcore/issues/45130

But it's been locked to me even though I created it. I was asked there by @javiercn as to what problems I run into with the new ASP.NET SPA approach that puts express.js in front of the ASP.NET server, so for the record I'd like to note two things:

1) I like to be able to modify the index.html page in the pipeline so that I can inject JavaScript into the page to provide configuration information from the ASP.NET app
2) I like to be able to selectively inject JS into the index.html page so that I can eg. only inject Google Analytics on the production server.

It seems to me that unless ASP.NET has ultimate control over serving the index.html page, I'm unable to do that with the new mechanism.

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

_No response_

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.