> For the complete documentation index, see [llms.txt](https://react-dsfr.codegouv.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://react-dsfr.codegouv.studio/publishing-a-npm-modules-that-depends-on-react-dsfr.md).

# Publishing a NPM modules that depends on react-dsfr

You want to publish your own library of components that depends on react-dsfr?

Here is an example:

{% embed url="<https://github.com/EIG6-Geocommuns/geocommuns-core>" %}
A module that depend on react-dsfr and MUI
{% endembed %}

I recommend starting from ts-ci for any project meant to be published on NPM

{% embed url="<https://github.com/garronej/ts-ci>" %}

The main takeway:

* [@codegouv/react-dsfr must be a peer dependency of your project](https://github.com/EIG6-Geocommuns/geocommuns-core/blob/55e015a453a681a12bfa84624ccfd243ce8a6150/package.json#L48). Any app that would use your library would need to explicitely install react-dsfr. [For devloppement purpose, you want to add @codegouvfr/react-dsfr as devDependencies of your project](https://github.com/EIG6-Geocommuns/geocommuns-core/blob/55e015a453a681a12bfa84624ccfd243ce8a6150/package.json#L56).
* Do not add `"postinstall": "react-dsfr  copy-static-assets"` in your library's package.json.&#x20;
* If you rely on MUI, `@mui/material` `@emotion/styled` and `@emotion/react` should be peer dependencies as well. You should add those modules as devDependencies.
* If you use TSS: react-dsfr dosen't need to be a peerDependencies but @emotion/react does, you do not configure the emotion cache in your lib, that's the the responsability of the host app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://react-dsfr.codegouv.studio/publishing-a-npm-modules-that-depends-on-react-dsfr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.