Leo Farias

> Happy to take a look for you too if you need, just lmk Its solved for now...

@mrgnhnt96, I will leave this open for now. We might have to put the legacy configuration generation behind a flag. But I am not 100% sure yet.

@saibotma This is because fvm is looking for a config and a pubspec to determine the configuration; this helps with constraints and dependency checking. I was able to replicate this...

I followed the initial instructions which caused the behavior I described. Will mark as a bug based on the information you provided so I can take a look.

@krispypen this issue is related to windows as it works in Mac based on the initial comment. You need to have a pubspec at the root of the monorepo.

I was able to replicate the issue mentioned by @saibotma

@saibotma I was able to reproduce, but than noticed that .fvmrc was not setup on the root of the project. If the root of the project, has a pubspec.yaml. One...

I added a warning if this happens on the latest version. I wonder if there was a .fvmrc in the sub1 on the Mac.

@JulianBissekkou, good question. The main issue that this resolves is by being explicit about the root directory you want to resolve the file from. There were many cases where .fvmrc...

@JulianBissekkou can you open an issue from this, so I can revisit?