open-index/open-npm huggingface dataset:
npm package: @sissel/prettier-config
Description: Shared prettier config
Latest version: 1.2.5

## @sissel/prettier-config

This package includes the shareable Prettier configuration.

### Install

[pnpm](https://pnpm.js.org/en/cli/install)

```cli
pnpm add prettier @sissel/prettier-config --save-dev
```

> Prettier is an `optionalDependency` so you will need to install it within your project.

### Usage

We extend configuration from within `package.json` files.

```json
{
  "prettier": "@sissel/prettier-config"
}
```

### Text Editor (VSCode)

Install the [esbenp.prettier-vscode](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) extension from the marketplace. Depending on how your editor is configured, one may require setting global configuration in a user `settings.json` file:

```jsonc
{
  "[json]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[markdown]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  }
}
```

### Ignored Files

I do not leverage prettier for various file types because it is extremely opinionated and conflicts with my code style, especially that found in JavaScript and TypeScript based projects. In almost all projects a `.prettierignore` file is included to prevent prettier from wreaking utter havoc in my development workspaces. Below is standard ignores asserted:

```
*.toml
*.mjs
*.js
*.ts
*.css
*.scss
*.liquid
*.html
```

### License

[MIT](#LICENSE)
npm package: @sissel/rollup-config
Description: Shared rollup configuration.
Latest version: 1.2.0

# @sissel/rollup-config

Shareable rollup configuration. The module acts as an interface, it exports an instance of Rollup and several plugins that are frequently used by me. Plugins are exposed using getters to better help negate the referencing factor involved in cases where certain projects only require certain plugins.

# Install

[Rollup](https://rollupjs.org/guide/en/) and [ESBuild](https://esbuild.github.io/) exist as a peer dependency. [PostCSS](https://postcss.org/), [AutoPrefixer](https://autoprefixer.github.io/) and [TypeScript](https://typescriptlang.org/) exist as optional dependencies. Install them when you require the plugins related.

```cli
pnpm add @sissel/rollup-config -D
```

# Usage

This is an ESM module, so rollup config files must use a `.mjs` extension (eg: `rollup.config.mjs`) or else Node will complain. The `rollup()` export is totally optional, its a re-export of `defineConfig` and used to provide type completions.

<!-- prettier-ignore -->
```ts
import { rollup, env, plugin } from "@sissel/rollup-config";

export default rollup(
  {
    input: "src/file.ts",
    output:   {
      format: 'cjs',
      dir: 'package',
      sourcemap: env.is('dev', 'inline'), // Inline sourcemap in development else false
      interop: 'default'
    },
    plugins: env.if('div')(
      [
        plugin.commonjs(options: {}),
        plugin.esbuild(options: {}),
        // etc etc
      ]
    )(
      [
        plugin.esminify()
      ]
    )
  }
);
```

### Rollup + ESBuild

This package is using ESBuild together will Rollup. TypeScript and JavaScript modules are processed with [esbuild](https://esbuild.github.io/) using [rollup-plugin-esbuild](https://github.com/egoist/rollup-plugin-esbuild).

> **Note** Rollup will inevitably die out as ESBuild starts to become the standard.

### Utilities Helper

The configuration is using [@brixtol/rollup-utils](https://github.com/BRIXTOL/rollup-utils) as a helper module. I maintain this in my work organization.

### License

[MIT](#LICENSE)
npm package: @sissel/stylelint-config
Description: Shared stylelint config
Latest version: 1.2.4

## @sissel/stylelint-config

This package includes the shareable Stylelint configuration.

### Install

[pnpm](https://pnpm.js.org/en/cli/install)

```cli
pnpm add stylelint @sissel/stylelint-config --save-dev
```

> [Stylelint](https://stylelint.io/) is an `peerDependency` so you will need to install it within your project.

### Usage

We extend configuration from within `package.json` files.

```json
{
  "stylelint": {
    "extends": "@sissel/stylelint-config",
    "ignoreFiles": ["**/node_modules"]
  }
}
```

### Text Editor (VSCode)

Install the [stylelint.vscode-stylelint](https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint) extension from the marketplace. Depending on how your editor is configured, one may require setting global configuration in a user `settings.json` file:

```jsonc
{
  "stylelint.validate": ["scss", "sass", "less", "postcss"],
  "stylelint.packageManager": "pnpm",
  "stylelint.enable": true,
  "scss.validate": false, // important to disable vscode validation
  "scss.scannerExclude": ["**/.git", "**/node_modules"],
  "editor.codeActionsOnSave": {
    "source.fixAll.stylelint": true
  }
}
```

### License

[MIT](#LICENSE)
npm package: @sissel/tsconfig
Description: Shared typescript config
Latest version: 1.0.0

# @sissel/tsconfig

This package includes a shareable TypeScript configuration which I use and referenced within various TypeScript packages via the `extends` option of a `tsconfig.json` file.

# Install

```cli
pnpm add @sissel/tsconfig typescript -D
```

> Include `typescript` as we need to reference it directly in most packages.

# Usage

Provide to the `extends` option within a `tsconfig.json`

```json
{
  "extends": "@sissel/tsconfig"
}
```
npm package: @sissijs/smolyaml
Description: SmolYAML implements a small minimalistic subset of the YAML specification.
Author: Lea Rosema
Latest version: 1.0.0

# SmolYAML

SmolYAML is a minimalistic parser for YAML-like data.

YAML is a [complex spec](https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell).

An `npm install yaml` weighs about 100kb of minified JavaScript.

SmolYAML is used in a static site generator that tries tries to be as minimalistic as possible.
That static site generator depends on YAML for parsing frontmatter, a block of meta data in template files.
But including the full YAML implementation would quite bloat it.

SmolYAML tries to address that by implementing only a small subset of the specification. To be fair,
it's an opinionated one that is (opinionatedly) considered good enough to parse frontmatter meta data.

In roughly 2KB of minified JavaScript.

## Usage

```sh
npm i @sissijs/smolyaml
```

```js
import { smolYAML } from '@sissijs/smolyaml';

const metadata = `
name: Lea
description: Lea is a Web Developer
age: 42
details:
  frontend: She loves doing Front of the Frontend work
  fullstack: But she really hates being called a fullstack developer
`

console.log(smolYAML(metadata));
```

## Limitations

- Right now, multi-line string values aren't supported.
- Only a parser is provided.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-active
Description: Library of sistema ser which support active DT module
Author: Cristian David Alfonso
Latest version: 0.0.1-alpha.33

# UniandesSistemaserActive

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-active` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-active`.
> Note: Don't forget to add `--project uniandes-sistemaser-active` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-active` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-active`, go to the dist folder `cd dist/uniandes-sistemaser-active` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-active` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-authorization
Description: Library of sistema ser which support authorization module
Author: Rafal Rueda - ro.rueda@uniandes.edu.co
Latest version: 0.0.1-alpha.5

# UniandesSistemaserAuthorization

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-authorization` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-authorization`.
> Note: Don't forget to add `--project uniandes-sistemaser-authorization` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-authorization` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-authorization`, go to the dist folder `cd dist/uniandes-sistemaser-authorization` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-authorization` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-conceptualization
Description: Library of sistema ser which support conceptualization module
Author: Rafal Rueda - ro.rueda@uniandes.edu.co
Latest version: 0.0.1-alpha.14

# UniandesSistemaserConceptualization

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-conceptualization` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-conceptualization`.
> Note: Don't forget to add `--project uniandes-sistemaser-conceptualization` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-conceptualization` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-conceptualization`, go to the dist folder `cd dist/uniandes-sistemaser-conceptualization` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-conceptualization` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-pagination
Description: Library of sistema ser which support pagination module
Author: Cristian David Alfonso
Latest version: 0.0.1-alpha.8

# UniandesSistemaserPagination

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-pagination` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-pagination`.
> Note: Don't forget to add `--project uniandes-sistemaser-pagination` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-pagination` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-pagination`, go to the dist folder `cd dist/uniandes-sistemaser-pagination` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-pagination` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-period
Description: Library to use the period name and combo functionality
Author: Jonatan Parra Jimenez
Latest version: 0.0.1-alpha.32

# UniandesSistemaserPeriod

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-period` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-period`.
> Note: Don't forget to add `--project uniandes-sistemaser-period` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-period` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-period`, go to the dist folder `cd dist/uniandes-sistemaser-period` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-period` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-response
Description: Library of sistema ser which manages pagination
Author: Rafal Rueda - ro.rueda@uniandes.edu.co
Latest version: 0.0.1-alpha.16

# UniandesSistemaserResponse

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project uniandes-sistemaser-response` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project uniandes-sistemaser-response`.
> Note: Don't forget to add `--project uniandes-sistemaser-response` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build uniandes-sistemaser-response` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build uniandes-sistemaser-response`, go to the dist folder `cd dist/uniandes-sistemaser-response` and run `npm publish`.

## Running unit tests

Run `ng test uniandes-sistemaser-response` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @sistemaser-uniandes-angular/uniandes-sistemaser-routing-lib
Description: Library of sistema ser which support routing in micro frontends
Author: Rafal Rueda - ro.rueda@uniandes.edu.co
Latest version: 0.0.1-alpha.1

# RoutingLib

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

## Code scaffolding

Run `ng generate component component-name --project routing-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project routing-lib`.
> Note: Don't forget to add `--project routing-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build routing-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build routing-lib`, go to the dist folder `cd dist/routing-lib` and run `npm publish`.

## Running unit tests

Run `ng test routing-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.