npm start fails on Default angular Template
Manmohabe opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
Running npm start fails on the default asp.net core angular template, check below.
dotnet run also does not start the angular proxy server
node --v 16.15.1
npm --v 7.5.6
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
6.0.201
Anything else?
No response
@Manmohabe thanks for contacting us.
Can you indicate what node version you are using?
Hi @Manmohabe. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Node and npm version are below. My Machine is running windows 10
@Manmohabe are there any files in %APPDATA%\ASP.NET\https?
Can you include the logs as described in the error message?
Hi @Manmohabe. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
@javiercn
I have data in the the https folder, check below.
The logs are as follows
[error] Error: error:0909006C:PEM routines:get_name:no start line
at node:internal/tls/secure-context:65:13
at Array.forEach ()
at setCerts (node:internal/tls/secure-context:63:3)
at configSecureContext (node:internal/tls/secure-context:152:5)
at Object.createSecureContext (node:_tls_common:117:3)
at Server.setSecureContext (node:_tls_wrap:1346:27)
at Server (node:_tls_wrap:1205:8)
at new Server (node:https:69:3)
at Object.createServer (node:https:105:10)
at Server.createServer (D:\ntera\FASCompany\SparkhubSoftware\TestUI\ClientApp\node_modules\webpack-dev-server\lib\Server.js:2403:57)
Running the below command seems to work
My project is not in the C directory, can this be the problem?
@Manmohabe can you quote the paths in the package.json file?
Hi @javiercn Quoting the path does not solve this issue
"start:windows": "ng serve --port 44464 --ssl --ssl-cert C:\Users\USER\AppData\ASP.NET\https\%npm_package_name%.pem --ssl-key C:\Users\USER\AppData\ASP.NET\https\%npm_package_name%.key"
@Manmohabe thanks for the additional information. We'll have to try and reproduce this on our end
Thanks for contacting us.
We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.