Skip to content

typescript 2.9.x problem with @angular-devkit/build-angular and @angular/compiler-cli #25141

Closed

Description

@steve3d

I'm submitting a might be a problem, and I don't think this is a bug.


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[x] Other... Please describe:

Current behavior

now with angular 6.1 released, the @angular/core now support ts 2.9.x version, but there are still some packages need ts < 2.9.x:

  • @ngtools/webpack which is needed by @angular-devkit/build-angular sill want ts version < 2.9
  • tsickle which is needed by @angular/compiler-cli, and this is even worse, the latest version of this still need ts < 2.8.

Expected behavior

all packages should also support ts 2.9, not only @angular/core

Activity

  1. sarunint commented on Jul 26, 2018

    @sarunint
    Contributor

    Angular CLI v6.1.1 has been released, which will fix this issue.

  2. gkalpak commented on Jul 26, 2018

    @gkalpak
    Member

    @angular/cli, @ngtools/webpack and tsickle are indeed fixed.
    There is still an issue with @angular/language-service, but it can be tracked separately in #24865.

  3. sarunint commented on Jul 26, 2018

    @sarunint
    Contributor

    @gkalpak tsickle has released 0.32.1, but @angular/compiler-cli still depends on tsickle@^0.30.0, which still restrict TypeScript version to 2.8. So I don't think this issue is completely solved.

    Edit: I mean 0.32.1 does not match ^0.30.0.

  4. added a commit that references this issue on Jul 26, 2018
    03574ca
  5. added
    area: packagingIssues related to Angular's creation of npm packages
    area: coreIssues related to the framework runtime
    on Jul 26, 2018
  6. modified the milestone: needsTriage on Jul 26, 2018
  7. steve3d commented on Jul 27, 2018

    @steve3d
    Author

    when can we expect a new fixed @angular/compiler-cli?

  8. gkalpak commented on Jul 27, 2018

    @gkalpak
    Member

    If everything goes according to plan, there should be a new release next week (probably ~Wednesday).

  9. added a commit that references this issue on Jul 27, 2018
    317c708
  10. AmyJeanes commented on Jul 30, 2018

    @AmyJeanes

    Thanks @gkalpak - can you let us know on this issue when that has been released?

  11. sarunint commented on Jul 30, 2018

    @sarunint
    Contributor

    @MattJeanes The Angular team usually cut releases on Wednesdays. (In my timezone, at least)

  12. simeyla commented on Jul 25, 2019

    @simeyla

    This issue will never be solved.

  13. hakimio commented on Jul 25, 2019

    @hakimio

    @simeyla What? It was fixed.

  14. Splaktar commented on Jul 30, 2019

    @Splaktar
    Contributor

    Fixed in 7.0.0.

  15. angular-automatic-lock-bot commented on Sep 15, 2019

    @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.

  16. locked and limited conversation to collaborators on Sep 15, 2019
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

    area: coreIssues related to the framework runtimearea: packagingIssues related to Angular's creation of npm packages

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions