Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newly created project doesn't work with docker and debug in Chrome extension in VSCode - sourcemap problem #7076

Closed
erlloyd opened this issue Jul 21, 2017 · 2 comments

Comments

@erlloyd
Copy link

erlloyd commented Jul 21, 2017

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

  _                      _                 ____ _     ___
 / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
/ ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
             |___/
@angular/cli: 1.2.2
node: 6.10.3
os: linux x64
@angular/animations: 4.3.1
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/router: 4.3.1
@angular/cli: 1.2.2
@angular/compiler-cli: 4.3.1
@angular/language-service: 4.3.1

Repro steps.

NOTE: This workflow works perfectly fine using @angular/cli 1.1.0. It breaks when using 1.1.1 and remains broken in the current version.

I have a sample repo setup here: https://github.com/erlloyd/ng-cli-vscode-error-sample

  1. Make sure you have docker installed
  2. Clone the above repo
  3. In the repo directory, run docker-compose build
  4. Run docker-compose up
  5. Make sure you have VSCode and the 'Debugger for Chrome' extension installed (https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome)
  6. Open the project in VSCode. Set a breakpoint in VSCode. I use line 12 of app.component.ts
  7. Launch the debugger config in VSCode. It should be called 'launch sample against localhost'

EXPECTED: the breakpoint becomes active (red) after the page loads (note that it isn't necessarily going to hit the breakpoint due to startup race conditions)

ACTUAL: From ng versions 1.1.1 onward, the breakpoint remains grey with the error: Breakpoint ignored because generated code not found (source map problem?).

Mention any other details that might be useful.

Note that this only occurs if the project is run through Docker. If I run the project on the local machine the breakpoints are hit without an issue. Could something have changed about where/how the sourcemaps are generated and stored?

Please let me know if you want any additional information and / or testing.

@erlloyd erlloyd changed the title Newly created project doesn't work with docker and debug in Chrome extension is VSCode - sourcemap problem Newly created project doesn't work with docker and debug in Chrome extension in VSCode - sourcemap problem Jul 21, 2017
@filipesilva
Copy link
Contributor

Duplicate of #6583, should be fixed in newer versions.

@filipesilva filipesilva marked this as a duplicate of #6583 Jul 31, 2017
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants