Mark Stosberg

I think the comment above may be on to something: the `.ts` config files that are the cause. Trying `.js` config files may help. It's not clear how much typing...

Breaking changes can considered as part of different categories: 1. Already deprecated. No action needed. 2. Expected to be used a very small number of users. Document the change. 3....

@lorenwest I agree that "node-config shouldn't need a config", but I don't see that being proposed here. What I do see is a fresh approach that addresses whole categories of...

@iMoses Thanks for thinking through how an incremental approach might work in this. It sounds painful, and ultimately results in a breaking-change release anyway. +1 for getting on a call...

@iMoses Could you document the signature for validators? The docs for Parser.validators say that it is an "array of validators", but I didn't see the definition of validation. I presume...

@iMoses Validators are a great feature. Recently we had a significant bug in production that a validator could have caught. We needed logic to validate configuration: "If we disable the...

Those sound like good refinements. On Wed, Aug 7, 2019 at 5:07 AM iMoses wrote: > @markstos side-note: I'm still > experimenting and adjusting the API.. > > I decided...

As one of the maintainers, I can see there _is_ interest in refactoring the library's API. @iMoses proposed a number of interesting changes, so this large conversation got split into...

If TypeScript quit being able to transpile valid JavaScript, why don't you file a bug with TypeScript instead? From the second paragraph of the [TypeScript spec]:(https://stackoverflow.com/questions/20759532/is-any-javascript-code-a-valid-typescript-code) > TypeScript is a...

Hmm, When calling `config.get()`, it's important that `get` `binds `this` to the calling method of `config`. With ``` import { get } from 'config' ``` Then nothing is bound to...