GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Easier way to provide disableConsoleIntercept to ng test with vitest · Issue #32726 · angular/angular-cli Open Labels area: @angular/cligemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini DescriptionCommandtest DescriptionVitest by default captures the console output, which reduces the ways available to debug tests. However, there is no direct equivalent option on Attempting to run Attempting to run Instead it seems like you would have to create a custom vitest configuration, with several other properties, and then provide that in angular.json which is rather heavy handed for simple one-time debugging. Describe the solution you'd likeSimple forwarding of arguments Describe alternatives you've considered
Activity
MetadataMetadataAssigneesLabelsarea: @angular/cligemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini TypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |