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
Given the AoT plugin no longer writes generated code to disk, allowing a developer to set the genDir for code generation adds a huge amount of complexity to lazy module resolution.
We should simply assume that the generated code ends up in the (virtual) filesystem as a sibling to the original file, and thus resolving for ngfactory code should require simply appending .ngfactory to the path.
Activity
hansl commentedon Oct 25, 2016
I'm going to remove the
genDiroption to the plugin entirely. There's absolutely no need for it.fix(aot): remove the genDir plugin option.
fix(aot): remove the genDir plugin option.
fix(aot): remove the genDir plugin option.
fix(aot): remove the genDir plugin option.
fix(aot): remove the genDir plugin option.
angular-automatic-lock-bot commentedon Sep 6, 2019
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.
fix(aot): remove the genDir plugin option.