Meta tags:
description= モダンなアプリを構築するためのウェブ開発フレームワーク;
author= Angular Team;
keywords= Angular framework, TypeScript, web development, hydration, Signals, standalone components, accessibility, performance;
Headings (most frequently used words):
differences, with, upgrademodule, downgrading, multiple, modules, community, downgrademodule, 目次, api, description, usage, notes, social, media, resources, translations,
Text of the page (most frequently used words):
the (105), angular (86), module (58), downgraded (38), that (38), #downgrademodule (37), you (36), for (34), will (31), when (29), and (27), function (26), can (25), angularjs (24), change (24), upgrademodule (22), using (21), modules (21), detection (21), upgrade (21), application (19), not (18), this (17), component (16), more (15), run (15), hybrid (15), use (15), static (15), bootstrap (14), ngmodulefactory (14), class (13), ngmodule (13), testing (13), platformbrowser (12), each (12), are (12), extraproviders (11), root (11), from (11), const (10), staticprovider (10), shared (10), needs (10), pass (10), one (9), injectable (9), with (9), see (9), multiple (9), bootstrapped (9), manually (9), differences (9), performance (9), does (9), applications (9), part (9), platform (9), browser (9), ngmoduleref (9), used (9), instantiate (9), injector (8), bootstrapmodule (8), aria (8), details (7), promise (7), creating (7), instantiated (7), necessary (7), main (7), lazily (7), example (7), rootinjector (6), return (6), created (6), via (6), your (6), have (6), act (6), all (6), bootstrapmodulefactory (6), provide (6), them (6), associated (6), downgrading (6), possible (6), trigger (6), digest (6), their (6), upgrading (6), other (6), two (6), runs (6), only (6), changes (6), unlike (6), same (6), note (6), available (6), expected (6), type (6), either (6), routes (6), string (6), moduleorbootstrapfn (6), create (5), downgradecomponent (5), api (5), how (5), returns (5), deprecated (5), animations (5), common (5), cdk (5), developer (4), await (4), rootinjectorpromise (4), provided (4), downgradeinjectable (4), pieces (4), declare (4), dependency (4), argument (4), please (4), instead (4), reference (4), helper (4), demand (4), possibly (4), lite (4), region (4), google (3), code (3), getrootinjector (3), async (3), considered (3), consequence (3), new (3), instance (3), every (3), intention (3), providedin (3), want (3), some (3), injectables (3), among (3), platformbrowserdynamic (3), platformref (3), explicitly (3), things (3), keep (3), mind (3), downgrade (3), include (3), case (3), ngzone (3), rootscope (3), scope (3), apply (3), detailed (3), discussion (3), implications (3), side (3), try (3), tie (3), systems (3), tightly (3), restricting (3), explicit (3), cases (3), where (3), knows (3), inputs (3), improves (3), especially (3), heavy (3), but (3), leaves (3), notify (3), framework (3), needed (3), what (3), means (3), frequently (3), order (3), ensure (3), both (3), frameworks (3), properly (3), notified (3), about (3), inevitably (3), result (3), than (3), automatically (3), detected (3), inside (3), zone (3), besides (3), different (3), there (3), important (3), internal (3), between (3), affect (3), behavior (3), cannot (3), apart (3), rest (3), helpers (3), usual (3), build (3), services (3), until (3), has (3), been (3), instantiating (3), usage (3), notes (3), name (3), wrapper (3), resolving (3), called (3), array (3), extra (3), returned (3), providers (3), requires (3), once (3), requested (3), first (3), time (3), point (3), onwards (3), allows (3), loading (3), bootstrapping (3), having (3), pay (3), cost (3), front (3), uses (3), specific (3), user (3), visits (3), these (3), library (3), apps (3), support (3), aot (3), compilation (3), router (3), forms (3), core (3), menu (3), licensed (2), under (2), v22 (2), 日本語版 (2), community (2), downgradedng2amodule (2), downgradedng2bmodule (2), modulebfactory (2), compilemoduleasync (2), compiler (2), get (2), moduleafactory (2), moduleref (2), null (2), ng2bootstrapfn (2), mymainangularjsmodule (2), upgradecomponent (2), import (2), multi (2), param (2), basic (2), arrow_back (2), ssr (2), server (2), dynamic (2), localize (2), signals (2), http (2), apiリファレンス (2), super, powered, 2010, 2026, documentation, built, mit, style, license, 正體中文版, 简体中文版, 한국어, русский, türkçe, español, azərbaycanca, translations, roadmap, press, kit, resources, experts, devlibrary, report, issues, conduct, contribute, stack, overflow, github, discord, youtube, bluesky, formerly, twitter, blog, social, media, jump, downgradedng2cmodule, exampleappmodule, appmodule, ng2bmodule, ng2amodule, then, ng2rootmodule, let, mylazyangularmodulefactory, represents, mylazyangularmodule, would, omitted, directly, browsermodule, description, passing, トップに戻る, arrow_upward_alt, stable, version, setangularjsglobal, getangularjsglobal, window, globals, node, service, worker, init, compat, elements, rxjs, interop, testbed, selenium, webdriver, protractor, drag, drop, tree, toolbar, tabs, listbox, grid, combobox, accordion, マイグレーション, アップデートガイド, バージョン互換性, バージョニングとリリース, 拡張診断, エラー百科辞典, cliリファレンス, 開発に参加する, ロードマップ, more_horiz, 資料集, ガイド, close, skip, content,
Text of the page (random words):
uleref t string a helper function for creating an angularjs module that can bootstrap an angular module on demand possibly lazily when a downgraded component needs to be instantiated part of the upgrade static library for hybrid upgrade apps that support aot compilation it allows loading bootstrapping the angular part of a hybrid application lazily and not having to pay the cost up front for example you can have an angularjs application that uses angular for specific routes and only instantiate the angular modules if when the user visits one of these routes the angular module will be bootstrapped once when requested for the first time and the same reference will be used from that point onwards downgrademodule requires either an ngmodulefactory ngmodule class or a function ngmodulefactory if you pass an ngmodulefactory it will be used to instantiate a module using platformbrowser s bootstrapmodulefactory note this type of the argument is deprecated please either provide an ngmodule class or a bootstrap function instead ngmodule class if you pass an ngmodule class it will be used to instantiate a module using platformbrowser s bootstrapmodule function if you pass a function it is expected to return a promise resolving to an ngmoduleref the function is called with an array of extra providers that are expected to be available from the returned ngmoduleref s injector downgrademodule returns the name of the created angularjs wrapper module you can use it to declare a dependency in your main angularjs module example upgrade static ts lite module ts region basic how to for more details on how to use downgrademodule see upgrading for performance param moduleorbootstrapfn type t extraproviders staticprovider promise ngmoduleref t returns string usage notes apart from upgrademodule you can use the rest of the upgrade static helpers as usual to build a hybrid application note that the angular pieces e g downgraded services will not be available until the downgraded module has been bootstrapped i e by instantiating a downgraded component you cannot use downgrademodule and upgrademodule in the same hybrid application use one or the other differences with upgrademodule besides their different api there are two important internal differences between downgrademodule and upgrademodule that affect the behavior of hybrid applications unlike upgrademodule downgrademodule does not bootstrap the main angularjs module inside the angular zone unlike upgrademodule downgrademodule does not automatically run a digest when changes are detected in the angular part of the application what this means is that applications using upgrademodule will run change detection more frequently in order to ensure that both frameworks are properly notified about possible changes this will inevitably result in more change detection runs than necessary downgrademodule on the other side does not try to tie the two change detection systems as tightly restricting the explicit change detection runs only to cases where it knows it is necessary e g when the inputs of a downgraded component change this improves performance especially in change detection heavy applications but leaves it up to the developer to manually notify each framework as needed for a more detailed discussion of the differences and their implications see upgrading for performance you can manually trigger a change detection run in angularjs using scope apply or rootscope digest you can manually trigger a change detection run in angular using ngzone run downgrading multiple modules it is possible to downgrade multiple modules and include them in an angularjs application in that case each downgraded module will be bootstrapped when an associated downgraded component or injectable needs to be instantiated things to keep in mind when downgrading multiple modules each downgraded component injectable needs to be explicitly associated with a downgraded module see downgradecomponent and downgradeinjectable for more details if you want some injectables to be shared among all downgraded modules you can provide them as staticprovider s when creating the platformref e g via platformbrowser or platformbrowserdynamic when using bootstrapmodule or bootstrapmodulefactory to bootstrap the downgraded modules each one is considered a root module as a consequence a new instance will be created for every injectable provided in root via providedin if this is not your intention you can have a shared module that will act as act as the root module and create all downgraded modules using that module s injector example upgrade static ts lite multi shared module ts region shared root module function downgrademodule t moduleorbootstrapfn ngmodulefactory t string a helper function for creating an angularjs module that can bootstrap an angular module on demand possibly lazily when a downgraded component needs to be instantiated part of the upgrade static library for hybrid upgrade apps that support aot compilation it allows loading bootstrapping the angular part of a hybrid application lazily and not having to pay the cost up front for example you can have an angularjs application that uses angular for specific routes and only instantiate the angular modules if when the user visits one of these routes the angular module will be bootstrapped once when requested for the first time and the same reference will be used from that point onwards downgrademodule requires either an ngmodulefactory ngmodule class or a function ngmodulefactory if you pass an ngmodulefactory it will be used to instantiate a module using platformbrowser s bootstrapmodulefactory note this type of the argument is deprecated please either provide an ngmodule class or a bootstrap function instead ngmodule class if you pass an ngmodule class it will be used to instantiate a module using platformbrowser s bootstrapmodule function if you pass a function it is expected to return a promise resolving to an ngmoduleref the function is called with an array of extra providers that are expected to be available from the returned ngmoduleref s injector downgrademodule returns the name of the created angularjs wrapper module you can use it to declare a dependency in your main angularjs module example upgrade static ts lite module ts region basic how to for more details on how to use downgrademodule see upgrading for performance deprecated passing ngmodulefactory as the downgrademodule function argument is deprecated please pass an ngmodule class reference instead param moduleorbootstrapfn ngmodulefactory t returns string usage notes apart from upgrademodule you can use the rest of the upgrade static helpers as usual to build a hybrid application note that the angular pieces e g downgraded services will not be available until the downgraded module has been bootstrapped i e by instantiating a downgraded component you cannot use downgrademodule and upgrademodule in the same hybrid application use one or the other differences with upgrademodule besides their different api there are two important internal differences between downgrademodule and upgrademodule that affect the behavior of hybrid applications unlike upgrademodule downgrademodule does not bootstrap the main angularjs module inside the angular zone unlike upgrademodule downgrademodule does not automatically run a digest when changes are detected in the angular part of the application what this means is that applications using upgrademodule will run change detection more frequently in order to ensure that both frameworks are properly notified about possible changes this will inevitably result in more change detection runs than necessary downgrademodule on the other side does not try to tie the two change detection systems as tightly restricting the explicit change detection runs only to cases where it knows it is necessary e g when the inputs of a downgraded component change this improves performance especially in change detection heavy applications but leaves it up to the developer to manually notify each framework as needed for a more detailed discussion of the differences and their implications see upgrading for performance you can manually trigger a change detection run in angularjs using scope apply or rootscope digest you can manually trigger a change detection run in angular using ngzone run downgrading multiple modules it is possible to downgrade multiple modules and include them in an angularjs application in that case each downgraded module will be bootstrapped when an associated downgraded component or injectable needs to be instantiated things to keep in mind when downgrading multiple modules each downgraded component injectable needs to be explicitly associated with a downgraded module see downgradecomponent and downgradeinjectable for more details if you want some injectables to be shared among all downgraded modules you can provide them as staticprovider s when creating the platformref e g via platformbrowser or platformbrowserdynamic when using bootstrapmodule or bootstrapmodulefactory to bootstrap the downgraded modules each one is considered a root module as a consequence a new instance will be created for every injectable provided in root via providedin if this is not your intention you can have a shared module that will act as act as the root module and create all downgraded modules using that module s injector example upgrade static ts lite multi shared module ts region shared root module description a helper function for creating an angularjs module that can bootstrap an angular module on demand possibly lazily when a downgraded component needs to be instantiated part of the upgrade static library for hybrid upgrade apps that support aot compilation it allows loading bootstrapping the angular part of a hybrid application lazily and not having to pay the cost up front for example you can have an angularjs application that uses angular for specific routes and only instantiate the angular modules if when the user visits one of these routes the angular module will be bootstrapped once when requested for the first time and the same reference will be used from that point onwards downgrademodule requires either an ngmodulefactory ngmodule class or a function ngmodulefactory if you pass an ngmodulefactory it will be used to instantiate a module using platformbrowser s bootstrapmodulefactory note this type of the argument is deprecated please either provide an ngmodule class or a bootstrap function instead ngmodule class if you pass an ngmodule class it will be used to instantiate a module using platformbrowser s bootstrapmodule function if you pass a function it is expected to return a promise resolving to an ngmoduleref the function is called with an array of extra providers that are expected to be available from the returned ngmoduleref s injector downgrademodule returns the name of the created angularjs wrapper module you can use it to declare a dependency in your main angularjs module import browsermodule platformbrowser from angular platform browser import downgradecomponent downgrademodule upgradecomponent from angular upgrade static the function that will bootstrap the angular module when if necessary this would be omitted if we provided an ngmodulefactory directly const ng2bootstrapfn extraproviders staticprovider platformbrowser extraproviders bootstrapmodule mylazyangularmodule this angularjs module represents the angularjs pieces of the application const mymainangularjsmodule angular module mymainangularjsmodule we declare a dependency on the downgraded angular module downgrademodule ng2bootstrapfn or downgrademodule mylazyangularmodulefactory for more details on how to use downgrademodule see upgrading for performance usage notes apart from upgrademodule you can use the rest of the upgrade static helpers as usual to build a hybrid application note that the angular pieces e g downgraded services will not be available until the downgraded module has been bootstrapped i e by instantiating a downgraded component you cannot use downgrademodule and upgrademodule in the same hybrid application use one or the other differences with upgrademodule besides their different api there are two important internal differences between downgrademodule and upgrademodule that affect the behavior of hybrid applications unlike upgrademodule downgrademodule does not bootstrap the main angularjs module inside the angular zone unlike upgrademodule downgrademodule does not automatically run a digest when changes are detected in the angular part of the application what this means is that applications using upgrademodule will run change detection more frequently in order to ensure that both frameworks are properly notified about possible changes this will inevitably result in more change detection runs than necessary downgrademodule on the other side does not try to tie the two change detection systems as tightly restricting the explicit change detection runs only to cases where it knows it is necessary e g when the inputs of a downgraded component change this improves performance especially in change detection heavy applications but leaves it up to the developer to manually notify each framework as needed for a more detailed discussion of the differences and their implications see upgrading for performance you can manually trigger a change detection run in angularjs using scope apply or rootscope digest you can manually trigger a change detection run in angular using ngzone run downgrading multiple modules it is possible to downgrade multiple modules and include them in an angularjs application in that case each downgraded module will be bootstrapped when an associated downgraded component or injectable needs to be instantiated things to keep in mind when downgrading multiple modules each downgraded component injectable needs to be explicitly associated with a downgraded module see downgradecomponent and downgradeinjectable for more details if you want some injectables to be shared among all downgraded modules you can provide them as staticprovider s when creating the platformref e g via platformbrowser or platformbrowserdynamic when using bootstrapmodule or bootstrapmodulefactory to bootstrap the downgraded modules each one is considered a root module as a consequence a new instance will be created for every injectable provided in root via providedin if this is not your intention you can have a shared module that will act as act as the root module and create all downgraded modules using that module s injector let rootinjectorpromise promise injector null null const getrootinjector extraproviders staticprovider if rootinjectorpromise rootinjectorpromise platformbrowser extraproviders bootstrapmodule ng2rootmodule then moduleref moduleref injector return rootinjectorpromise const downgradedng2amodule downgrademodule async extraproviders staticprovider const rootinjector await getrootinjector extraproviders const moduleafa...
|