Angular signal input migration fails with "extends": "@tsconfig/strictest/tsconfig.json" in tsconfig · Issue #59348 · angular/angular · GitHub
Skip to content

Angular signal input migration fails with "extends": "@tsconfig/strictest/tsconfig.json" in tsconfig #59348

Closed as duplicate

Description

@wein2011

Which @angular/* package(s) are the source of the bug?

core

Is this a regression?

Yes

Description

When running the Angular Migration to signal inputs

ng generate @angular/core:signal-input-migration

the operations fails with the following error:

Tsconfig could not be parsed or is invalid:

File '@tsconfig/strictest/tsconfig.json' not found.

After removing the line

"extends": "@tsconfig/strictest/tsconfig.json"

from tsconfig.common.json, the operations completes successfully.

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: 19.0.6
Node: 22.12.0
Package Manager: npm 10.9.0
OS: win32 x64

Angular: 19.0.5
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                              Version
--------------------------------------------------------------
@angular-devkit/architect            0.1900.6
@angular-devkit/build-angular        19.0.6
@angular-devkit/core                 19.0.6
@angular-devkit/schematics           19.0.6
@angular/cdk                         19.0.4
@angular/cli                         19.0.6
@angular/material                    19.0.4
@angular/material-date-fns-adapter   19.0.4
@schematics/angular                  19.0.6
rxjs                                 7.8.1
typescript                           5.6.3
zone.js                              0.15.0

Anything else?

No response

Activity

  1. added this to the needsTriage milestone on Jan 2, 2025
  2. devversion commented on Jan 10, 2025

    @devversion
    Member

    @wein2011 Thanks for the issue. I tried reproducing this issue, but couldn't reproduce. Is it possible the package for @tsconfig/strictest simply wasn't installed?

    Please create a reproduction if possible. Thanks

  3. added
    needs reproductionThis issue needs a reproduction in order for the team to investigate further
    on Jan 10, 2025
  4. modified the milestones: needsTriage, Backlog on Jan 10, 2025
  5. self-assigned this
    on Jan 10, 2025
  6. wein2011 commented on Jan 10, 2025

    @wein2011
    Author

    I attached a simple reproduction which is based on the standard new Angular project.

    The differences are:

    1. tsconfig.json includes the line: "extends": "@tsconfig/strictest/tsconfig.json"
    2. The project migration-test-1 is part of a workspace within the "migration test"/package.json file.

    The issue only occurs when using the workspaces feature within package.json which changes the default location of node_modules.

    In order to reproduce, please follow these steps:

    1. Unzip the migration test.zip file
    2. $> cd "migration test"
    3. $> npm install
      This will create the node_modules folder next to and not within the migration-test-1 folder
    4. $> cd migration-test-1
    5. $> ng generate @angular/core:signal-input-migration
      Which directory do you want to migrate? ./
      Do you want to migrate as much as possible, even if it may break your build? no
    6. This results in:
      Preparing analysis for: tsconfig.app.json..
      Tsconfig could not be parsed or is invalid:
      File '@tsconfig/strictest/tsconfig.json' not found.

    I assume this has to do with the fact that the node_modules are now one level higher. However, this should be ok.

    migration test.zip

  7. angular-automatic-lock-bot commented on Feb 13, 2025

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  8. locked and limited conversation to collaborators on Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: migrationsIssues related to `ng update`/`ng generate` migrationscross-cutting: signalsneeds reproductionThis issue needs a reproduction in order for the team to investigate further

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions