Error Message
No Subdirectories.
Symptom
No subdirectories are found.
Possible Causes
The local node_modules directory does not contain subdirectories.
Solution
Check the node_modules directory and ensure that valid subdirectories exist.
Error Message
Not Found Attribute Name.
Symptom
The artifactType attribute is not found.
Possible Causes
The artifactType attribute is not found in the package.json configuration file.
Solution
Ensure that the artifactType attribute exists in the package.json file.
Error Message
Invalid Rule Type.
Symptom
The rule type is invalid.
Possible Causes
ruleType corresponding to the attrName attribute is not found during configuration verification.
Solution
Ensure that ruleType exists in the configuration being verified.
Error Message
Not Found Constants.PackageJson.
Symptom
The package.json file is not found.
Possible Causes
The specified rule type does not exist in the configuration being verified.
Solution
Check the directory and ensure that the package.json file exists in the npm package.
Error Message
Convert Package Failed.
Symptom
Failed to convert the package.
Possible Causes
Required fields are missing in the package.json configuration file of the npm package.
Solution
Check the package.json file in the npm package to ensure that all required fields exist and their values comply with the specified requirements. For details about the fields, see oh-package.json5.
Error Message
Configure Node Modules Error.
Symptom
The node_modules directory is incorrectly configured.
Possible Causes
The node_modules directory is incorrectly configured for conversion in local mode.
Solution
Configure the correct node_modules directory to ensure successful conversion.