save error, but saves ... about nconf HOT 5 CLOSED

This sounds like a bug. I'll look into it.

from nconf.

Okay, I got it.

nconf has this concept of "stores", or different places to load, save, get/set, etc., configurations. One of these is 'system', which is an abstraction of command line arguments.

When you save your configuration, it does so for all the stores, including the 'system' store, for which saving makes no sense. However, for your 'file' store it works fine. Hence, you see an error but it still saves.

This is technically pretty easy to fix, so I should have one out later today.

from nconf.

coool josh ... thks for your fast advice ...

from nconf.

This is fixed in [email protected] if you try to save when you have a store which has no .save() or .saveSync() methods, we will not throw an error, we will just ignore it and not save.

from nconf.

yup, now works !

thks !

from nconf.