Mark SPA Proxy as not for publication in SPA templates

[amcasey]

Mark SPA Proxy as not for publication in SPA templates

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Summary of the changes (Less than 80 chars)

Mark SPA Proxy as not for publication in the SPA templates

Description

The SPA Proxy is only useful at development time, not in production, so it should be included in the output folder, but should not be published.

Fixes #46036

[dougbu]

This looks like the correct change but I'm not sure it'll work w/o checking the fix into dotnet/spa-templates then (separately) updating the submodule to use that new commit. My best guess is committing this change will not change what's visible in the other repo and that's not good.

[wtgodbe]

He did that here: dotnet/spa-templates#117. As long as this commit is updating the submodule commit to use that one (I can't tell via the github UI), we're good

[amcasey]

This looks like the correct change but I'm not sure it'll work w/o checking the fix into dotnet/spa-templates then (separately) updating the submodule to use that new commit. My best guess is committing this change will not change what's visible in the other repo and that's not good.

The GH UI is displaying things confusingly, but this change is (as @wtgodbe mentioned) just a submodule update to pull in dotnet/spa-templates#117.