René's URL Explorer Experiment


Title: RFC: Ivy Library Distribution · Issue #38366 · angular/angular · GitHub

Open Graph Title: RFC: Ivy Library Distribution · Issue #38366 · angular/angular

X Title: RFC: Ivy Library Distribution · Issue #38366 · angular/angular

Description: Authors: Pete Bacon Darwin (@petebacondarwin), Alex Rickabaugh (@alxhub) Status: Ended tl;dr We're proposing an update to the Angular Package Format (APF), which defines an "Ivy-native" library format on NPM and introduces a new tool (th...

Open Graph Description: Authors: Pete Bacon Darwin (@petebacondarwin), Alex Rickabaugh (@alxhub) Status: Ended tl;dr We're proposing an update to the Angular Package Format (APF), which defines an "Ivy-native" library for...

X Description: Authors: Pete Bacon Darwin (@petebacondarwin), Alex Rickabaugh (@alxhub) Status: Ended tl;dr We're proposing an update to the Angular Package Format (APF), which defines an "Ivy-native&quo...

Opengraph URL: https://github.com/angular/angular/issues/38366

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"RFC: Ivy Library Distribution","articleBody":"**Authors**: Pete Bacon Darwin (@petebacondarwin), Alex Rickabaugh (@alxhub)\r\n\r\n**Status**: Ended\r\n\r\n# tl;dr\r\n\r\nWe're proposing an update to the Angular Package Format (APF), which defines an \"Ivy-native\" library format on NPM and introduces a new tool (the Angular Linker) to process libraries for inclusion in an application build. This linker will be available as a Babel plugin for maximum compatibility with all Angular build processes, and will be integrated into the Angular CLI.\r\n\r\nThis proposal replaces the current system of publishing libraries in View Engine format, and running ngcc, the Angular compatibility compiler, to upgrade them to Ivy after `npm install`.\r\n\r\nAs part of upgrading the APF, we're also proposing standardizing on ES2015 as a publication format.\r\n\r\n# Background\r\n\r\nThe Angular ecosystem is currently in a transitional period as applications update from the View Engine to the Ivy runtime. During this period it was essential that the library ecosystem on NPM remain compatible with View Engine applications. To achieve this, libraries are always built and published in \"View Engine format\", which ensures compatibility with all existing View Engine applications, including those using Angular 9+ and opting out of Ivy.\r\n\r\nTo enable Ivy applications to consume these View Engine libraries, we introduced the Angular Compatibility Compiler (ngcc). ngcc runs as part of an Ivy application's build process and updates any View Engine libraries in `node_modules` to use the Ivy runtime. This allows the Ivy app to build against View Engine libraries.\r\n\r\nAs we deprecated View Engine runtime and will remove it completely in a future version of Angular, this compatibility is only needed temporarily, after which libraries can ship on NPM in a format that's directly compatible with Ivy. This RFC proposes such an \"Ivy-native\" library format.\r\n\r\n# Requirements\r\n\r\nWe considered the following goals to be essential requirements which ensure the health and stability of the Angular ecosystem:\r\n\r\n1. **Low-friction integration with non-CLI build tooling.**\r\n\r\nMany applications use the Angular CLI to build, but not all. Like with ngcc, it must be straightforward for non-CLI builds to consume Ivy libraries from NPM. Not all Angular projects are able to use the CLI.\r\n\r\nFor example, previously lazy loading in Angular was extremely difficult or impossible to achieve without using the Angular CLI (or the Webpack plugin) and even then it only worked with the `@angular/router`. In Angular 8 lazy loading was supported via ES dynamic import(), which allowed for lazy loading of Angular modules and components independently of the toolchain in use.\r\n\r\n2. **No in-place modification of node_modules.**\r\n\r\nA key aspect of ngcc's design is that it updates libraries in-place in `node_modules`. This was needed to ensure compatibility with existing build tooling, and because changes to library .d.ts files were required for downstream compilations.\r\n\r\nMutating `node_modules` causes a number of problems: Package managers frequently overwrite such updates, requiring expensive re-runs of ngcc. Certain tools such as PNPM also rely on the immutability of `node_modules` and are simply not compatible with ngcc as a result.\r\n\r\nThis was acceptable since ngcc is a temporary solution, but in the long term mutating `node_modules` should not be a part of our strategy for libraries.\r\n\r\n3. **Maintaining Angular's guarantees of library compatibility.**\r\n\r\nAngular formally guarantees that a library built with a major version X will be compatible with an application using version X+1. For example, Angular 8 libraries can be used from applications built with Angular 9.\r\n\r\nIn practice, this compatibility often extends much further, and there have been very few breakages since the original Angular 2.0 release.\r\n\r\n4. **Generated Ivy instructions do not become public API.**\r\n\r\nThe code generation API of the Ivy runtime, like that of View Engine, should remain private API. That is, Ivy instructions should not be published to NPM, as that would severely limit Angular's ability to evolve and optimize the runtime in the future.\r\n\r\n# Feedback Requested\r\n\r\nThe Angular team is interested in any and all feedback from our community regarding this proposal. There are a few aspects of this design where we feel this feedback will be especially valuable:\r\n\r\n* For application developers that use a custom build process instead of the Angular CLI, what challenges do you anticipate integrating the linker into your build process? How does this compare to using ngcc today? Would something other than a Babel plugin work well for you?\r\n\r\n* For application developers who use the UMD package format in some way (e.g. with server-side rendering), what challenges do you anticipate if Angular libraries no longer ship with UMD bundles? What could the Angular CLI do to alleviate those challenges?\r\n\r\n* For authors of Angular utilities that rely on `.metadata.json` information, what does your tooling do, and how are you using the metadata files? What could we provide to ensure your tools are still able to function?\r\n\r\n# Proposal\r\n\r\n## The compilation lifecycle of Angular libraries\r\n\r\nAn important aspect of Angular compilation in the previous View Engine architecture is that libraries have their NgFactory code generated at application build time, using the same version of the Angular compiler as the application itself. This has several important effects:\r\n\r\n* It ensures libraries are compatible with a wide range of Angular versions, including future versions, which satisfies requirement 3.\r\n* Code generated for View Engine NgFactory classes is never published to NPM, satisfying requirement 4.\r\n\r\nAt the same time, this approach requires that libraries are shipped on NPM with the metadata required to run Angular compilation later, during the application build. For View Engine, this is achieved through `.metadata.json` files which are published alongside each JS file.\r\n\r\nFor Ivy libraries, we propose a modification of this architecture, which maintains its benefits while optimizing for application build efficiency. Instead of performing all compilation at application build time, Ivy libraries will be compiled in two phases:\r\n\r\nPrior to publication on NPM, the library is compiled with the Ivy compiler in a special library mode. Instead of generating `.metadata.json` files, the compiler collects metadata for each component and emits it into the component class itself, in place of the normal Ivy component definition.\r\n\r\nDuring the application build, a \"linker\" tool processes each library file and completes compilation of each component, replacing the inline metadata with a full component definition.\r\n\r\n### Pre-publication compilation\r\n\r\nPrior to publication on NPM, an Ivy library will be compiled by `ngc` in a library mode. This operation analyzes the declared Angular types in the library (any components, directives, etc) and produces self-contained metadata which is inlined into the component class in place of the Ivy component definition.\r\n\r\nUnlike with View Engine's `.metadata.json` files, the inlined component metadata is \"self-contained\" - it has all of the information needed to compile that component, without the need to reference any other files (such as the NgModule or any consumed directives/pipes/etc). This means that the final compilation step can be performed on a component-by-component basis, opening up lots of opportunities for caching and parallelization.\r\n\r\n### Application build \"linking\"\r\n\r\nAn application will install many Angular libraries from NPM into its `node_modules`. The code in these libraries cannot be bundled directly along with the built application as it is not fully compiled. Compilation must be finished by running a new Angular tool which translates the inline metadata into final component definitions. We call this process \"linking\" and the tool the \"Angular linker\".\r\n\r\nThe linker scans its inputs for inline Angular metadata, extracts it, and replaces it with a compiled component. Because this process happens during the application build, it uses the same version of the Angular compiler, ensuring that the app and all of its libraries are built with a single version of Angular.\r\n\r\n### The linker as a Babel plugin\r\n\r\nTo satisfy requirement 1, it makes sense to implement the linker as a Babel plugin. Babel has become a de facto standard for JS tooling, and babel plugins can be used in a variety of environments. Webpack and Rollup can both use Babel plugins, in addition to standalone Babel itself.\r\n\r\nAs a Babel plugin, the linker will receive an input AST corresponding to a particular library file, and transform it, replacing the inline metadata with a compiled component definition and maintaining the correct source mapping.\r\n\r\nIt's also common for Babel plugins to support some kind of build caching. We can take advantage of this in the linker plugin to make repeat compilations virtually free. Effectively, then, libraries will only need to be processed by the linker a single time, regardless of other NPM operations (unlike ngcc which often needed to be re-run if NPM or yarn reverted changes ngcc made to `node_modules`).\r\n\r\n### Integration with Angular Tooling\r\n\r\nThe Angular CLI will integrate the linker plugin automatically, so users of the CLI will be able to install Ivy-native libraries from NPM without any additional configuration.\r\n\r\nOn the publication side, ng-packagr will be updated with the capability to publish libraries in the Ivy-native format as well, meaning that any existing libraries which use it will be trivially able to switch over.\r\n\r\n## Removing UMD from the APF\r\n\r\nAs part of updating the Angular Package Format, we're standardizing on ES2015 as the publication format for libraries. This means that UMD bundles will no longer be published as part of Angular packages.\r\n\r\nES5 support was dropped in the previous version of the APF, and Angular tooling now downlevels ES2015 sources on NPM to ES5 as needed. This approach has been working extremely well, and we feel that UMD could be handled in a similar way.\r\n\r\nUsing ES2015 as the \"source format of truth\" strikes a balance between flexibility for translation into other needed formats, and ease of use with most tooling and browsers able to consume ES2015 without modification (so post-processing isn't required).\r\n\r\n# Alternatives Considered\r\n\r\nThis section summarizes potential alternative designs that were considered and rejected. See the linker design doc for more details.\r\n\r\n## Shipping instructions directly to NPM\r\n\r\nIt would theoretically be possible to compile libraries directly in Ivy mode, and ship the resulting artifacts to NPM directly. Downstream consumers would not need to perform any extra build steps to consume such libraries.\r\n\r\nHowever, this idea runs into a number of issues with the requirements listed above:\r\n\r\n* It complicates library compatibility, especially across major versions of Angular.\r\n* It greatly increases the difficulty of changing the Angular runtime, since all runtime instructions would become \"public API\" of Angular.\r\n\r\n## Continuing to use ngcc\r\n\r\nIt's possible that ngcc could be adapted to continue to work indefinitely. However, ngcc has several undesirable characteristics that fail to meet our requirements for a long-term library solution:\r\n\r\n* It mutates node_modules, making it incompatible with a number of other tools in the JS ecosystem.\r\n* It requires expensive processing that's hard to cache, since it consumes entire packages as input instead of individual files.\r\n\r\n# Additional Resources\r\n\r\n* [Design doc](https://docs.google.com/document/d/148eXrCST6TM7Uo90KxaBrMbOkwJbYrQSQgRaGMK5WRc/edit#) for the Angular Linker concept","author":{"url":"https://github.com/alxhub","@type":"Person","name":"alxhub"},"datePublished":"2020-08-06T17:13:31Z","url":"https://github.com/angular/angular/issues/38366"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:06c0a51e-3903-a93b-86db-c21776ed0d1a
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idE87C:3A4875:98576C:CC4D9B:6B00E881
html-safe-nonce3e02d23372e6e3cce86c9825484635341f6814960484ad2e794dfb9304b703f2
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFODdDOjNBNDg3NTo5ODU3NkM6Q0M0RDlCOjZCMDBFODgxIiwidmlzaXRvcl9pZCI6Ijc0MDYyNDE1OTQxMzI3MTk3NDUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmacf26b55fbce78a1f67e5be503747a505df6059866f18e8c906a85d413051e4995
hovercard-subject-tagissue:674474599
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/38366/issue_layout
twitter:imagehttps://opengraph.githubassets.com/af7e4d14af623cf1fa2641b1e98f307142ce19e6f4e2b35cb7d16bddf679b369/angular/angular/issues/38366
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/af7e4d14af623cf1fa2641b1e98f307142ce19e6f4e2b35cb7d16bddf679b369/angular/angular/issues/38366
og:image:altAuthors: Pete Bacon Darwin (@petebacondarwin), Alex Rickabaugh (@alxhub) Status: Ended tl;dr We're proposing an update to the Angular Package Format (APF), which defines an "Ivy-native" library for...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamealxhub
hostnamegithub.com
expected-hostnamegithub.com
None27088b6977484d0d3321d9a11c907c6d6637b315cfa359ef7952dbf6292f9b14
turbo-cache-controlno-preview
go-importgithub.com/angular/angular git https://github.com/angular/angular.git
octolytics-dimension-user_id139426
octolytics-dimension-user_loginangular
octolytics-dimension-repository_id24195339
octolytics-dimension-repository_nwoangular/angular
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id24195339
octolytics-dimension-repository_network_root_nwoangular/angular
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release624179fb8b88d26ba5bba08894eb60a1c5a1d93d
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/angular/angular/issues/38366#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F38366
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F38366
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=angular%2Fangular
Reloadhttps://github.com/angular/angular/issues/38366
Reloadhttps://github.com/angular/angular/issues/38366
Reloadhttps://github.com/angular/angular/issues/38366
angularhttps://github.com/angular
angularhttps://github.com/angular/angular
Codehttps://github.com/angular/angular
Issues835 (835)https://github.com/angular/angular/issues
Pull requests140 (140)https://github.com/angular/angular/pulls
Discussionshttps://github.com/angular/angular/discussions
Actionshttps://github.com/angular/angular/actions
Projectshttps://github.com/angular/angular/projects
Security and quality40 (40)https://github.com/angular/angular/security
Insightshttps://github.com/angular/angular/insights
https://github.com/angular/angular
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/38366
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/38366
RFC: Ivy Library Distributionhttps://github.com/angular/angular/issues/38366#top
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issue-674474599
@petebacondarwinhttps://github.com/petebacondarwin
@alxhubhttps://github.com/alxhub
Design dochttps://docs.google.com/document/d/148eXrCST6TM7Uo90KxaBrMbOkwJbYrQSQgRaGMK5WRc/edit
Nexthttps://github.com/angular/angular/issues/38366?timeline_page=1
alxhubhttps://github.com/alxhub
on Aug 6, 2020https://github.com/angular/angular/issues/38366#event-3630208996
https://github.com/emilio-martinez
emilio-martinezhttps://github.com/emilio-martinez
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670151872
https://github.com/oocx
oocxhttps://github.com/oocx
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670165094
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670166870
https://github.com/mlc-mlapis
mlc-mlapishttps://github.com/mlc-mlapis
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670203184
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670228655
@LayZeeDKhttps://github.com/LayZeeDK
https://github.com/mlc-mlapis
mlc-mlapishttps://github.com/mlc-mlapis
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670233382
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 6, 2020https://github.com/angular/angular/issues/38366#issuecomment-670248351
@alxhubhttps://github.com/alxhub
The Theory of Ivyhttps://youtu.be/isb5Ef6yI48
https://user-images.githubusercontent.com/6364586/89593696-1b95b200-d850-11ea-98fd-953d22864cbc.png
https://user-images.githubusercontent.com/6364586/89593732-32d49f80-d850-11ea-8d70-a9ecbc20ce6e.png
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670252858
The Theory of Ivyhttps://youtu.be/isb5Ef6yI48
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670254405
https://github.com/itea-dev
itea-devhttps://github.com/itea-dev
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670261796
https://github.com/johncrim
johncrimhttps://github.com/johncrim
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670296831
ng-packagr/ng-packagr#460https://github.com/ng-packagr/ng-packagr/issues/460
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670381847
https://github.com/yjaaidi
yjaaidihttps://github.com/yjaaidi
on Aug 7, 2020https://github.com/angular/angular/issues/38366#issuecomment-670434205
@alxhubhttps://github.com/alxhub
@LayZeeDKhttps://github.com/LayZeeDK
https://github.com/alyssamichelle
alyssamichellehttps://github.com/alyssamichelle
on Aug 8, 2020https://github.com/angular/angular/issues/38366#issuecomment-670841821
@alxhubhttps://github.com/alxhub
https://github.com/thesayyn
thesayynhttps://github.com/thesayyn
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676568857
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676588775
NgccClassSymbolhttps://github.com/angular/angular/blob/9ad69c1503256e7347d41a59fd696f097bd172c1/packages/compiler-cli/ngcc/src/host/ngcc_host.ts#L28-L57
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676592952
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676619977
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676669767
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676796014
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676804371
@SchnWalterhttps://github.com/SchnWalter
injection-jshttps://github.com/mgechev/injection-js
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 19, 2020https://github.com/angular/angular/issues/38366#issuecomment-676808409
cacheDirectoryhttps://webpack.js.org/loaders/babel-loader/#options
https://github.com/LayZeeDK
LayZeeDKhttps://github.com/LayZeeDK
on Aug 20, 2020https://github.com/angular/angular/issues/38366#issuecomment-677266317
@bbarryhttps://github.com/bbarry
https://github.com/xiaoxiangmoe
xiaoxiangmoehttps://github.com/xiaoxiangmoe
on Aug 20, 2020https://github.com/angular/angular/issues/38366#issuecomment-677504499
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 20, 2020https://github.com/angular/angular/issues/38366#issuecomment-677803612
https://github.com/alxhub
alxhubhttps://github.com/alxhub
on Aug 20, 2020https://github.com/angular/angular/issues/38366#issuecomment-677841359
alxhubhttps://github.com/alxhub
completedhttps://github.com/angular/angular/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
on Aug 20, 2020https://github.com/angular/angular/issues/38366#event-3676685498
alxhubhttps://github.com/alxhub
on Aug 20, 2020https://github.com/angular/angular/issues/38366#event-3676686090
angularhttps://github.com/angular
on Aug 20, 2020https://github.com/angular/angular/issues/38366#event-3676687010
Sign up for freehttps://github.com/signup?return_to=https://github.com/angular/angular/issues/38366
Sign in to commenthttps://github.com/login?return_to=https://github.com/angular/angular/issues/38366
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.