open-index/open-npm huggingface dataset:
npm package: @sedoo/sedoo-doc-deploy
Description: Stupid CLI to deploy vuepress documentation on SEDOO CDN server
Author: SEDOO
Latest version: 0.0.2

Ce CLI permet d'uploader une documentation VuePress sur le CDN du SEDOO.

# Utilisation 

## Dépendance 

Le CLI s'ajoute dans les devDependencies du projet via la commande 

```
npm i @sedoo/sedoo-doc-deploy --save-dev
```

## Ajout du script

Dans la partie *scripts* du fichier *package.json*, il faut ajouter la ligne suivante

```
"scripts": {
        ...
        "docs:deploy": "node ./node_modules/@sedoo/sedoo-doc-deploy/index.js -p nomduprojet"
        ...
},
```

## Exécution

L'execution s'effectue via la commande ```npm run docs:deploy```

## URL de la documentation

La documentation est alors disponible à l'url suivante: https://api.sedoo/aeris-cdn-rest/documentation/v1_0/nomduprojet_en_minuscule
npm package: @sedoo/unidoo
Description: Commons components to simplify vuetify based application developement
Author: SEDOO
Latest version: 0.1.76

# unidoo

see [Documentation](https://sedoo.pages.in2p3.fr/unidoo)

## Library

## For users

### How to integrate Unidoo in a project

1. Install the module

```shell
npm i @sedoo/unidoo
```

2. In you main.js add the following lines

```
import { Unidoo, UnidooKeycloak } from "@sedoo/unidoo";
Vue.use(Unidoo, { vuetify, axios, iconfont: 'mdi' }); // à mettre après Vue.use(VueAxios, axios);
Vue.use(UnidooKeycloak, { axios }); // à mettre après Vue.use(VueAxios, axios);
```
NB :
- **Unidoo** : bibliothèque de composants vuetify
- **UnidooKeycloak** : wrapper keycloak

## For developers

### Warning

Naming convention: the main branch is called *main* and not *master*


### How to publish the library in NPM ?

The publishing of the library is automated by the Gitlab pipeline. No other method should be used.

Gitlab pipeline is triggering after each `git push --tags` on the main branch : 
- the documentation of the library is built and deployed as a gitlab page
- the library is built and deployed to [@sedoo/unidoo](https://www.npmjs.com/package/@sedoo/unidoo) npm registry

If the build is successful, the system will publish it on NPM using the version number indicated in the *package.json* file.
If this version corresponds to an already published version, the build will stop here. Else, the version is published.

Hence, to publish an new version, it is important to update the number in the *package.json* file.    

Tips to prevent errors in the publishing process in the pipeline:
- use the `npm run build --fix` command to test the build locally before pushing the code to the repository and fix the linting errors
- use the `npm run docs:build` command to test the documentation build locally before pushing the code to the repository
Nevertheless if the pipeline fails, check the logs in the Gitlab pipeline console to find the error :
Example of error : `error Unexpected console statement  no-console` means that there is a console.log() statement in the code.
Resolve action : Remove console.log. However if log are necessary a workaround can be to implement infoLog() and errorLog() functions in the code of the component (like in the UnidooMapGeoFeatures) to replace console.log() and console.error() statements.

Then run the demo locally like bellow to check that everything is ok before merging and pushing the code on the main branch of the repository:

## Demo application

### On developement station

To run the demo locally: 

```shell
npm run docs:dev
```

## Demonstration on the Web in Wordpress after publishing

[Live demonstration](https://sedoo.pages.in2p3.fr/unidoo)
npm package: @sedpro/cl-lib
Description: ## How to publish
Latest version: 0.0.27

# ClLib

## How to publish

* Add module
* Add export for this module in `projects/cl-lib/src/public-api.ts`
* Update version in `projects/cl-lib/package.json`
* Build library `ng build cl-lib --prod`
* Publish library to npm `cd dist/cl-lib && npm publish`

```
ng build cl-lib --prod
cd dist/cl-lib && npm publish
```

Details: https://angular.io/guide/creating-libraries

##Faq:

* `403 Forbidden - PUT https://registry.npmjs.org/@sedpro%2fcl-lib - You cannot publish over the previously published versions` -  rm node_modules and run `npm install` again