open-index/open-npm huggingface dataset:
npm package: @haitch-ui/react-compose-refs
Description: Compose multiple React refs into a single ref callback.
Latest version: 0.1.2

# @haitch-ui/react-compose-refs

Scaffolded primitive package. Note - this package is now deprecated. Future releases will be included in @haitch-ui/react

## Install
```sh
pnpm add @haitch-ui/react-compose-refs
```
npm package: @haithamsboui/ngx-countdown-timer
Description: Forked from [markpenaranda/ngx-countdown-timer](https://github.com/markpenaranda/ngx-countdown-timer)
Author: haitham sboui
Latest version: 1.0.2

Forked from [markpenaranda/ngx-countdown-timer](https://github.com/markpenaranda/ngx-countdown-timer)

# ngx-countdown-timer

## Installation

To install this library, run:

```bash
$ npm install @haithamsboui/ngx-countdown-timer --save
```

## Consuming your library

Once you have published your library to npm, you can import your library in any Angular application by running:

```bash
$ npm install ngx-countdown-timer
```

and then from your Angular `AppModule`:

```typescript
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';

import { AppComponent } from './app.component';

// Import your library
import { CountdownTimerModule } from 'ngx-countdown-timer';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,

    // Specify your library as an import
    LibraryModule
    CountdownTimerModule.forRoot()
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }
```

Once your library is imported, you can use its components, directives and pipes in your Angular application:

```xml
<!-- You can now use your library component in app.component.html -->
<h1>
  {{title}}
</h1>
Timer mode:
<countdown-timer [start]="'2017-01-01 00:00:00'"></countdown-timer>
 
Countdown:
<countdown-timer [end]="'2018-01-01 00:00:00'"></countdown-timer>

Countdown with zero trigger:
<countdown-timer (zeroTrigger)="yourOwnFunction()" [end]="'2018-01-01 00:00:00'"></countdown-timer>
```

## Development

To generate all `*.js`, `*.d.ts` and `*.metadata.json` files:

```bash
$ npm run build
```

To lint all `*.ts` files:

```bash
$ npm run lint
```

## License

MIT © [MJP](mailto:markangelpenaranda@gmail.com)
npm package: @haithembelhaj/compass-mixins
Description: Compass stylesheets
Author: Haithem Bel Haj
Latest version: 0.12.8

[![Build Status](https://travis-ci.org/Igosuki/compass-mixins.svg?branch=master)](https://travis-ci.org/Igosuki/compass-mixins)

# Compass SASS Stylesheets

This is a repository to pull SASS style sheets on Bower, and enjoy the compass mixins by using libsass for faster compilation. This project makes minimal modifications to the original stylesheets from the [original repository](https://github.com/Compass/compass/tree/stable/core/stylesheets), intented to improve libsass compatibility and not change output.

## Compass Ruby Functions

This project includes reasonably similar implementations of some of the Ruby functions that Compass provides as Sass extensions. These are used in some Compass mixins, such as `@include background()`.

To make those functions available to your compass mixins, you'll want to either `@import "compass";` or `@import "compass/functions"'` before the specific compass scss files you import.

## Contributors
Guillaume Balaine Igosuki@github
Michael Heillein michaek@github

## License
Copyright (c) 2008-2009 Christopher M. Eppstein<br>
All Rights Reserved.<br>
Released under a [slightly modified MIT License](https://github.com/Compass/compass/blob/stable/LICENSE.markdown).
npm package: @haiticss/haiticss
Description: Just another baseline perspective to wear any project with the ITCSS architecture
Author: Daniel Fornells
Latest version: 1.0.0-alpha

# :pineapple: haiticss

[![Build Status](https://travis-ci.org/haiticss/haiticss.svg?branch=master)](https://travis-ci.org/haiticss/haiticss)

Just another baseline perspective to wear any project with the [ITCSS](http://itcss.io/) architecture. Mainly based on the excellent project [inuitcss](https://github.com/inuitcss/inuitcss) by [Harry Roberts](https://csswizardry.com/), from where I found my best suitable starting point.

The idea to create this project, comes from the necessity to adding some modifications and missing features on INUIT that probably will not fit into the original project roadmap.

The input of this mutation comes from my experience applying this architecture on many projects, some new, some not.

Main differences from [inuitcss](https://github.com/inuitcss/inuitcss) are:

* Number prefixes on CSS layers, helping non familiar developers to get into the architecture hierarchy.
* Namespaced variables to improve compatibility when importing into an existent project.
* Scoped version of generic layer, helping to start old site migrations on the fly, respecting the legacy code, but breaking most risky inheritance.
* Feature toggling variables to include/exclude any object or utility.
* Extended objects and utilities configuration variables to toggle and configure some modifiers groups and unused CSS output.



### References

* [BEM Naming](http://getbem.com/naming/)
* [Managing CSS Projects with ITCSS](https://www.youtube.com/watch?v=1OKZOV-iLj4&feature=youtu.be)
* [BEMIT: Taking the BEM Naming Convention a Step Further](https://csswizardry.com/2015/08/bemit-taking-the-bem-naming-convention-a-step-further/)
* [INUIT CSS](https://github.com/inuitcss/inuitcss)
npm package: @haitrungle/create-cli
Description: Scaffold a modern Node.js CLI app
Author: Hai Trung Le
Latest version: 0.0.3

# create-cli

Scaffold a modern and minimal Node.js CLI app.

This is the template I use whenever I have to write a Node.js script. I prioritize modern libraries for their focus on performance, good typing support, and sane default configuration. The catch is that this template is only compatible with Node.js >=20 and uses the preview version of TypeScript, but for internal and personal tools, those requirements are acceptable to me.

This template is heavily inspired by the post [My JS CLI Stack 2025
](https://ryoppippi.com/blog/2025-08-12-my-js-cli-stack-2025-en) by [ryoppippi](https://github.com/ryoppippi). Thank you for sharing!

## Usage

```bash
npx @haitrungle/create-cli <project-name>

# Or follow the prompts
npx @haitrungle/create-cli 
```

Then, refer to [gunshi docs](https://gunshi.dev/guide/essentials/getting-started):

```ts
import { define, cli } from "gunshi";

// Define a subcommand
const hello = define({
  name: "hello",
  description: "Say hello",
  args: {
    name: {
      type: "string",
      short: "n",
      description: "Name to greet",
      default: "World",
    },
  },
  run: (ctx) => {
    console.log(`Hello, ${ctx.values.name}!`);
  },
});

// Define the entry point
const main = define({
  name: "my-nice-cli",
  description: "My little CLI app",
  run: () => {
    console.log("Welcome to my-nice-cli! Run with --help to see commands.");
  },
});

// Wire up and start the CLI
await cli(process.argv.slice(2), main, {
  name: "my-nice-cli",
  version: "0.0.1",
  description: "My little CLI app",
  subCommands: {
    hello,
  },
});
```

## Dependencies

- `gunshi`: declarative CLI definition with type information out of the box
- `oxfmt` and `oxlint`: formatting and linting
- `vitest`: standard choice for testing
- `@typescript/native-preview`: TypeScript 7.0 preview, fast and stable in my usage
- `@types/node`: type declarations for Node.js
- `tsdown`: fast bundler that is both configurable and extensible

The heaviest library here is `tsdown` at 26 MB. It is possible to omit `tsdown` if you use Node.js >=24 with type stripping, but you have to annotate all type imports with the `type` keyword and set `allowImportingTsExtensions` to true in "tsconfig.json". Then, remove `tsdown` and the `build` script from "package.json" and delete "tsdown.config.ts", and you are good to go.

The second heaviest library here is `vitest` at 21 MB. I hear you: I don't like testing something that feels like an one-off script either. Still, most CLI tools I write are ran more than once anyways, and since they are the easiest kind of program to test, I bit the bullet and include it to make myself feel good. The fact that coding agents work best with tests to keep them in track is the cherry on top. However, you can also delete it just as easily as with `tsdown`, should you prefer.