Error: Cannot copy '../semver/bin/semver.js' to a subdirectory of itself
See original GitHub issueIf you run test:ember-compatibility
more than once, it fails with the following:
Error!
Error: Cannot copy '../semver/bin/semver.js' to a subdirectory of itself, '../semver/bin/semver.js'.
Error: Cannot copy '../semver/bin/semver.js' to a subdirectory of itself, '../semver/bin/semver.js'.
at /home/*****/*****/e4a/node_modules/fs-extra/lib/copy/copy.js:210:21
at FSReqCallback.oncomplete (node:fs:188:23)
Steps to reproduce:
ember addon e4a
cd e4a
npm install
npm run test:ember-compatibility
num run test:ember-compatibility
I had a co-worker try the same steps and he got the same error.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:10
- Comments:6
Top Results From Across the Web
Error: Cannot copy to a subdirectory of itself #708 - GitHub
I am having this same problem on Ubuntu 20.04.1, node v14.9.0, fs-extra v9.0.1. fs.copy(src, dest). Error: Cannot copy '.
Read more >cannot move to a subdirectory of itself - Server Fault
I want to move and overwrite all of the files from tmp into the main folder. I am currently using: mv -f /home/sphinx/tmp/articlesdb ......
Read more >Bash move * to subfolder fail: cannot move to a subdirectory of ...
It will move all the files from the folder to the subfolder without any errors. Share.
Read more >elementary/houston - Gitter
I'm using encryption on both disks (ecryptfs on hdd, LVM with sda_crypt on /) disks, sometimes it breaks up due to too big...
Read more >Go Modules Reference - The Go Programming Language
See Semantic Versioning 2.0.0 for details on how versions are formatted, ... or if two or more modules provide the package, the go...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, For me downgrading to the ember-try@1.4.0 worked around this issue.
@knownasilya I had the same problem here, trying to run
ember try:one
on ember-elsewhere. To make it work again, I have to manuallyrm .node_modules.ember-try package-lock.json.ember-try package.json.ember-try
Seems like the “cleanup” (or the revert to the “initial state” of dependencies is not done correctly after running ember try.Also, the buggy behavior is independent from running with yarn 1 or npm