open-index/open-npm huggingface dataset:
npm package: @solcial.io/solana-client
Description: Solcial solana client SDK
Author: Solcial Developers
Latest version: 1.1.1

# Solcial library

Minimal library to absctract Solcial interaction with the Solana blokchain.

- User token minting
- User swap pool creation
- Trade function and price utility for users token
- List user NFT

This library use the `spl-token 0.1.8` beacause `"@raydium-io/raydium-sdk": "^1.1.0-beta.7"`

## Run test and bin

A basic test file is present simply run `npm test`

```bash
# run gloabl test files
npm test
# Do a swap on existing user pool
npm run test-dev
# Check price function outputs
npm run test-prices
# Run script in /bin
cd bin
npm run build
npx ts-node list-user-nft.ts
npx ts-node list-users-from-pools.ts
```
npm package: @solcial.io/solana-mobile-client
Description: Solcial solana client SDK
Author: Solcial Developers
Latest version: 0.4.4

# Solcial library

Minimal library to absctract Solcial interaction with the Solana blokchain.

- User token minting
- User swap pool creation
- Trade function and price utility for users token
- List user NFT

This library use the `spl-token 0.1.8` beacause `"@raydium-io/raydium-sdk": "^1.1.0-beta.7"`

## Run test and bin

A basic test file is present simply run `npm test`

```bash
# run gloabl test files
npm test
# Do a swap on existing user pool
npm run test-dev
# Check price function outputs
npm run test-prices
# Run script in /bin
cd bin
npm run build
npx ts-node list-user-nft.ts
npx ts-node list-users-from-pools.ts
```
npm package: @solcial.io/spl-token-swap
Description: The Token-swap JavaScript library comprises:
Latest version: 0.2.1-beta-2

# Token-swap JavaScript API

The Token-swap JavaScript library comprises:

* A library to interact with the on-chain program
* A test client that exercises the program
* Scripts to facilitate building the program

## Getting Started

First fetch the npm dependencies, including `@solana/web3.js`, by running:
```sh
$ npm install
```

### Build the on-chain program

```sh
$ npm run build:program
```

### Run the test client

```sh
$ npm run start-with-test-validator
```
npm package: @solcre-org/admin-panels
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 18.3.4

# AdminPanelsLibrary

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

## Code scaffolding

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

## Build

Run `ng build admin-panels-library` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

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

## Running unit tests

Run `ng test admin-panels-library` 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: @solcre-org/core
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.2.0.
Latest version: 18.0.18

# CoreLibrary

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test core-library` 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: @solcre-org/core-ui
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.
Latest version: 2.26.7

# CoreUiLibrary

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.

## LLM docs (published in npm)

This package publishes LLM-friendly docs under `llm/` in the npm output.

- Entry point: `llm/llms.txt`
- Component docs: `llm/components/`
- Recipes and blueprints: `llm/form-recipes.md`, `llm/screen-blueprints.md`
- Prompt bundle script (repo): `npm run llm:prompt`
- Update LLM docs from demo (repo): `npm run llm:update`

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build core-ui-library
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:

   ```bash
   cd dist/core-ui-library
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
npm package: @solcre-org/next-core-library
Description: Este repositorio contiene la **implementación base del core de Columnis**, desarrollada en [Next.js](https://nextjs.org/).
Latest version: 1.13.2

# 🚀 Columnis Core – Next.js

Este repositorio contiene la **implementación base del core de Columnis**, desarrollada en [Next.js](https://nextjs.org/).

> Este proyecto es el punto de partida para cualquier sitio Columnis. Si deseas crear un nuevo sitio, **debes forkar este repositorio** y seguir las convenciones documentadas aquí.

---

## 📚 Tabla de Contenidos

- [Introducción](#introducción)
- [Estructura del Proyecto](#estructura-del-proyecto)
- [Guías por Carpeta](#guías-por-carpeta)
- [Buenas Prácticas](#buenas-prácticas)
- [Scripts de Desarrollo](#scripts-de-desarrollo)

---

## 🧭 Introducción

El core proporciona:
- Parsers reutilizables
- Interfaces tipadas
- Configuraciones centralizadas
- Componentes desacoplados
- Tipos compartidos

---

## 🏗️ Estructura del Proyecto

```bash
/src
├── config/
├── parsers/
├── interfaces/
├── types/
├── components/
├── services/
├── middlewares/
├── utils/
├── styles/
├── app/
├── cache/
├── helpers/
```

---

## 📁 Guías por Carpeta

- [`src/parsers`](src/parsers/README.md)
- [`src/interfaces`](src/interfaces/README.md)
- [`src/types`](src/types/README.md)
- [`src/components`](src/components/README.md)
- [`src/config`](src/config/README.md)
- [`src/services`](src/services/README.md)
- [`src/middlewares`](src/middlewares/README.md)
- [`src/utils`](src/utils/README.md)
- [`src/app`](src/app/README.md)
- [`src/styles`](src/styles/README.md)
- [`src/cache`](src/cache/README.md)
- [`src/helpers`](src/helpers/README.md)

---

## ✅ Buenas Prácticas

- Tipar todo correctamente
- Aislar lógica en parsers
- Centralizar configuración
- Dividir componentes core y site

---

## 🛠️ Scripts de Desarrollo

| Comando         | Descripción              |
|----------------|---------------------------|
| `npm run dev`  | Inicia entorno local      |
| `npm run build`| Compila para producción   |
| `npm run start`| Ejecuta servidor Next.js  |
npm package: @solcre-org/ng-auth
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.1.3.
Latest version: 2.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# NgAuth

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test ng-auth` 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 README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @solcre-org/ng-core
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.1.3.
Latest version: 2.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# NgCore

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test ng-core` 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 README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @solcre-org/ng-pusher
Description: Solcre library to package all the functionalities of PusherJS.
Latest version: 1.0.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# NgPusher
Solcre library to package all the functionalities of PusherJS.

## Init
Import in module.ts the NgPusher module.
``` js
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';

import { AppComponent } from './app.component';
import { NgPusherModule } from '@solcre-org/ng-pusher';

@NgModule({
  declarations: [AppComponent],
  imports: [
	BrowserModule,
	NgPusherModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }
```

Put this code in app_initializer or before pusherjs code

``` js
...
this.pusherService.createClient({
	apiKey: '', // Put your apiKey
	apiCluster: '' //Put your api cluster name
});
...
```

In the code:
``` js
const channelName: string = 'CHANNEL-NAME'; // In users case meaybe put @ID in the ends

//Pusher bind
this.pusherSubscriber = this.pusherService.bindEvent(channelName, 'CHANNEL-EVENT-NAME', (data: any) => {
	// This code is called from the server
});
```

``` js
//IMPORTANT: Pusher unbind (on component destroy)
if(this.pusherSubscriber){
	const channelName: string = 'CHANNEL-NAME'; 

	//Pusher unbind
	this.pusherService.unbindEvent(channelName, this.pusherSubscriber);
}
```