Replies: 1 comment
-
Nevermind. I've gone the route of reducing the deps in the global CLI so that the config isn't brought in. That should get me fixed up. Scott |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm using nest-typed-config for a CLI project with nest-commander and in some instances, the globally installed CLI won't be in a project folder, which means there won't be a config file to parse. This causes nest-typed-config to fail. Would it be feasible to add an
ignoreFailedSearch
(or something similar) flag to the loaders? Currently I'd only need it in thefileLoader
, but I'd imagine if one loader gets it, all should have it?I can also more than likely get around this constraint, as I have a package of CLI commands which are also local to the project, and thus I could stick an extra config setup in there, but I was hoping to keep things simpler config-wise and the flag would help.
Scott
Beta Was this translation helpful? Give feedback.
All reactions