Closed mspace closed 7 months ago
Solved it by updating launch.json
to this:
"configurations": [
{
"name": "Attach to Chrome",
"port": 9222,
"request": "attach",
"type": "chrome",
"webRoot": "${workspaceFolder}",
"sourceMaps": true,
"sourceMapPathOverrides": {
"*": "${webRoot}/*"
}
},
Page is server from /dashboard/spa
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
Command
build
Is this a regression?
The previous version in which this bug was not present was
16.0.1
Description
We have a task to upgrade our existing angular application from angular 16 to 17.
We followed https://update.angular.io/?l=3&v=16.0-17.0
ng update @angular/core@17 @angular/cli@17
Our angular.json looks like this:
From visual studio code, we navigate to Run and Debug section and attach to chrome. Launch.json file content
Because we have set outputPath, the build application is copied here:
Debugging works from http://localhost:4200, if we ran ng serve command, but we are serving our application from URL:
https://example.com/dashboard/spa/user-management
(example.com points to localhost, defined in host file of Windows)We are using next command for build (defined in package.json):
ng build --watch --base-href /dashboard/spa/ --output-hashing all
Debugging doesn't work
Minimal Reproduction
Exception or Error
No response
Your Environment
Anything else relevant?
No response