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
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
jasonaden commentedon Nov 10, 2017
We will need to put back this file and the calls to it (such as this one).
IgorMinar commentedon Dec 22, 2017
while we are fixing this we should ensure that we also resolve #14021 as well.
IgorMinar commentedon Jun 1, 2020
This is still a problem in 10.0.0-rc.0.
petebacondarwin commentedon Jun 1, 2020
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
jelbourn commentedon Oct 16, 2020
@petebacondarwin can this issue be combined/duplicated into another issue? Maybe a tracking issue for ngtsc?
petebacondarwin commentedon Oct 19, 2020
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.
angular-automatic-lock-bot commentedon Nov 19, 2020
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.