You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now untool deduces the rootDir from the found (from pwd and up) package.json.
From this process the configuration is loaded using cosmiconfig. This part is not overridable.
Problem
This behaviour is a bit too static.
The first issues arose during unit testing where we currently need to spawn the test in a separate process.
On a broader view this right now prevents integrating untool in a programatic way where the scope is not the current directory. E.g. initalize an untool instance as part of a program where the start-folder should not be the current directory.
Solution
It would be good to set the rootDir from outside and respect this during each and every initialize step (cosmiconfig, webpack, ...)
Current status
Right now
untool
deduces therootDir
from the found (from pwd and up)package.json
.From this process the configuration is loaded using cosmiconfig. This part is not overridable.
Problem
This behaviour is a bit too static.
The first issues arose during unit testing where we currently need to spawn the test in a separate process.
On a broader view this right now prevents integrating untool in a programatic way where the scope is not the current directory. E.g. initalize an untool instance as part of a program where the start-folder should not be the current directory.
Solution
It would be good to set the rootDir from outside and respect this during each and every initialize step (cosmiconfig, webpack, ...)
Additional Info
Moved from untool/untool#488
The text was updated successfully, but these errors were encountered: