This topic will address the issues encountered during the installation and setup of Eclipse for simulating and running OpenEMS, along with their resolutions.
During the installation and setup process, I encountered the following error. Does anyone have a solution for this issue, or will this error affect the program’s execution?
" Description
Resource Path Location
Type
Unnecessary @SuppressWarnings(“deprecation”)
TimeOfUseTariffController.java /io.openems.edge.controller.ess.timeofusetariff/src/io/openems/edge/controller/ess/timeofusetariff
line 14
Java Problem"
now in npm install -g @angular/cli
I am encountering this error, which indicates that the installer cannot locate the correct path for this file. What should be checked to resolve this issue?
Thank you for your guidance.
"[error] Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import
‘D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\build-angular\src\dev-server’
is not supported resolving ES modules imported from
D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\architect\node\node-modules-architect-host.js
Did you mean to import
“file:///D:/Programing_codes/GitHub/openems/ui/node_modules/@angular-devkit/build-angular/src/dev-server/index.js”?
at finalizeResolution (node:internal/modules/esm/resolve:251:11)
at moduleResolve (node:internal/modules/esm/resolve:913:10)
at defaultResolve (node:internal/modules/esm/resolve:1037:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:650:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:599:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:582:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:241:38)
at onImport.tracePromise.proto (node:internal/modules/esm/loader:542:36)
at TracingChannel.tracePromise (node:diagnostics_channel:337:14)
at ModuleLoader.import (node:internal/modules/esm/loader:541:21)
at defaultImportModuleDynamicallyForScript (node:internal/modules/esm/utils:230:31)
at importModuleDynamicallyCallback (node:internal/modules/esm/utils:252:12)
at eval (eval at loadEsmModule (D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\architect\node\node-modules-architect-host.js:235:14), :3:1)
at loadEsmModule (D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\architect\node\node-modules-architect-host.js:236:12)
at getBuilder (D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\architect\node\node-modules-architect-host.js:259:35)
at WorkspaceNodeModulesArchitectHost.loadBuilder (D:\Programing_codes\GitHub\openems\ui\node_modules@angular-devkit\architect\node\node-modules-architect-host.js:206:31)
"
After attempting to resolve the issue, I realized that this error occurs with the npm install command. It typically arises when installation is performed under different conditions or when the --force option is used to install a newer version of dependencies.
"To resolve this issue, you need to execute the following commands:
npm uninstall -g @angular/cli
npm cache clean --force
Then, re-run the following commands:
npm install -g @angular/cli
npm install