open-index/open-npm huggingface dataset:
npm package: @sigmaproit/loading-states-section
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.0.4.
Latest version: 0.0.4

# LoadingStatesSection

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test loading-states-section` 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: @sigmasd/nvim-types
Description: This npm package provide types that you can use with https://github.com/TypeScriptToLua/TypeScriptToLua to write your neovim config or plugins in typescript
Latest version: 0.0.10

# Nvim Types

This npm package provide types that you can use with https://github.com/TypeScriptToLua/TypeScriptToLua to write your neovim config or plugins in typescript

## Usage

1. Install this package and the required dependencies for a tstl project

```bash
npm install @sigmasd/nvim-types lua-types @typescript-to-lua/language-extensions typescript-to-lua typescript --save-dev 
```


2. Modify your `tsconfig.json` to activate the types

```json
  {
  "compilerOptions": {
    "types": ["@sigmasd/nvim-types", "@typescript-to-lua/language-extensions", "lua-types/jit"]
  }
}
```

Thats it you should be able now to run your project (`npx tstl -p tsconfig.json`) and have lsp working correctly.

## Credits

Credits to https://github.com/jose-elias-alvarez/typescript.nvim for the original idea and code
npm package: @sigmastics/qwik-lib-1
Description: Create a Qwik library
Latest version: 0.0.1

# Qwik Library ⚡️

- [Qwik Docs](https://qwik.dev/)
- [Discord](https://qwik.dev/chat)
- [Qwik on GitHub](https://github.com/QwikDev/qwik)
- [@QwikDev](https://twitter.com/QwikDev)
- [Vite](https://vitejs.dev/)
- [Partytown](https://partytown.builder.io/)
- [Mitosis](https://github.com/BuilderIO/mitosis)
- [Builder.io](https://www.builder.io/)

---

## Project Structure

Inside your project, you'll see the following directories and files:

```
├── public/
│   └── ...
└── src/
    ├── components/
    │   └── ...
    └── index.ts
```

- `src/components`: Recommended directory for components.

- `index.ts`: The entry point of your component library, make sure all the public components are exported from this file.

## Development

Development mode uses [Vite's development server](https://vitejs.dev/). For Qwik during development, the `dev` command will also server-side render (SSR) the output. The client-side development modules are loaded by the browser.

```
npm run dev
```

> Note: during dev mode, Vite will request many JS files, which does not represent a Qwik production build.

## Production

The production build should generate the production build of your component library in (./lib) and the typescript type definitions in (./lib-types).

```
npm run build
```