open-index/open-npm huggingface dataset:
npm package: @omkaryalla/masnory-layout
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.3.0.
Latest version: 0.0.3

# MasnoryLayout

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test MasnoryLayout` 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: @omkaryalla/password-validator
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 13.3.0.
Latest version: 0.0.1

# MyLib

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test my-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.
npm package: @omklokare1998/data-grid
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.
Latest version: 0.0.1

# DataGrid

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.0.

## 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 data-grid
```

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/data-grid
   ```

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: @oml/language
Description: The language specific package
Latest version: 0.13.0

# OML Language

`@oml/language` contains the core language layer for OML.

It is responsible for:

- the Langium grammar and generated AST
- language service composition through `createOmlServices(...)`
- validation, scope, completion, hover, rename, edit, formatting, and serialization
- OML workspace and document mechanics

It does not contain the semantic web layer anymore. OWL/RDF mapping, reasoning, SPARQL, and SHACL now live in `@oml/owl`.

## Package Boundary

- `@oml/language` is the base language package
- `@oml/owl` depends on `@oml/language`
- `@oml/markdown` depends on `@oml/owl`

## Main Exports

- `createOmlServices`
- `OmlModule`
- `OmlSharedModule`
- generated AST and grammar exports
- language service implementations and request registrations

## Instructions

Use this package when you need language tooling without the semantic layer.

Typical usage:

```ts
import { createOmlServices } from '@oml/language';

const { shared, Oml } = createOmlServices(context);
```

Run the language package tests with:

```bash
npm run --workspace packages/language test
```
npm package: @oml/markdown
Description: Markdown runtime and execution contracts for OML
Latest version: 0.13.0

# OML Markdown

`@oml/markdown` contains the markdown layer for OML.

It is responsible for:

- markdown parsing and front matter handling
- markdown execution request/result types
- markdown block execution through `MarkdownExecutor`
- browser runtime assets
- shared markdown renderers

## Package Boundary

- `@oml/language` owns the language layer
- `@oml/owl` owns the semantic web layer
- `@oml/markdown` depends on `@oml/owl`

This package does not implement the core OML language services directly.

## Main Exports

- `MarkdownPreviewRuntime`
- `MarkdownExecutionRequest`
- `MarkdownExecutor`
- markdown execution/result types
- `STATIC_MARKDOWN_RUNTIME_BUNDLE_FILE`
- `STATIC_MARKDOWN_RUNTIME_CSS`
- shared renderers via `@oml/markdown/renderers`

## Instructions

Use this package when you need markdown preparation, markdown execution contracts, or OML markdown block execution on top of `@oml/owl`.

Typical usage:

```ts
import { MarkdownExecutor } from '@oml/markdown';
```
npm package: @oml/owl
Description: The semantic web specific package
Latest version: 0.13.0

# OML OWL

`@oml/owl` contains the semantic web layer for OML.

It is responsible for:

- mapping OML models to OWL/RDF
- reasoning services and prepared datasets
- SPARQL query and construct execution
- SHACL validation
- semantic service composition through `createOwlServices(...)`

## Package Boundary

- `@oml/language` owns syntax, AST, language services, validation, scope, rename, hover, formatting, and workspace mechanics
- `@oml/owl` depends on `@oml/language`
- `@oml/markdown` depends on `@oml/owl`

This keeps semantic web concerns out of the language package.

## Main Exports

- `createOwlServices`
- `ReasoningService`
- `PreparedReasonedModel`
- `Oml2OwlMapper`
- `createOwlOntologyQuads`
- `owlOntologyPrefixes`
- `deriveSelectQueryFromShape`
- `createDefaultShaclService`
- `registerShaclValidationRequests`

## Instructions

Use this package when you need OML semantic services instead of core language services alone.

Typical usage:

```ts
import { createOwlServices } from '@oml/owl';

const { shared, Oml } = createOwlServices(context);
const reasoningService = Oml.reasoning.ReasoningService;
```

For pure language tooling without the semantic layer, use `@oml/language`.