feat: restore resolving config from multiple paths and combine config discovery #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is better config discovery that isn't as confusing and cause issues like this.
Essentially now that we have workspaces, we can use the exact same rules for discovering deno.json files that we do for package.json files:
/home/david/project/node_modules/package/file.js
, then it should start discovery at/home/david/project/
. That way we don't cause errors about configs not being in a workspace for stuff in the node_modules folder and so we properly discover the project configs (and not stop at the first found package.json)This is a breaking change for some projects, but it's easy to work around by adding the config as part of the workspace and it will be better in the long term.