René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Chrome/karma is started before the webpack dev server is ready to serve","articleBody":"\u003c!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅\r\n\r\nOh hi there! 😄\r\n\r\nTo expedite issue processing please search open and closed issues before submitting a new one.\r\nExisting issues often contain information about workarounds, resolution, or progress updates.\r\n\r\n🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅--\u003e\r\n\r\n# 🐞 Bug report\r\n\r\n### Command (mark with an `x`)\r\n\r\n\u003c!-- Can you pin-point the command or commands that are effected by this bug? --\u003e\r\n\u003c!-- ✍️edit: --\u003e\r\n\r\n- [ ] new\r\n- [ ] build\r\n- [ ] serve\r\n- [x] test\r\n- [ ] e2e\r\n- [ ] generate\r\n- [ ] add\r\n- [ ] update\r\n- [ ] lint\r\n- [ ] extract-i18n\r\n- [ ] run\r\n- [ ] config\r\n- [ ] help\r\n- [ ] version\r\n- [ ] doc\r\n\r\n### Is this a regression?\r\n\r\n\u003c!-- Did this behavior use to work in the previous version? --\u003e\r\n\u003c!-- ✍️--\u003e Yes, the previous version in which this bug was not present was: ....\r\n\r\nNo, AFAIK, this has always been present\r\n\r\n### Description\r\n\r\n\u003c!-- ✍️--\u003e A clear and concise description of the problem...\r\n\r\nThere is this issue in Karma: https://github.com/karma-runner/karma/issues/3745\r\n\r\nWhat happens is that Angular CLI is starting karma and the webpack dev server at the same time. On large Angular projects, like ours, Angular + webpack is very slow (1-2 minutes to start `ng serve` for example, separate issue we really need to address somehow). \r\n\r\nWhat seems to occur is that chrome (or ChromeHeadless) gives up trying to load the page (it would see the problem that the server is not responding). Karma then kills the browser and restarts it (triggering issue https://github.com/karma-runner/karma/issues/3745). Eventually the webpack dev server starts responding, and the tests run. Once the tests complete, the coverage report (and potentially other reporters) fail to write their reports.\r\n\r\nWhile there is a bug in Karma that needs to be fixed, it does not seem to make sense to start the test framework until the webpack dev server is ready to serve the application. When it is ready, we see the `Browser application bundle generation complete` printed to the terminal.\r\n\r\nIdeally karma would be started after a 200 HTTP response could be obtained from the webpack dev server\r\n\r\n## 🔬 Minimal Reproduction\r\n\r\n\u003c!--\r\nSimple steps to reproduce this bug.\r\n\r\nPlease include: commands run (including args), packages added, related code changes.\r\n\r\nIf reproduction steps are not enough for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.\r\nA good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem.\r\nShare the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.\r\n\r\nIssues that don't have enough info and can't be reproduced will be closed.\r\n\r\nYou can read more about issue submission guidelines here: https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-submitting-an-issue\r\n--\u003e\r\n\r\nOnly thing that is required is to run `ng test` on an Angular project. The problem to reproduce is that the application has to have enough code to cause webpack dev server to be too slow to start before chrome gives up loading the page.\r\n\r\n## 🔥 Exception or Error\r\n\r\n\u003cpre\u003e\u003ccode\u003e\r\n\u003c!-- If the issue is accompanied by an exception or an error, please share it below: --\u003e\r\n\u003c!-- ✍️--\u003e\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\r\n\r\n## 🌍 Your Environment\r\n\r\n\u003cpre\u003e\u003ccode\u003e\r\n\u003c!-- run `ng version` and paste output below --\u003e\r\n\u003c!-- ✍️--\u003e\r\nAngular CLI: 13.1.2\r\nNode: 14.17.1\r\nPackage Manager: npm 6.14.13\r\nOS: darwin x64\r\n\r\nAngular: 13.1.1\r\n... animations, common, compiler, compiler-cli, core, forms\r\n... language-service, platform-browser, platform-browser-dynamic\r\n... router\r\n\r\nPackage                         Version\r\n---------------------------------------------------------\r\n@angular-devkit/architect       0.1301.2\r\n@angular-devkit/build-angular   13.1.2\r\n@angular-devkit/core            13.1.2\r\n@angular-devkit/schematics      13.1.2\r\n@angular/cli                    13.1.2\r\n@ngtools/webpack                13.1.2\r\n@schematics/angular             13.1.2\r\nng-packagr                      13.1.2\r\nrxjs                            6.6.7\r\ntypescript                      4.5.4\r\nwebpack                         5.65.0\r\n\u003c/code\u003e\u003c/pre\u003e\r\n\r\n**Anything else relevant?**\r\n\r\n\u003c!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. --\u003e\r\n\r\n\u003c!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. --\u003e\r\n","author":{"url":"https://github.com/arobinson","@type":"Person","name":"arobinson"},"datePublished":"2022-01-12T23:18:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/22495/angular-cli/issues/22495"}