Skip to main content
Version: 2.7.0


Configuring providers

You'll have noticed that our providers url option only contains the url fragment, not the full url. This was made intentionally. We are delegating the configuration of the API baseUrl to another piece, normally closer to the application, which is able to read some configuration, as environment variables, etc.

Doing it in this way also allows to better reuse our providers, so we could even publish them to independent packages and reuse them across many applications, acting as "api clients".

Using the providers object.

The Data Provider library give to us an utility for configuring groups of providers at a time (read the providers API page for further info).

Let's use it to set the baseUrl option of all our providers of type axios (created using the @data-provider/axios addon).

import { providers } from "@data-provider/core";

baseUrl: "http://localhost:3100" // Here will be listening json-server

The @data-provider/axios addon automatically adds the "axios" tag to all providers created.

The providers.config method works for already instantiated providers, and also for providers instantiated in the future, so it does not matter if we first import the config.js file, or the data/todos.js file. This is a very important detail, because the "app" does not need to know about specific providers, and the providers don't need to know about the base configuration, which boost the reusability. This is the reason why Data Provider gives to us a "tag based configuration system".

Source code


import { providers } from "@data-provider/core";

baseUrl: "http://localhost:3100"