Meta tags:
description= Command test Is this a regression? Yes, this behavior used to work in the previous version The previous version in which this bug was not present was vitest@4.0.8 Description I m not sure if this issue is an issue with Vitest, or the Ang...;
Headings (most frequently used words):
error, navigation, commented, on, mar, 2026, issue, import, app, the, description, metadata, footer, this, was, csvn, 27, vitest, coverage, vite, analysis, pre, transform, failed, to, resolve, util, from, src, ts, does, file, exist, 32891, menu, repository, activity, actions, command, is, regression, previous, version, in, which, bug, not, present, minimal, reproduction, exception, or, your, environment, anything, else, relevant, emilycarter6561, byte, 28, assignees, labels, type, projects, milestone, relationships, development,
Text of the page (most frequently used words):
angular (39), the (25), app (23), issue (22), vitest (18), github (17), and (16), import (16), this (14), cli (14), #coverage (14), build (13), util (13), from (13), that (12), 2026 (11), mar (10), triaged (9), gemini (9), src (9), not (8), actions (8), label (8), for (8), with (8), file (8), error (8), has (7), you (6), noting (6), been (6), csvn (6), 32891 (6), paths (6), vite (6), security (5), copilot (5), area (5), test (5), sign (5), json (5), resolve (5), does (5), failed (5), browser (5), your (5), pre (5), analysis (5), greet (5), code (5), like (4), package (4), more (4), version (4), transform (4), exist (4), add (4), support (4), can (3), navigation (3), open (3), projects (3), unit (3), comment (3), related (3), are (3), path (3), using (3), imports (3), commented (3), tsconfig (3), fixes (3), core (3), errors (3), shared (3), signal (3), export (3), tests (3), new (3), source (3), copy (3), link (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), reload (3), developers (3), changelog (3), customer (3), enterprise (3), grade (3), features (3), all (3), community (2), status (2), footer (2), pull (2), requests (2), development (2), none (2), milestone (2), type (2), labels (2), one (2), metadata (2), have (2), added (2), note (2), likely (2), suggests (2), email (2), notifications (2), unsubscribe (2), because (2), message (2), how (2), workaround (2), seems (2), emilycarter6561 (2), byte (2), author (2), contributor (2), downgrading (2), use (2), files (2), but (2), npm (2), compiler (2), platform (2), router (2), alias (2), which (2), project (2), repro (2), class (2), title (2), npx (2), browsers (2), include (2), config (2), playwright (2), chunk (2), maps (2), when (2), used (2), description (2), previous (2), was (2), work (2), insights (2), 196 (2), repository (2), signed (2), universe (2), training (2), integrations (2), stories (2), center (2), documentation (2), learn (2), business (2), products (2), secret (2), perform, action, time, share, personal, information, manage, cookies, contact, docs, privacy, terms, inc, branches, yet, relationships, assigned, assignees, already, account, join, conversation, free, removed, alan, agius4, fri, christian, svensson, wrote, left, reply, directly, view, email_source, email_token, b7z2x6coqmkf2yy5ekfnjul4s4g5xa5cnfsnuabfm5uwiorpf5tws5bnnb2wel2jonzxkzkdn5ww2zlooqxtimjugu4tmmrxge32m4tfmfzw63vkon2we43dojuwezleuvsxmzlooswgm33porsxex3dnruwg2y, issuecomment, 4145962717, receiving, subscribed, thread, https, com, auth, b7z2x6dbab62vytqqaj4jo34s4g5xavcnfsm6aaaaacxcuthaovhi2dsmvqwix3lmv43oslton2wkq3pnvwwk3tuhm2dcnbvhe3denzrg4, thanks, details, looks, might, change, affects, aliases, handled, good, temporary, fix, hopefully, proper, solution, implemented, soon, appreciate, heads, via, scripts, other, than, same, robot, activity, seem, specific, ubuntu, locally, windows, anything, else, relevant, tried, several, versions, including, both, node, unsupported, manager, operating, system, win32, x64, installed, requested, common, forms, rxjs, typescript, environment, there, logged, every, uses, our, most, them, client, plugin, users, foo, component, routeroutlet, let, exception, watch, chromium, run, readonly, protected, make, value, compileroptions, hello, const, ng21, style, css, ssr, init, install, packages, minimal, reproduction, coverageinclude, creates, sourcemap, eslint, requirements, results, during, generation, crash, come, dev, server, transforming, original, referenced, property, running, these, will, tries, read, requirement, exists, steps, sure, integration, put, here, idea, reproduce, without, moment, bug, present, yes, behavior, regression, command, body, opened, items, issues, dismiss, alert, switched, accounts, out, appearance, settings, search, pricing, event, talks, workshops, what, next, partners, about, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, ons, trust, why, evaluate, see, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, latest, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, environments, codespaces, enforcement, automation, ship, coding, agent, tasks, automated, hosting, review, collaboration, menu, skip, content,
Text of the page (random words):
vitest coverage issue vite import analysis error pre transform error failed to resolve import util from src app app ts does the file exist issue 32891 angular angular cli github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message angular angular cli repository navigation code issues 196 196 pull requests 19 19 actions security and quality 8 8 insights more items vitest coverage issue vite import analysis error pre transform error failed to resolve import util from src app app ts does the file exist 32891 new issue copy link new issue copy link open open vitest coverage issue vite import analysis error pre transform error failed to resolve import util from src app app ts does the file exist 32891 copy link labels angular build unit test area angular build gemini triaged label noting that an issue has been triaged by gemini label noting that an issue has been triaged by gemini description csvn opened on mar 27 2026 issue body actions command test is this a regression yes this behavior used to work in the previous version the previous version in which this bug was not present was vitest 4 0 8 description i m not sure if this issue is an issue with vitest or the angular cli integration with vitest i put the issue here because i have no idea how to reproduce this issue without angular at the moment the issue is that when using tsconfig json property paths and running browser tests with coverage these paths will not used when vitest tries to read coverage from source maps the requirement seems to be that a shared chunk exists import app in the repro steps this results in errors during coverage generation but tests do not crash the errors come from vite s dev server pre transforming original ts files referenced in source maps requirements using paths in tsconfig json angular cli eslint creates a shared chunk that has the paths in it s sourcemap vitest with browsers coverage coverageinclude vitest v4 1 0 minimal reproduction init angular project install vitest coverage browser packages npx angular cli 21 1 5 new ng21 1 5 s t style css no ssr ai config none npm i e d vitest 4 1 0 vitest browser playwright 4 1 0 vitest coverage v8 4 1 0 playwright add src app util ts file export const greet hello add a path alias to util file compileroptions paths util src app util ts make app app ts use value from util ts import greet from util export class app protected readonly title signal greet add import to app ts from app config ts import app run tests with browser coverage coverage include npx ng test no watch browsers chromium coverage coverage include src app ts exception or error there s logged errors for every file that uses the path alias which in our project is most of them e g import shared from core 00 02 12 vite client pre transform error failed to resolve import util from src app app ts does the file exist plugin vite import analysis file c users foo repro src app app ts 3 22 11 import component signal from angular core 12 import routeroutlet from angular router 13 import greet from util 14 export let app class 15 title signal greet your environment i ve tried with angular build angular cli at several versions including 21 1 x and 21 2 x downgrading vitest to 4 0 8 fixes the issue but vitest 4 1 0 and 4 1 2 both failed angular cli 21 2 5 angular 21 2 6 node js 25 8 2 unsupported package manager npm 11 11 1 operating system win32 x64 package installed version requested version angular build 21 2 5 21 1 5 angular cli 21 2 5 21 1 5 angular common 21 2 6 21 1 0 angular compiler 21 2 6 21 1 0 angular compiler cli 21 2 6 21 1 0 angular core 21 2 6 21 1 0 angular forms 21 2 6 21 1 0 angular platform browser 21 2 6 21 1 0 angular router 21 2 6 21 1 0 rxjs 7 8 2 7 8 0 typescript 5 9 3 5 9 2 vitest 4 1 0 4 1 0 anything else relevant does not seem to be os specific the issue is on github actions on ubuntu and locally on windows activity angular robot added area angular cli gemini triaged label noting that an issue has been triaged by gemini label noting that an issue has been triaged by gemini on mar 27 2026 csvn commented on mar 27 2026 csvn on mar 27 2026 contributor author more actions a workaround other than downgrading to vitest 4 0 8 is to use imports in package json this can resolve files the same as tsconfig json paths imports util src app util ts scripts csvn commented on mar 27 2026 csvn on mar 27 2026 contributor author more actions note likely related to angular build and not angular cli like the label suggests emilycarter6561 byte commented on mar 28 2026 emilycarter6561 byte on mar 28 2026 via email more actions thanks for the details it looks like this issue might be related to a change in vitest 4 1 0 that affects how path aliases are handled in coverage the workaround of using imports in package json seems like a good temporary fix hopefully a proper solution can be implemented soon appreciate the heads up on this on fri mar 27 2026 6 44 pm christian svensson wrote csvn left a comment angular angular cli 32891 32891 comment note likely related to angular build and not angular cli like the label suggests reply to this email directly view it on github 32891 email_source notifications email_token b7z2x6coqmkf2yy5ekfnjul4s4g5xa5cnfsnuabfm5uwiorpf5tws5bnnb2wel2jonzxkzkdn5ww2zlooqxtimjugu4tmmrxge32m4tfmfzw63vkon2we43dojuwezleuvsxmzlooswgm33porsxex3dnruwg2y issuecomment 4145962717 or unsubscribe https github com notifications unsubscribe auth b7z2x6dbab62vytqqaj4jo34s4g5xavcnfsm6aaaaacxcuthaovhi2dsmvqwix3lmv43oslton2wkq3pnvwwk3tuhm2dcnbvhe3denzrg4 you are receiving this because you are subscribed to this thread message id alan agius4 added area angular build angular build unit test and removed area angular cli on mar 30 2026 sign up for free to join this conversation on github already have an account sign in to comment metadata metadata assignees no one assigned labels angular build unit test area angular build gemini triaged label noting that an issue has been triaged by gemini label noting that an issue has been triaged by gemini type no type projects no projects milestone no milestone relationships none yet development no branches or pull requests issue actions open in github copilot app footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|