Lines Matching refs:dependencies
46 "dependencies": {
91 1. The module names used in imports are the aliases under **dependencies** in the **oh-package.json…
92 2. It is recommended that the alias under **dependencies** be the same as the values of **moduleNam…
123 "dependencies": {
148 "dependencies": {
173 "dependencies": {
198 "dependencies": {
214 "dependencies": {
230 "dependencies": {
269 "dependencies": {
287 …dependencies between modules are configured through **dependencies** in the **oh-package.json5** f…
288 …dependencies can be added to the dependency tree, participate in the build process, and finally ge…
311 …e of the module to dynamically import. It must be the same as the one specified under dependencies.
318 … the module to dynamically import. It must be the same as the one specified under **dependencies**.
342 "dependencies": {
378 "dependencies": {
406 "dependencies": {
434 "dependencies": {
496 "dependencies": {
531 …x, configuring their dependencies in DevEco Studio can be challenging and, if not handled carefull…
543 - When converting dependencies, you must transfer both **dependencies** and **runtimeOnly**.
556 "dependencies": {
581 "dependencies": {
627 The **dependencies** and **runtimeOnly** configurations of har1 on har2 are transferred to the HAP.…
631 "dependencies": {