hvigor ERROR: project.getModuleDir is not a function HarmonyOS 鸿蒙Next

hvigor ERROR: project.getModuleDir is not a function HarmonyOS 鸿蒙Next 为什么会出现> hvigor ERROR: project.getModuleDir is not a function的报错?

G:\software\nodejs16\node.exe C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules@ohos\hvigor\bin\hvigor.js -p product=default clean --debug --parallel --incremental --enable-build-script-type-check --daemon

hvigor DEBUG default Daemon process will change 46c8c128264234726b93532a70db5651a778c402 info with

{“pid”:1296,“state”:“stopReq”,“address”:“127.0.0.1”,“cwdPath”:“D:\workspace\AllTester4”,“hvigorVersion”:“3.0.9”,“keyId”:“46c8c128264234726b93532a70db5651a778c402”,“nodeParams”:“e31dfdc15710d70251b68f3b2f632782”,“nodeVersion”:“v16.19.1”,“port”:45000,“lastUsedTime”:1708237039319,“createdBy”:“deveco”,“sessionId”:“00000050d3eb9e06672cdd3d9ac5da16364266d0b5d9dc8e2b5b807d04bf02eda06cfa56334cc0adc28c104b9b2ac21011dc4d2df9facf44f4dbea6fac339ba73aef1dc381b63953e8e3d7b53c17f61b3cfbb857248f680e1b7b49c02c14913c”} in registry.

hvigor DEBUG default client data: { debug: true, parallel: true, prop: [ ‘product=default’ ], enableBuildScriptTypeCheck: true, incremental: true, _: [ ‘clean’ ], daemon: true }.

hvigor DEBUG default build start.

hvigor DEBUG default Daemon process will change 46c8c128264234726b93532a70db5651a778c402 info with

{“pid”:1296,“state”:“busy”,“address”:“127.0.0.1”,“cwdPath”:“D:\workspace\AllTester4”,“hvigorVersion”:“3.0.9”,“keyId”:“46c8c128264234726b93532a70db5651a778c402”,“nodeParams”:“e31dfdc15710d70251b68f3b2f632782”,“nodeVersion”:“v16.19.1”,“port”:45000,“lastUsedTime”:1708237039322,“createdBy”:“deveco”,“sessionId”:“00000050d3eb9e06672cdd3d9ac5da16364266d0b5d9dc8e2b5b807d04bf02eda06cfa56334cc0adc28c104b9b2ac21011dc4d2df9facf44f4dbea6fac339ba73aef1dc381b63953e8e3d7b53c17f61b3cfbb857248f680e1b7b49c02c14913c”} in registry.

hvigor DEBUG hvigor env: hvigorVersion=3.0.9

hvigor DEBUG hvigor-init Hvigor init with startParameters:{ hvigorfileTypeCheck: true, parallelExecution: true, incrementalExecution: true, printStackTrace: false, daemon: true, logLevel: Level { level: 10000, levelStr: ‘DEBUG’, colour: ‘cyan’ } }

hvigor DEBUG hvigor-init Cache service initialization finished in 1 ms

hvigor DEBUG configuration hvigorfile, resolving D:\workspace\AllTester4\hvigorfile.ts

hvigor DEBUG configuration hvigorfile, require result:
{ default: { system: [Function: appTasks], plugins: [], getModuleDir: [Function: getModuleDir] } }

hvigor DEBUG configuration hvigorfile, binding system plugins [Function: appTasks]

hvigor DEBUG hvigor-process hvigor build process will be closed with an error.

hvigor ERROR: project.getModuleDir is not a function

hvigor DEBUG hvigor-process ERROR: stacktrace = TypeError: project.getModuleDir is not a function

at new AppPlugin (D:\workspace\node_modules@ohos\hvigor-ohos-plugin\src\plugin\app-plugin.js:25:74) at Function.getAppPlugin (D:\workspace\node_modules@ohos\hvigor-ohos-plugin\src\plugin\factory\plugin-factory.js:18:16) at appTasks (D:\workspace\node_modules@ohos\hvigor-ohos-plugin\index.js:46:54) at bindSystemPlugins (C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\internal\lifecycle\configuration.js:1:2762) at evaluateNodeVigorFile (C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\internal\lifecycle\configuration.js:1:4986) at configuration (C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\internal\lifecycle\configuration.js:1:1262) at start (C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\boot\index.js:1:1950) at boot (C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\boot\index.js:1:1695) at C:\Users\jichunxiang.hvigor\project_caches\51881010c49be65805a24b786b95a4fb\workspace\node_modules.pnpm@ohos+hvigor@3.0.9\node_modules@ohos\hvigor\src\base\daemon\socket\daemon-server-socket-listener-registry.js:1:3538

hvigor ERROR: BUILD FAILED in 9 ms

hvigor DEBUG hvigor-process hvigor build process will be closed.

hvigor DEBUG default The process timeout timer will be reset.

hvigor DEBUG default Daemon process will change 46c8c128264234726b93532a70db5651a778c402 info with

{“pid”:1296,“state”:“half_busy”,“address”:“127.0.0.1”,“cwdPath”:“D:\workspace\AllTester4”,“hvigorVersion”:“3.0.9”,“keyId”:“46c8c128264234726b93532a70db5651a778c402”,“nodeParams”:“e31dfdc15710d70251b68f3b2f632782”,“nodeVersion”:“v16.19.1”,“port”:45000,“lastUsedTime”:1708237039323,“createdBy”:“deveco”,“sessionId”:“00000050d3eb9e06672cdd3d9ac5da16364266d0b5d9dc8e2b5b807d04bf02eda06cfa56334cc0adc28c104b9b2ac21011dc4d2df9facf44f4dbea6fac339ba73aef1dc381b63953e8e3d7b53c17f61b3cfbb857248f680e1b7b49c02c14913c”} in registry.

hvigor DEBUG default end time: 16 ms

Process finished with exit code -1


更多关于hvigor ERROR: project.getModuleDir is not a function HarmonyOS 鸿蒙Next的实战教程也可以访问 https://www.itying.com/category-93-b0.html

3 回复

getModuleDir返回值与getInstance期望的值是否一致?

更多关于hvigor ERROR: project.getModuleDir is not a function HarmonyOS 鸿蒙Next的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


getInstance是哪个上面的方法?
getModuleDir这个编译就报错了,

hvigor ERROR: project.getModuleDir is not a function 是鸿蒙Next开发环境中使用hvigor构建工具时可能遇到的错误。project.getModuleDir 是一个用于获取模块目录的方法,如果出现该错误,通常是由于以下原因之一:

  1. hvigor版本不兼容:当前使用的hvigor版本可能不支持project.getModuleDir方法,或者该方法已被弃用或修改。建议检查hvigor的版本是否符合鸿蒙Next的要求。

  2. 项目配置问题:项目的hvigor配置文件(如hvigorfile.tshvigorfile.js)可能存在语法错误或配置缺失,导致project.getModuleDir无法正确调用。

  3. 模块定义错误:项目中的模块定义可能不正确,导致project对象无法识别getModuleDir方法。检查模块定义文件(如module.json5)是否符合规范。

  4. SDK或工具链问题:鸿蒙Next的SDK或工具链可能存在不兼容或未更新的问题,导致project.getModuleDir无法正常工作。

解决方法包括:

  • 确保hvigor版本与鸿蒙Next兼容。
  • 检查项目配置文件,确保语法和配置正确。
  • 验证模块定义文件是否符合规范。
  • 更新SDK和工具链至最新版本。
回到顶部