[Bug]: `tsp compile --list-files` doesn't list files, if spec is outside current directory

[mikeharder]

Describe the bug

tsp compile --list-files doesn't list files, if the spec is outside the current directory. The compile itself seems to work fine, just the files are not listed.

Reproduction

If I run tsp compile --list-files on a spec under my current directory, it prints the files as expected:

~/specs-mh$ npx tsp compile --list-files specification/contosowidgetmanager/Contoso.Management
TypeSpec compiler v1.7.1

✔ Compiling
✔ @azure-tools/typespec-autorest 565ms specification/contosowidgetmanager/
    specification/contosowidgetmanager/resource-manager/Microsoft.Contoso/preview/2021-10-01-preview/contoso.json
    specification/contosowidgetmanager/resource-manager/Microsoft.Contoso/preview/2021-10-01-preview/examples/Operations_List.json
    ...
Compilation completed successfully.

However, if I run the same command on the same spec, but outside my current directory, no files are printed:

~/specs-mh$ npx tsp compile --list-files ../specs-mh-2/specification/contosowidgetmanager/Contoso.Management
TypeSpec compiler v1.7.1

✔ Compiling
✔ @azure-tools/typespec-autorest 529ms ../specs-mh-2/specification/contosowidgetmanager/

Compilation completed successfully.

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[timotheeguerin]

hhm so initially can't repro just by being in a different dir

[timotheeguerin]

ah I think this is due to the files being saved in a global varialbe which is different across instance of a library so when you load the example you have above it probably doesn't use the same compiler/emitter exact combo

[mikeharder]

ah I think this is due to the files being saved in a global varialbe which is different across instance of a library so when you load the example you have above it probably doesn't use the same compiler/emitter exact combo

You might have found the root cause, but if not, what might be specific about my scenario, is both the source and target folders had their own copies of node_modules in the root of the specs repo. Full repro steps would be something like:

1. clone specs repo to specs1
2. close specs repo again to specs2
3. run npm ci in the root of each specs repo
4. run npx tsv from specs1, to analyze a spec under specs2

[timotheeguerin]

yeah it was the issue above, I fixed it in #9320