bug report: Core.CopyFileError
Closed this issue · 4 comments
Command failed: npm run convert-to-single-host --if-present -- outlook
'npm' is not recognized as an internal or external command,
operable program or batch file.
stack:
CopyFileError: Command failed: npm run convert-to-single-host --if-present -- outlook
'npm' is not recognized as an internal or external command,
operable program or batch file.
at Object.CopyFileError (<REDACTED: user-file-path>:14:6061575)
at Function.doScaffolding (<REDACTED: user-file-path>:14:5832308)
at processTicksAndRejections (node:<REDACTED: user-file-path>:95:5)
at Function.generate (<REDACTED: user-file-path>:14:5829076)
at Function.<anonymous> (<REDACTED: user-file-path>:14:5903681)
at Coordinator.create (<REDACTED: user-file-path>:14:5406420)
at Coordinator.<anonymous> (<REDACTED: user-file-path>:14:5903681)
at Coordinator.<anonymous> (<REDACTED: user-file-path>:14:6067221)
at FxCore.createProject (<REDACTED: user-file-path>:14:5994987)
at FxCore.<anonymous> (<REDACTED: user-file-path>:14:5907557)
at FxCore.exports.ErrorHandlerMW (<REDACTED: user-file-path>:14:6071470)
at FxCore.<anonymous> (<REDACTED: user-file-path>:14:6067221)
Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.
@kharidukranthi Thanks for reporting, could you describe the reproduce step in details? Thanks.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.
Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.