Skip to content

Reconnect TS sourcemaps  #19841

Closed
Closed

Description

@kara

We temporarily removed sorcery while we were waiting for the new version of tsickle and TS 2.4. Now that these updates are in, we should be able to hook sorcery (or the rollup plugin) back up.

Activity

  1. jasonaden commented on Nov 10, 2017

    @jasonaden
    Contributor

    We will need to put back this file and the calls to it (such as this one).

  2. IgorMinar commented on Dec 22, 2017

    @IgorMinar
    Contributor

    while we are fixing this we should ensure that we also resolve #14021 as well.

  3. added this to the Backlog milestone on Jan 23, 2018
  4. modified the milestones: Backlog, needsTriage on Feb 26, 2018
  5. IgorMinar commented on Jun 1, 2020

    @IgorMinar
    Contributor

    This is still a problem in 10.0.0-rc.0.

  6. petebacondarwin commented on Jun 1, 2020

    @petebacondarwin
    Contributor

    Note that we have our own library that can do what sorcery did. Currently it is in ngcc: https://github.com/angular/angular/tree/master/packages/compiler-cli/ngcc/src/sourcemaps
    But will soon be in ngtsc: #37114

  7. added
    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
    and removed on Oct 1, 2020
  8. jelbourn commented on Oct 16, 2020

    @jelbourn
    Contributor

    @petebacondarwin can this issue be combined/duplicated into another issue? Maybe a tracking issue for ngtsc?

  9. petebacondarwin commented on Oct 19, 2020

    @petebacondarwin
    Contributor

    I think this is obsolete since we now use Bazel to build Angular. So in fact we should close this in favour of #23520, which I will re-open.

  10. angular-automatic-lock-bot commented on Nov 19, 2020

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

  11. locked and limited conversation to collaborators on Nov 19, 2020
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

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: build & ciRelated the build and CI infrastructure of the projectarea: packagingIssues related to Angular's creation of npm packagesfreq4: criticalstate: confirmedtype: bug/fix

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions