Meta tags:
description= Which @angular/* package(s) are the source of the bug? Don t known / other Is this a regression? Yes Description The package.json file generated by ng new includes the dev dependency jasmine-core : ~5.7.0 , but jasmine-core 4.6.1 is al...;
Headings (most frequently used words):
commented, on, the, sgravrock, 2025, navigation, bug, please, provide, oct, angular, projects, description, metadata, footer, of, this, you, 31, 2026, new, install, jasmine, core, but, use, 30575, menu, repository, activity, issue, actions, which, package, are, source, is, regression, link, to, minimal, reproduction, exception, or, error, saw, environment, discovered, in, run, ng, version, anything, else, jun, 24, atscott, nov, dgp1130, jan, 26, aug, assignees, labels, type, milestone, relationships, development,
Text of the page (most frequently used words):
the (40), #jasmine (32), and (29), #angular (23), that (19), core (18), for (17), github (15), version (15), you (14), 2025 (13), sgravrock (12), actions (11), karma (11), but (11), this (9), are (9), issue (8), more (8), new (8), commented (7), package (7), 2026 (6), projects (6), all (6), use (6), team (6), steps (6), with (6), support (6), from (6), oct (6), cli (6), can (5), security (5), copilot (5), sign (5), have (5), about (5), anything (5), author (5), next (5), versions (5), major (5), jun (5), run (5), code (5), open (4), one (4), people (4), actually (4), see (4), agenda (4), meeting (4), determine (4), release (4), out (4), there (4), firefox (4), browser (4), using (4), window (4), bug (4), who (4), running (4), json (4), dependency (4), another (4), users (4), which (4), build (4), link (4), install (4), your (4), navigation (3), labels (3), think (3), happen (3), would (3), jan (3), dgp1130 (3), reacted (3), react (3), other (3), changes (3), has (3), don (3), documented (3), come (3), override (3), faq (3), npm (3), devkit (3), please (3), provide (3), note (3), step (3), installed (3), copy (3), 30575 (3), quality (3), tab (3), refresh (3), session (3), reload (3), developers (3), changelog (3), customer (3), enterprise (3), grade (3), features (3), not (2), community (2), status (2), footer (2), pull (2), requests (2), development (2), milestone (2), type (2), metadata (2), already (2), let (2), know (2), never (2), going (2), why (2), google (2), thing (2), aug (2), needs (2), discussion (2), here (2), bump (2), work (2), test (2), get (2), hopefully (2), then (2), current (2), chrome (2), edge (2), 102 (2), safari (2), supported (2), nov (2), pretty (2), only (2), problems (2), aware (2), problematic (2), done (2), unmaintained (2), issues (2), atscott (2), alex (2), what (2), still (2), ship (2), occasionally (2), confused (2), they (2), response (2), compiler (2), platform (2), schematics (2), latest (2), add (2), shows (2), different (2), description (2), source (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), fixes (2), products (2), secret (2), perform, action, time, share, personal, information, manage, cookies, contact, docs, privacy, terms, inc, app, branches, none, yet, relationships, assigned, assignees, comment, account, join, conversation, free, forget, possibility, being, updated, fine, isn, doing, double, installation, how, many, because, hate, same, idea, removed, steve, gravrock, just, quick, update, created, trying, web, into, well, maybe, argument, jumping, directly, resolved, soon, make, clydin, collaborator, 155, 128, 140, potential, factor, consistently, treated, semver, until, around, was, light, breaking, switch, instead, nobody, reported, any, onerror, addeventlistener, might, haven, heard, far, recall, reports, involving, been, turned, good, news, thank, concern, effectively, untested, upgrade, library, real, mechanism, address, bumping, either, patch, getting, something, contributor, shift, cost, supporting, decision, abandon, back, where, belongs, unsupported, thought, were, newer, https, pages, html, 002, option, final, adds, unconditional, deprecation, warning, along, lines, example, today, 2066, added, alan, agius4, transferred, jeanmeche, activity, daniel, schreiber, yiding, wang, else, node, manager, darwin, arm64, common, forms, router, architect, 2000, rxjs, typescript, zone, environment, discovered, exception, error, saw, minimal, reproduction, user, maintain, seen, mismatch, cause, couple, makes, download, statistics, much, useless, determining, uptake, since, unknown, probably, large, portion, downloads, problem, declares, tries, set, project, doesn, necessary, expected, agree, single, observed, show, two, displayed, accept, defaults, some, name, file, generated, includes, dev, also, used, tests, reproduce, yes, regression, known, body, opened, items, message, dismiss, alert, switched, accounts, appearance, settings, search, pricing, event, talks, workshops, partners, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, ons, trust, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, enterprises, stage, businesses, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, environments, codespaces, analysis, enforcement, automation, coding, agent, tasks, automated, hosting, review, collaboration, menu, skip, content,
Text of the page (random words):
new angular projects install jasmine core 5 7 0 but use 4 6 1 issue 30575 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 20 20 actions security and quality 8 8 insights more items new angular projects install jasmine core 5 7 0 but use 4 6 1 30575 new issue copy link new issue copy link open open new angular projects install jasmine core 5 7 0 but use 4 6 1 30575 copy link description sgravrock opened on jun 21 2025 issue body actions which angular package s are the source of the bug don t known other is this a regression yes description the package json file generated by ng new includes the dev dependency jasmine core 5 7 0 but jasmine core 4 6 1 is also installed and used to run tests in karma steps to reproduce install angular cli 20 0 3 run ng new some name and accept all the defaults note the jasmine core dependency in package json run npm test and note the jasmine version displayed in the browser run npm ls jasmine core expected the versions from steps 3 and 4 agree and step 5 shows that only a single version of jasmine core is installed observed step 3 and 4 show different major versions and step 5 shows that two different versions of jasmine core are installed the problem is that karma jasmine declares a dependency on jasmine core 4 x ng new tries to set up the project to use jasmine core 5 x but it doesn t add the necessary override note i m not an angular user but i do maintain jasmine i ve seen this version mismatch cause a couple of problems one is that angular users are occasionally confused about which major version of jasmine core they re actually using the other is that it makes jasmine core download statistics pretty much useless for determining uptake of the latest major version since an unknown but probably large portion of 5 x downloads are from angular users who are actually still running 4 x please provide a link to a minimal reproduction of the bug no response please provide the exception or error you saw please provide the environment you discovered this bug in run ng version angular cli 20 0 3 node 20 19 0 package manager npm 10 8 2 os darwin arm64 angular 20 0 4 common compiler compiler cli core forms platform browser router package version angular devkit architect 0 2000 3 angular devkit core 20 0 3 angular devkit schematics 20 0 3 angular build 20 0 3 angular cli 20 0 3 schematics angular 20 0 3 rxjs 7 8 2 typescript 5 8 3 zone js 0 15 1 anything else no response react with 3 reacted by daniel schreiber alex and yiding wang activity jeanmeche transferred this issue from angular angular on jun 21 2025 alan agius4 added needs discussion on the agenda for team meeting to determine next steps on the agenda for team meeting to determine next steps on jun 23 2025 sgravrock commented on jun 24 2025 sgravrock on jun 24 2025 author more actions angular users are occasionally confused about which major version of jasmine core they re actually using here s an example from today jasmine jasmine 2066 sgravrock commented on oct 2 2025 sgravrock on oct 2 2025 author more actions one option is for me to do a final jasmine core 4 x release that adds an unconditional deprecation warning along the lines of you are running jasmine core 4 x which is unsupported and unmaintained if you re using karma and thought you were running a newer version see https jasmine github io pages faq html 002 karma version that would let users know what s going on and hopefully shift the cost of supporting google s decision to abandon but still ship karma back to where it belongs react with 1 reacted by alex atscott commented on oct 31 2025 atscott on oct 31 2025 contributor more actions sgravrock bumping the version in either a patch or getting another karma jasmine release out is something we re open to the concern would be that s it s effectively an untested version upgrade for a dependency in a library that s unmaintained karma so there d be no real mechanism to address issues that come from the version bump are you aware of anything problematic that has come up for people who have done the version override in package json as you ve documented in the jasmine faq sgravrock commented on oct 31 2025 sgravrock on oct 31 2025 author more actions that s good news thank you are you aware of anything problematic that has come up for people who have done the version override in package json as you ve documented in the jasmine faq no i haven t heard anything as far as i can recall all the bug reports involving karma and jasmine 5 have been from people who turned out to be running jasmine 4 5 0 was pretty light on breaking changes the only thing i can think of that might be an issue is the switch to using addeventlistener instead of window onerror but nobody s reported any problems there sgravrock commented on nov 1 2025 sgravrock on nov 1 2025 author more actions the other potential factor is changes in browser support jasmine has never consistently treated browser support changes as semver major but i don t think we documented that we don t do that until around 5 3 0 or so 4 6 0 supported safari 14 16 firefox 91 and 102 then current versions of chrome firefox and edge 5 12 1 supported safari 16 17 firefox 102 155 128 and 140 then current versions of chrome firefox and edge dgp1130 commented on jan 26 2026 dgp1130 on jan 26 2026 collaborator more actions just a quick update here clydin created a pr to bump karma to use jasmine v5 and we re trying to work with the web test team to see if we can get this into a release jasmine v6 is out as well so there s maybe an argument for jumping directly to there hopefully we can get this resolved soon and make a release happen for karma react with 1 reacted by steve gravrock dgp1130 removed needs discussion on the agenda for team meeting to determine next steps on the agenda for team meeting to determine next steps on jan 26 2026 sgravrock commented on aug 8 2026 sgravrock on aug 8 2026 author more actions let s forget about the possibility of karma jasmine being updated i think we all know that s never going to happen and that s fine but why isn t google doing anything about the double installation issue i already have no idea how many people actually use jasmine 5 x or 6 x because of this and i would hate to see the same thing happen to 7 x 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 no labels no labels 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
|