1# Compilation Toolchain Error Codes 2 3> **NOTE** 4> 5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md). 6 7## 10311001 Failed to Import ArkTS Files 8 9**Error Message** 10 11Importing ArkTS files in JS and TS files is forbidden. 12 13**Description** 14 15It is forbidden to import ArkTS files to JS or TS files. 16 17**Possible Causes** 18 19ArkTS files have been imported in JS and TS files. 20 21**Solution** 22 23Remove the import statements for ArkTS files from JS and TS files. 24 25## 10311002 Failed to Parse OhmUrl 26 27**Error Message** 28 29Failed to resolve OhmUrl. Failed to get a resolved OhmUrl for `${filePath}` imported by `${importerFile}`. 30 31**Description** 32 33Failed to resolve OhmUrl. Failed to obtain the parsed OhmUrl for ${filePath} imported by ${importerFile}. 34 35**Possible Causes** 36 37The ${pkgName} module to which ${filePath} belongs is configured incorrectly. 38 39**Solution** 40 411. Make sure the ${pkgName} module is correctly configured in the ${filePath} file. 422. Make sure the file name is correct, including its case sensitivity. 43 44## 10311003 Failed to Obtain the Kit Configuration File 45 46**Error Message** 47 48Kit `${moduleRequest}` has no corresponding config file in ArkTS SDK. 49 50**Description** 51 52The ${moduleRequest} kit does not have the corresponding configuration file in the ArkTS SDK. 53 54**Possible Causes** 55 561. The APIs of the kit are inconsistent with those in the SDK. 572. The APIs of the kit are modified locally. 58 59**Solution** 60 611. Make sure the kit API you are importing is consistent with the SDK version you are using, and the kit APIs are not modified locally. 622. For details about the kit APIs, see <!--RP1-->[API Reference Document Description](../development-intro.md).<!--RP1End--> 63 64## 10311005 Incorrect Kit Identifier 65 66**Error Message** 67 68Identifier `${this.importName}` comes from `${this.symbol.source}` which can not be imported in .ts file. 69 70**Description** 71 72The identifier ${this.importName} comes from ${this.symbol.source}. This identifier cannot be imported to a .ts file. 73 74**Possible Causes** 75 76An ArkTS file of the kit is imported to the TS file. 77 78**Solution** 79 80Remove the import statement or change the file name extension to .ets. 81 82## 10311006 Failed to Export Imported Names from the Kit 83 84**Error Message** 85 86`${importName}` is not exported from Kit `${KitInfo.getCurrentKitName()}`. 87 88**Description** 89 90Kit ${importName} is not exported from ${KitInfo.getCurrentKitName()}. 91 92**Possible Causes** 93 941. The APIs of the kit are inconsistent with those in the SDK. 952. The APIs of the kit are modified locally. 96 97**Solution** 98 991. Make sure the kit API you are importing is consistent with the SDK version you are using, and the kit APIs are not modified locally. 1002. For details about the kit APIs, see <!--RP1-->[API Reference Document Description](../development-intro.md).<!--RP1End--> 101 102## 10311007 Failed to Import or Export Kit Namespaces 103 104**Error Message** 105 106Namespace import or export of Kit is not supported currently. 107 108**Description** 109 110Currently, the namespace of a kit cannot be imported or exported. 111 112**Possible Causes** 113 114The file uses the namespace of the kit for import or export. 115 116**Solution** 117 118Replace the namespace import or export of the kit with a named import or export. Example: `import * as ArkTS from "@kit.ArkUI";` -> `import { AlertDialog } from "@kit.ArkUI";`; 119 120## 10311008 Kit Empty Import Error 121 122**Error Message** 123 124Can not use empty import(side-effect import) statement with Kit `${(kitNode.moduleSpecifier as ts.StringLiteral).text.replace(/'|"/g, '')}`. 125 126**Description** 127 128Empty import (side-effect import) statements cannot be used in Kit `${(kitNode.moduleSpecifier as ts.StringLiteral).text.replace(/'|"/g, '')}`. 129 130**Possible Causes** 131 132The empty import (side-effect import) statement of the kit is used in the file. 133 134**Solution** 135 136Specify the symbol to be imported. Example: `import "@kit.ArkUI";` -> `import { lang } from "@kit.ArkUI";` 137 138## 10311009 es2abc Execution Error 139 140**Error Message** 141 142Failed to execute es2abc. 143 144**Description** 145 146es2abc fails to be executed. 147 148**Possible Causes** 149 150An error occurred during the execution of es2abc. 151 152**Solution** 153 154Refer to the error codes of es2abc for troubleshooting. 155 156## 10311010 Lazy Import Re-export Error 157 158**Error Message** 159 160`${elementText}` of lazy-import is re-export. 161 162**Description** 163 164The lazy import of ${elementText} is re-exported. 165 166**Possible Causes** 167 168The lazy-imported ${elementText} lazy-imported is exported again. 169 170**Solution** 171 1721. Make sure lazily loaded named bindings are not re-exported. 1732. Check whether **autoLazyImport** is enabled. 174