Error: Cannot copy '../semver/bin/semver.js' to a subdirectory of itself

[BryanHunt]

If 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.

[ro0gr]

Same for me. Surprisingly it does also reproduce in GH Actions steps https://github.com/san650/ember-cli-page-object/runs/4800467424?check_suite_focus=true#step:5:30 🤔

using the latest [email protected]

[knownasilya]

Seeing this but with handlebars. Using yarn 1.

Can see here: nickschot/ember-gesture-modifiers#188
For me it did it after the first run, now I can't run try:each at all, even if I clear lockfile, node_modules and npm cache.

[knownasilya]

Looks like maybe it needs a change like

await fs.copy(source, destination);

to

await fs.copy(source, destination, {dereference: true});

[ro0gr]

FYI, For me downgrading to the [email protected] worked around this issue.

[oliverlangan]

We're also seeing it in our CI system.

[sly7-7]

For me it did it after the first run, now I can't run try:each at all, even if I clear lockfile, node_modules and npm cache.

@knownasilya I had the same problem here, trying to run ember try:one on ember-elsewhere. To make it work again, I have to manually rm .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

[jelhan]

I run into the same issue. For me it was solved as well by deleting .node_module.ember-try folder as described by @sly7-7.

[mansona]

I imagine this would be fixed if we ever went through with #598 🤔

[kategengler]

We should do #598 but this issue has also been fixed in #912

[mansona]

Ah so I guess the next big thing would be to get a release out 🤔 quite a few fixes ready to go. I'll start a conversation in #dev-ember-cli about this 👍

[grapho]

I'm getting this error as well.. but for an acorn package ... it appears the 3.0 beta fixed it