From 573dda3b738bd9abe34f50fc29cb4ad6bee0c43e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Val=C3=A9rian=20Rousset?= Date: Mon, 13 May 2024 10:42:53 +0200 Subject: [PATCH] Update docs/CONTRIBUTING.md Co-authored-by: Julien Vignoud <33122365+JulienVig@users.noreply.github.com> --- docs/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index ed1835c31..6e1ab4721 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -145,7 +145,7 @@ Similarly to the server, any file ending with `.spec.ts` will be ran in the test `discojs` contains the core, platform-agnostic code of Disco.js, used by both `discojs-web` and `discojs-node`. As such, contributions to `discojs` must only contain code independent of either Node or the browser. As the names subtly suggest, `discojs-node` and `discojs-web` implement features specific to Node.js and browsers respectively, mostly related to memory and data handling as browser don't allow access to the file system. Currently, the `discojs-node` project is available as the `@epfml/discojs-node` NPM package, which can be installed with -`npm i @epfml/discojs-node` while the `discojs-web` project is available as the `@epfml/discojs` (and **not** as `@epfml/discojs-web`) NPM package, which can be installed with `npm i @epfml/discojs`. +`npm i @epfml/discojs-node` and the `discojs-web` as the `@epfml/discojs-web`. ## Contributing conventions