{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/meteor/issues/9875","repository_url":"https://api.github.com/repos/meteor/meteor","labels_url":"https://api.github.com/repos/meteor/meteor/issues/9875/labels{/name}","comments_url":"https://api.github.com/repos/meteor/meteor/issues/9875/comments","events_url":"https://api.github.com/repos/meteor/meteor/issues/9875/events","html_url":"https://github.com/meteor/meteor/issues/9875","id":321774997,"number":9875,"title":"Chrome Node debugger fails to set breakpoints","user":{"login":"brucejo75","id":14342237,"avatar_url":"https://avatars0.githubusercontent.com/u/14342237?v=4","gravatar_id":"","url":"https://api.github.com/users/brucejo75","html_url":"https://github.com/brucejo75","followers_url":"https://api.github.com/users/brucejo75/followers","following_url":"https://api.github.com/users/brucejo75/following{/other_user}","gists_url":"https://api.github.com/users/brucejo75/gists{/gist_id}","starred_url":"https://api.github.com/users/brucejo75/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brucejo75/subscriptions","organizations_url":"https://api.github.com/users/brucejo75/orgs","repos_url":"https://api.github.com/users/brucejo75/repos","events_url":"https://api.github.com/users/brucejo75/events{/privacy}","received_events_url":"https://api.github.com/users/brucejo75/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-10T01:02:38Z","updated_at":"2018-05-10T15:31:10Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I can no longer set breakpoints in my meteor code.  I can put debugger statements in and step through the code, But setting breakpoints no longer works.\r\n\r\nI think this happened after a Chrome update, so it is probably a Chrome issue with Meteor?\r\n\r\nI noticed it started happening when I started seeing this icon in the network tab at the upper left:\r\n\r\n![chrome icon](https://user-images.githubusercontent.com/14342237/39846831-a493b1bc-53b2-11e8-98d5-e571fb3271ca.png)\r\n\r\nMaybe a source map problem?\r\n\r\n### Environment:\r\n- Chrome Version 66.0.3359.139 (Official Build) (64-bit)\r\n- meteor@1.6.1.1\r\n- node 8.11.1\r\n- npm 5.8.0\r\n- Windows 10\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/meteor/meteor/issues/comments/388089829","html_url":"https://github.com/meteor/meteor/issues/9875#issuecomment-388089829","issue_url":"https://api.github.com/repos/meteor/meteor/issues/9875","id":388089829,"user":{"login":"benjamn","id":5750,"avatar_url":"https://avatars0.githubusercontent.com/u/5750?v=4","gravatar_id":"","url":"https://api.github.com/users/benjamn","html_url":"https://github.com/benjamn","followers_url":"https://api.github.com/users/benjamn/followers","following_url":"https://api.github.com/users/benjamn/following{/other_user}","gists_url":"https://api.github.com/users/benjamn/gists{/gist_id}","starred_url":"https://api.github.com/users/benjamn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benjamn/subscriptions","organizations_url":"https://api.github.com/users/benjamn/orgs","repos_url":"https://api.github.com/users/benjamn/repos","events_url":"https://api.github.com/users/benjamn/events{/privacy}","received_events_url":"https://api.github.com/users/benjamn/received_events","type":"User","site_admin":false},"created_at":"2018-05-10T15:31:10Z","updated_at":"2018-05-10T15:31:10Z","author_association":"OWNER","body":"I'm not sure whether this is a Chrome issue or a Node inspector issue, but (thankfully?) I don't think it's a source maps issue, because when I turn off JS source maps, and let the inspector stop on this `debugger` statement (in `server/main.js`), I still can't get the inspector to stop at a breakpoint that I've set on the `console.log` line:\r\n```js\r\nMeteor.startup(() => {\r\n  debugger;\r\n  console.log(module.id);\r\n});\r\n```\r\nThis also seems to imply it's not a fibers issue, since there's certainly no `Fiber.yield` between the `debugger` and the `console.log`, which is good news (i.e., it's not another case of #9275)."}}
{"actor":{"display_login":"benjamn"}}