Skip to main content


The main goal of @pallad/config is to be helpful at every stage of application development.

Development for programmers

Configuration must be accessible in type-safe manner for typescript based codebase. That will limit amount of errors or bugs caused by typos or configuration misuse.

If you want to have an access to database configuration then you can be sure that config.database.username will be available. Moreover if you've protected that value with @pallad/secret then you can also be sure that config.database.username.getValue() will always work since typescript will tell you that username is a Secret object.

That's why we put a lot of effort to make @pallad/config as much type friendly as possible and allow your configuration shape to be precisely inferred.

Debugging for devops and programmers

Since configuration structure is easily available then CLI can analyze it and tell you very early if there is something wrong in it. That allows to ensure, even at continuous integration stage, that your configuration is valid or debug it in secure way.

That's the reason why configuration is defined in a function that can be called at any time without running the entire application.