open-index/open-npm huggingface dataset:
npm package: @stablyhung/contract-helpers
Description: The `@aave/contract-helpers` package offers a set of services which allow querying aggregated on-chain data via rpc.
Latest version: 1.28.0

# @aave/contract-helpers

The `@aave/contract-helpers` package offers a set of services which allow
querying aggregated on-chain data via rpc.

## Installation

Install the package in your project directory with:

```sh
// with npm
npm install @aave/contract-helpers

// with yarn
yarn add @aave/contract-helpers
```
npm package: @stablyhung/math-utils
Description: The `@aave/math-utils` data formatting methods act as a layer on top of the chain data. The use-cases range from "human readable formatting" to "approximating accrual over time".
Latest version: 1.28.0

# @aave/math-utils

The `@aave/math-utils` data formatting methods act as a layer on top of the
chain data. The use-cases range from "human readable formatting" to
"approximating accrual over time".

## Installation

Install the package in your project directory with:

```sh
// with npm
npm install @aave/math-utils

// with yarn
yarn add @aave/math-utils
```
npm package: @stacc/clear-module
Description: Clear a module from the cache
Author: Sindre Sorhus
Latest version: 4.3.2

# clear-module

> Clear a module from the [cache](https://nodejs.org/api/modules.html#modules_caching)

Useful for testing purposes when you need to freshly import a module.

## Install

```
$ npm install clear-module
```

## Usage

```js
// foo.js
let i = 0;
module.exports = () => ++i;
```

```js
const clearModule = require('clear-module');

require('./foo')();
//=> 1

require('./foo')();
//=> 2

clearModule('./foo');

require('./foo')();
//=> 1
```

## API

### clearModule(moduleId)

#### moduleId

Type: `string`

What you would use with `require()`.

### clearModule.all()

Clear all modules from the cache.

### clearModule.match(regex)

Clear all matching modules from the cache.

#### regex

Type: `RegExp`

Regex to match against the module IDs.

### clearModule.single(moduleId)

Clear a single module from the cache non-recursively. No parent or children modules will be affected.

This is mostly only useful if you use singletons, where you would want to clear a specific module without causing any side effects.

#### moduleId

Type: `string`

What you would use with `require()`.

## Related

- [import-fresh](https://github.com/sindresorhus/import-fresh) - Import a module while bypassing the cache
- [import-from](https://github.com/sindresorhus/import-from) - Import a module from a given path
- [import-cwd](https://github.com/sindresorhus/import-cwd) - Import a module from the current working directory
- [import-lazy](https://github.com/sindresorhus/import-lazy) - Import a module lazily
npm package: @stacc/flow-types
Description: Flow types
Author: Stacc
Latest version: 2.0.7

# Flow types

## Introduction
Generic types for handlers and common types used in Stacc's Flow projects.

For documentation about Flow itself please refer to its [docs](https://flow-docs.stacc.dev/)
To dive deeper into the types please see [modules](./modules.md) section.

## Types

### Handlers
* FlowHandler
* EventTaskHandler
* MessageTaskHandler
* ServiceTaskHandler
* StartHandler
* TerminateHandler
* UserTaskHandler

### Other
* User
* Meta
* JsonPatch
* Await
npm package: @stacc/red
Description: ![stacc_red](https://user-images.githubusercontent.com/62754080/194485987-66b2ccc6-df91-4ff1-be1a-55f5391ec899.png)
Latest version: 1.4.0

![stacc_red](https://user-images.githubusercontent.com/62754080/194485987-66b2ccc6-df91-4ff1-be1a-55f5391ec899.png)

# _Red_ - Stacc's design system
More to come
npm package: @stacc/semantic-release-config
Description: ```shell npm install --save-dev @stacc/semantic-release-config semantic-release ```
Latest version: 1.3.0

# Stacc Semantic Release Configuration
## Installation
```shell
npm install --save-dev @stacc/semantic-release-config semantic-release
```

## Add to package.json
```json
{
  "release": {
    "extends": "@stacc/semantic-release-config"
  }
}
```

## In your workflow
```yaml
      - name: Semantic Release
        if: success()
        working-directory: .
        env:
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          NPM_PUBLISH: true # if you need to publish to npm
          GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
          SLACK_WEBHOOK: ${{ secrets.SLACK_RELEASE_BOT_WEBHOOK }}
        run: npm run semantic-release -- --branches main
```
npm package: @stacc/services-ambita-realty
Description: An API that proxies the Ambita Realty API
Latest version: 2.7.3

# Stacc Ambita Realty Proxy API

An API that proxies the Ambita Realty API

## Requirements
To run and try out this API locally, a .env file must be included with the correct credentials: 
```
API_URL=<API_URL>
AUTH_URL=<AUTH_URL
AMBITA_CLIENT_ID=<AMBITA_CLIENT_ID>
AMBITA_CLIENT_SECRET=<AMBITA_CLIENT_SECRET>
AMBITA_USERNAME=<AMBITA_USERNAME>
AMBITA_PASSWORD=<AMBITA_PASSWORD>
```
After this is setup, run the following command at the project's root:

``` $ npm install && npm run dev```
## Try out the API locally with REST client (Visual Studio Code)
1. Install a REST client for your IDE
    - VSCode: https://marketplace.visualstudio.com/items?itemName=humao.rest-client
2. Add a settings.json file to your .vscode folder and include the following: 
    ```
    {
        "rest-client.environmentVariables": {
            "$shared":{
                "nin1": "<enter your nin here>",
                "nin2": "<enter your nin here>"
            },
            "local": {
            },
            "production": {
            }
        }
    }
    ```
    - !! Always make sure to not commit sensitive personal data to the VCS !!
3. ``` $ npm run dev ```
4. You should now be abvle to run the requests in the src/requests folder.

For other IDE's, follow the documentation and makes sure to .gitignore any files containing sensitive information:
- Webstorm: https://www.jetbrains.com/help/webstorm/exploring-http-syntax.html#using_request_vars
npm package: @stacc/services-eiendomsverdi
Description: ```bash curl -X POST http://localhost:3000/api/template -H 'Content-Type: application/json' -d '{"name":"Stacc X"}' ```
Latest version: 1.1.14

# An empty service

```bash
curl -X POST http://localhost:3000/api/template -H 'Content-Type: application/json' -d '{"name":"Stacc X"}'
```
npm package: @staccoverflow/hydraderp
Description: Hydra
Author: Hydra GlassEaters
Latest version: 1.3.8

# Hydra

Collective account pooling, fan out wallet, dao treasury, all of the things you need to FAN OUT

![](/packages/docs/static/img/logo.jpeg)

## Setup && Development

To get started the basic steps are to install all the JS dependencies, cargo dependencies will be installed automatically when you run `anchor build`.
This package uses the latest yarn, which is yarn 3 and I will accept no hate for using the latest yarn :)

```
yarn
```

There are three components in this repo..

1. Program
2. SDK
3. Docs

### Program Development

The Hydra smart contract is written with anchor but we have changed the development flow slightly to allow for what we think is a better SDK.
Using `anchor build` you get the BPF so file and the IDL. You then run the following to generate the SDK and spin up a local validator when you want to test your changes.

```shell
yarn run api:gen
yarn run amman:start
```

Now you have a validator running your newly compiled SO file and any other programs you have listed in the `.ammanrc.cjs`.

Currently we require the local validator to have the `Token Metadata` program from `Metaplex`. We suggest you clone the `Metaplex Program Library` and put it in the same root folder as hydra like this:

```shell
 /root-folder
    /hydra
    /metaplex-program-library
```

To build the latest token metadata program you will need to do the following:

```shell
cd metaplex-program-library/token-metadata/program
cargo build-bpf --bpf-out-dir ../../target/deploy/
```

Now your top level MPL target folder will have the token metadata `so` file that `amman` can find and deploy to the local validator.

After accomplishing this your workflow to build new code will be:

```shell
anchor build //Optional as the next commant runs anchor build for you
yarn run api:gen
yarn run amman:start
```

### SDK Development

Now that you know how to build the program, building the SDK is easy. All you need to do is run:

```shell
yarn run watch
```

This will watch your `packages/sdk` folder for any changes, which means it will build the SDK for use in apps or tests when the auto generated code from the api generator is saved in the folder.

#### Testing

Now that you have the ability to build the program, generated sdk and the rest of the sdk, running tests is a breeze.
With the local validator up and running you can simply run.

```shell
yarn test
```

Using ts-node/register you can even setup breakpoints and debuggers on your IDE to debug your tests.
If you dont have the local validator running do:

```shell
yarn run amman:start
yarn test
```

Or if you are like Noah or Will and are extremely lazy and can't be bothered to run more than one command run `yarn run mega-test`

### Docs Development

```shell
cd packages/docs
yarn start
```
npm package: @staccx/block-content-to-pug
Description: Transform Sanity block content to pug
Author: Stacc
Latest version: 0.1.0

# block-content-to-pug
[Based on this](https://github.com/sanity-io/block-content-to-markdown) 

Render an array of [block text](https://www.sanity.io/docs/schema-types/block-type) from Sanity to [Pug](https://github.com/pugjs/pug/tree/master/packages/pug).

## Installing

```
npm install --save block-content-to-pug
```

## Usage

````js
const toPug = require('block-content-to-pug')
const client = require('@sanity/client')({
  projectId: '<your project id>',
  dataset: '<some dataset>',
  useCdn: true
})

const serializers = {
  types: {
    code: props => '```' + props.node.language + '\n' + props.node.code + '\n```'
  }
}

client.fetch('*[_type == "article"][0]').then(article => {
  console.log(toPug(article.body, {serializers}))
})
````

## Options

- `serializers` - Specifies the functions used for rendering content. Merged with default serializers.
- `serializers.types` - Serializers for block types, see example above
- `serializers.marks` - Serializers for marks - data that annotates a text child of a block. See example usage below.
- `serializers.list` - Function to use when rendering a list node
- `serializers.listItem` - Function to use when rendering a list item node
- `serializers.hardBreak` - Function to use when transforming newline characters to a hard break
- `imageOptions` - When encountering image blocks, this defines which query parameters to apply in order to control size/crop mode etc.

In addition, in order to render images without materializing the asset documents, you should also specify:

- `projectId` - The ID of your Sanity project.
- `dataset` - Name of the Sanity dataset containing the document that is being rendered.

## Examples

### Rendering custom marks

```js
const input = [
  {
    _type: 'block',
    children: [
      {
        _key: 'a1ph4',
        _type: 'span',
        marks: ['s0m3k3y'],
        text: 'Sanity'
      }
    ],
    markDefs: [
      {
        _key: 's0m3k3y',
        _type: 'highlight',
        color: '#E4FC5B'
      }
    ]
  }
]

const highlight = props => {
  const content = Array.isArray(props.children) ? props.children.join('') : props.children
  return `<span style="background-color: ${props.mark.color};">${content}</span>`
}

toPug(input, {serializers: {marks: {highlight}}})
```

### Specifying image options

```js
toPug(input, {
  imageOptions: {w: 320, h: 240, fit: 'max'},
  projectId: 'myprojectid',
  dataset: 'mydataset'
})
```

## License

MIT-licensed. See LICENSE.
npm package: @staccx/eslint-config
Description: JavaScript linting setup for @staccx
Author: Stacc X
Latest version: 11.1.0

# StaccX eslint-config

Shared eslint settings for Stacc X. Based on prettier + standard. [Based on eslints own documentation of shareable-configs](https://eslint.org/docs/developer-guide/shareable-configs)

## Usage

`yarn add @staccx/eslint-config --dev`

Create .eslintrc in the root of your project

```
{
    "extends": "@staccx"
}
```
npm package: @staccx/next-i18n
Description: Package template
Author: Stacc
Latest version: 2.1.3

# Package template

#### `i18next-parser.config.js`

```js
const { i18n } = require("./next-i18next.config")

module.exports = {
  locales: i18n.locales,
  output: "i18n/$LOCALE/$NAMESPACE.json",
  defaultNamespace: "common",
  lexers: {
    js: ["JsxLexer"],
    ts: ["JsxLexer"],
    jsx: ["JsxLexer"],
    tsx: ["JsxLexer"],
  },
  verbose: true,
}
```
#### `next-i18next.config.js`

```js
const path = require("path")

module.exports = {
  i18n: {
    defaultLocale: "no",
    locales: ["no"],
  },
  localePath: path.resolve("./i18n"),
  returnObjects: true,
}
```

#### `next.config.js`

```js
const { i18n } = require("./next-i18next.config")

module.exports = {
  i18n,
  reactStrictMode: true,
}
```
npm package: @stacio/detox
Description: E2E tests and automation for mobile
Author: Tal Kol
Latest version: 16.8.2

# detox

Graybox End-to-End Tests and Automation Library for Mobile

[![NPM Version](https://img.shields.io/npm/v/detox.svg?style=flat)](https://www.npmjs.com/package/detox)
[![Build Status](https://img.shields.io/jenkins/s/http/jenkins-oss.wixpress.com:8080/job/multi-detox-master.svg)](https://jenkins-oss.wixpress.com/job/multi-detox-master/)
[![NPM Downloads](https://img.shields.io/npm/dm/detox.svg?style=flat)](https://www.npmjs.com/package/detox)


For more information go to our [README](https://github.com/wix/detox/blob/master/README.md) or [Read The Docs](https://github.com/wix/detox/tree/master/docs)
npm package: @stack-craft/create-stack-craft
Description: A CLI tool to create projects with Express, Hono, and Prisma
Author: Dev Rio
Latest version: 1.0.0

# Create Stack Craft

**Create Stack Craft** is a CLI tool to create projects with Express, Hono, and Prisma. This tool helps you quickly set up a new project with the desired framework, language, and Prisma integration.

## Features

-   Create projects with Express or Hono.
-   Choose between TypeScript or JavaScript.
-   Optionally include Prisma for database management.
-   Automatically set up the project structure and dependencies.

## Installation

To use Create Stack Craft, you need to have Node.js and npm installed on your machine. You can install Create Stack Craft globally using npm:

```bash
npm install -g create-stack-craft
```

## Usage

You can create a new project by running the following command with `npm`:

```bash
npm create stack-craft@latest
```

Or with `pnpm`:

```bash
pnpm create stack-craft@latest
```

### Interactive Prompts

You will be prompted to enter the following information:

1. **Project Name**: Enter the name of your project.
2. **Framework**: Choose between Express or Hono.
3. **Language**: Choose between TypeScript or JavaScript.
4. **Include Prisma**: Optionally include Prisma in your project.
5. **Run npm install**: Optionally run `npm install` after setting up the project.

### Example

```bash
npm create stack-craft@latest
```

or

```bash
pnpm create stack-craft@latest
```

Follow the prompts to create your project. Once the setup is complete, navigate to your project directory and start the development server:

```bash
cd my-project
npm run dev
```

## Project Structure

The generated project structure will look like this:

```
my-project/
├── prisma/
│   └── schema.prisma (if Prisma is included)
├── src/
│   ├── app.ts (or app.js)
│   └── routes/
│       └── index.ts (or index.js)
├── .env (if Prisma is included)
├── .env.example (if Prisma is included)
├── package.json
└── tsconfig.json (if TypeScript is selected)
```

## Scripts

The generated `package.json` will include the following scripts:

-   `build`: Compile the TypeScript code (if TypeScript is selected).
-   `start`: Run the compiled code.
-   `lint`: Run ESLint on the project.
-   `db:generate`: Generate Prisma client (if Prisma is included).
-   `db:migrate`: Run Prisma migrations (if Prisma is included).
-   `db:push`: Push the Prisma schema to the database (if Prisma is included).
-   `db:studio`: Open Prisma Studio (if Prisma is included).

## Links

-   [Prisma](https://www.prisma.io/)
-   [Hono](https://honojs.dev/)
-   [Express](https://expressjs.com/)

## Contributing

Contributions are welcome! Please open an issue or submit a pull request for any bugs or feature requests.

## License

This project is licensed under the MIT License.
npm package: @stack-dev/cli
Description: An opinionated, high-velocity TypeScript monorepo manager built on `pnpm` and `tsup`. This workspace provides the scaffolding for building shared libraries, React components, and CLI tools with minimal configuration overhead.
Latest version: 0.3.3

# Stack-Dev Workspace

An opinionated, high-velocity TypeScript monorepo manager built on `pnpm` and `tsup`. This workspace provides the scaffolding for building shared libraries, React components, and CLI tools with minimal configuration overhead.

---

## ⚡ Quick Start

### 1. Install the CLI
To manage this workspace, install the `@stack-dev/cli` globally via npm:

```bash
npm install -g @stack-dev/cli
```

### 2. Create a New Workspace
Generate a new workspace using the `stack create` command:

```bash
stack create my-new-project
```

### 3. Generate Packages
Inside the workspace, use the `stack g` command to create different types of modules:

```bash
# Generate a vanilla TypeScript library
stack g my-utils --type library

# Generate a React library with Styled Components
stack g ui-kit --type react --style styled-components

# Generate a Vite + React application
stack g web-app --type vite
```

---

## 🛠 Commands

| Command                       | Alias | Description                                  |
|-------------------------------|-------|----------------------------------------------|
| `stack create <name>`         |       | Initialize a new workspace                  |
| `stack g <name>`              |       | Generate a new package, app, or config      |
| `stack link [name]`           | `l`   | Link a local workspace package to the current directory |
| `stack unlink [name]`         | `u`   | Remove a local package link                 |

---

## 🏗 Project Structure

This workspace is organized as follows:

- `packages/*`: Shared libraries and configuration packages.
- `apps/*`: Deployment targets such as Vite apps, CLIs, etc.
- `configs/*`: Shared ESLint, Prettier, and TypeScript configuration files.

---

## 🔧 Development Workflow

### Building
To build the workspace, run:

```bash
pnpm run build
```

### Running Locally
To run a compiled build:

```bash
pnpm start
```

For development, run in watch mode:

```bash
pnpm run build --watch
```

---

## 🛠 Smart Linking with CLI

The `@stack-dev/cli` provides intelligent linking for local packages in your workspace:

- **Interactively link a package**:
  ```bash
  stack link
  ```

- **Link as a `devDependency`**:
  ```bash
  stack link @stack-dev/core --dev
  ```

To unlink a package:

```bash
stack unlink
```

---

## Documentation

Visit the individual package directories (e.g., `packages/cli` or `apps`) for more specific details about their usage and configuration.
npm package: @stack-dev/docs
Description: [![Built with Starlight](https://astro.badg.es/v2/built-with-starlight/tiny.svg)](https://starlight.astro.build)
Latest version: 0.2.1

# Starlight Starter Kit: Basics

[![Built with Starlight](https://astro.badg.es/v2/built-with-starlight/tiny.svg)](https://starlight.astro.build)

```
pnpm create astro@latest -- --template starlight
```

> 🧑‍🚀 **Seasoned astronaut?** Delete this file. Have fun!

## 🚀 Project Structure

Inside of your Astro + Starlight project, you'll see the following folders and files:

```
.
├── public/
├── src/
│   ├── assets/
│   ├── content/
│   │   └── docs/
│   └── content.config.ts
├── astro.config.mjs
├── package.json
└── tsconfig.json
```

Starlight looks for `.md` or `.mdx` files in the `src/content/docs/` directory. Each file is exposed as a route based on its file name.

Images can be added to `src/assets/` and embedded in Markdown with a relative link.

Static assets, like favicons, can be placed in the `public/` directory.

## 🧞 Commands

All commands are run from the root of the project, from a terminal:

| Command                   | Action                                           |
| :------------------------ | :----------------------------------------------- |
| `pnpm install`             | Installs dependencies                            |
| `pnpm dev`             | Starts local dev server at `localhost:4321`      |
| `pnpm build`           | Build your production site to `./dist/`          |
| `pnpm preview`         | Preview your build locally, before deploying     |
| `pnpm astro ...`       | Run CLI commands like `astro add`, `astro check` |
| `pnpm astro -- --help` | Get help using the Astro CLI                     |

## 👀 Want to learn more?

Check out [Starlight’s docs](https://starlight.astro.build/), read [the Astro documentation](https://docs.astro.build), or jump into the [Astro Discord server](https://astro.build/chat).
npm package: @stack-finance/moengage-sdk
Description: An API to API NodeJS SDK for MoEngage
Author: Samarth Kulkarni
Latest version: 1.0.1

# moengage-sdk
An API to API NodeJS SDK for MoEngage.

---
## Requirements

You will need an account on MoEngage to make successful method calls from this package, *obviously*.

You will also need the `API ID` and `API Key` for your account, which can be obtained from
`Dashboard -> Settings -> APIs`

## Installation

`npm i @stack-finance/moengage-sdk`

## Starter Code

```js
import { MoEngage } from '@stack-finance/moengage-sdk';

const moengage = new MoEngage(
  '<API ID>',
  '<API Key>',
  '<Data Center - Only "01", "02" and "03" are valid values>');

const res = await MoengageSDK.triggerEvent({
  "type": "event",
  "customer_id": "john@example.com",
  "device_id": "96bd03b6-defc-4203-83d3-dc1c73080232",
  "actions": [{
      "action": "Added to Cart",
      "attributes": {
        "product": "Mobile",
        "color": "white",
        "Brand": "Apple"
      },
      "platform": "iOS",
      "app_version": "1.2.3",
      "current_time": new Date().getTime() / 1000,
      "user_timezone_offset": 19800
    },
    {
      "action": "Purchase",
      "attributes": {
        "product": "MacBook Air",
        "Brand": "Apple"
      },
      "platform": "web",
      "app_version": "1.2.3",
      "current_time": new Date().getTime() / 1000,
      "user_timezone_offset": 19800
    }
  ]
});
if (res.ok) {
  console.log(await res.json());
} else {
  // Errors are not handled in the package yet, for now you will have to handle this.
  // We will implement error handlign in the future versions.
  console.log(await res.text() || res.statusText());
}
```
npm package: @stack-inc/electron-notification-state
Description: Should you send a notification?
Author: Felix Rieseberg
Latest version: 0.1.3

# electron-notification-state
Should you display a notification to your user? This module allows you to check.

## Usage

### Do Not Disturb / Quiet Hours
```js
const { getDoNotDisturb } from 'electron-notification-state'
// On Windows, logs `true` if "quiet hours" are enabled
// On macOS, logs `true` if "do not disturb" is enabled
console.log(getDoNotDisturb());
```

### Session State
On Windows, you likely want to check [SHQueryUserNotificationState](https://msdn.microsoft.com/en-us/library/windows/desktop/bb762242(v=vs.85).aspx), checking whether or not a screensaver is running, if the screen is locked, or if a presentation is running. On macOS, you likely want to check if the screen is locked and if the if the user has an active screen session.

The call below logs a different string, depending on the platform:
#### macOS
- `SESSION_SCREEN_IS_LOCKED` The screen is locked.
- `SESSION_ON_CONSOLE_KEY` The user currently has console/graphical control.

#### Windows
- `QUNS_NOT_PRESENT` A screen saver is displayed, the machine is locked, or a nonactive Fast User Switching session is in progress.
- `QUNS_BUSY` A full-screen application is running or Presentation Settings are applied. Presentation Settings allow a user to put their machine into a state fit for an uninterrupted presentation, such as a set of PowerPoint slides, with a single click.
- `QUNS_RUNNING_D3D_FULL_SCREEN` A full-screen (exclusive mode) Direct3D application is running.
- `QUNS_PRESENTATION_MODE` The user has activated Windows presentation settings to block notifications and pop-up messages.
- `QUNS_ACCEPTS_NOTIFICATIONS` None of the other states are found, notifications can be freely sent.
- `QUNS_QUIET_TIME` Introduced in Windows 7. The current user is in "quiet time", which is the first hour after a new user logs into his or her account for the first time. During this time, most notifications should not be sent or shown. This lets a user become accustomed to a new computer system without those distractions. Quiet time also occurs for each user after an operating system upgrade or clean installation, according to Windows. This is _not_ the same as "quiet hours".
Note that during quiet time, if the user is in one of the other blocked modes (QUNS_NOT_PRESENT, QUNS_BUSY, QUNS_PRESENTATION_MODE, or QUNS_RUNNING_D3D_FULL_SCREEN) SHQueryUserNotificationState returns only that value, and does not report QUNS_QUIET_TIME.
- `QUNS_APP` Introduced in Windows 8. A Windows Store app is running.

```js
const { getSessionState } from 'electron-notification-state'

console.log(getSessionState());
```

## License
MIT. Please see LICENSE for details.
npm package: @stack-inc/macos-notification-state
Description: macOS notification state as a native node addon
Author: Felix Rieseberg
Latest version: 0.1.0

## macos-notification-state
Do you want to check if you should display a notification to your user on macOS? This native module checks if the user is active, if the screen is locked, or if "do not disturb" is enabled.

```
npm install macos-notification-state
```

```
const { getNotificationState, getSessionState, getDoNotDisturb } = require('macos-notification-state`)

// This will brint a boolean (true if enabled, false if not)
console.log(getDoNotDisturb())

// This will print a string indiciating the current state, being one of the following:
// 'SESSION_SCREEN_IS_LOCKED'
// 'SESSION_ON_CONSOLE_KEY'
// 'DO_NOT_DISTURB'
// 'UNKNOWN'
// 'UNKNOWN_ERROR'
//
// If "do not disturb" is enabled, it takes precedence.
console.log(getNotificationState())

// This will print a string indiciating the current session state, being one of the following:
// 'SESSION_SCREEN_IS_LOCKED'
// 'SESSION_ON_CONSOLE_KEY'
// 'UNKNOWN'
console.log(getSessionState())
```

## Not working?

This package _needs_ to be compiled with at least the macOS 11.0 SDK. If not, the internal
operating system info will always return 10.16, rendering the package unusable.

To see the current version, run `xcrun --show-sdk-version`.

#### License
MIT, please see LICENSE for details. Copyright (c) 2019 Felix Rieseberg.
npm package: @stack-inc/windows-notification-state
Description: SHQueryUserNotificationState as a native Node addon
Author: Felix Rieseberg
Latest version: 0.1.2

## windows-notification-state
[SHQueryUserNotificationState](https://msdn.microsoft.com/en-us/library/windows/desktop/bb762242(v=vs.85).aspx), implemented as a native Node addon. If you're looking for a simple solution to check whether or not you should send your user a notification, this is it.

```
npm install windows-notification-state
```

```
const { shQueryUserNotificationState, getNotificationState } = require('windows-notification-state`)

// This will print a number (corresponding with QUERY_USER_NOTIFICATION_STATE)
console.log(shQueryUserNotificationState())

// If you prefer your code to be more readable, you can use the string-based variant.
// This will print the name of the enum (so "QUNS_ACCEPTS_NOTIFICATIONS" instead of 5)
console.log(getNotificationState())
```

#### License
MIT, please see LICENSE for details. Copyright (c) 2017 Felix Rieseberg.
npm package: @stack-inc/windows-quiet-hours
Description: Checks if Windows 10 quiet hours are active
Author: Felix Rieseberg
Latest version: 0.1.1

## windows-quiet hours
Easily check if Windows 10 "Quiet Hours" are active - natively, without shelling out, and without any dependencies. 

```
npm install windows-quiet-hours
```

```
const { getIsQuietHours } = require('windows-quiet-hours`)
const isQuietHours = getIsQuietHours()
```

#### License
MIT, please see LICENSE for details. Copyright (c) 2016 Felix Rieseberg.
npm package: @stack-lint/node
Description: stack lint eslint configs for nodejs
Author: https://github.com/saifulislamsojib
Latest version: 0.1.0

# @stack-lint/node

**Node.js ESLint configuration** with best practices tailored for backend and server-side JavaScript projects.  
Part of the **Stack Lint** family — designed to be combined with `@stack-lint/base` and others.

---

## 📦 Installation

```sh
npm install --save-dev eslint prettier @stack-lint/base @stack-lint/node
# or
yarn add -D eslint prettier @stack-lint/base @stack-lint/node
# or
pnpm add -D eslint prettier @stack-lint/base @stack-lint/node
```

## 🚀 Usage

**eslint.config.js** (or **eslint.config.mjs** if not `"type": "module"`):

```js
import getFlatConfigs from '@stack-lint/base';
import getNodeConfig from '@stack-lint/node';

export default getFlatConfigs(getNodeConfig(true)); // true if ESM, false or omit if CJS
```

### Node + TypeScript

```bash
npm install --save-dev @stack-lint/typescript typescript
# or
yarn add -D @stack-lint/typescript typescript
# or
pnpm add -D @stack-lint/typescript typescript
```

**eslint.config.js**:

```js
import getFlatConfigs from '@stack-lint/base';
import getNodeConfig from '@stack-lint/node';
import getTsConfigs from '@stack-lint/typescript';

export default getFlatConfigs(
  getNodeConfig(true), // true if ESM, false or omit if CJS
  ...getTsConfigs({
    tsconfigRootDir: import.meta.dirname,
    // tsRootDir: 'src/' your tsconfigs files rootDir, if * then no need the field
  }),
);
```

---

### Explanation

- `getNodeConfig(true || { extension: true })` returns the Node.js ESLint configuration optimized for ESM (ECMAScript Modules) environments.
- Passing `true` enables ESM-specific rules and settings; pass `false` or omit the argument for CommonJS environments.
- Passing `{ extension: true }` enables ESM-specific rules and settings and `extension: true` for omit extension check if you use bundler for resolve extension
- `getFlatConfigs(...)` takes one or more ESLint config objects and merges them into a single flat configuration that ESLint can directly use.
npm package: @stack-lint/react
Description: stack lint eslint configs for react
Author: https://github.com/saifulislamsojib
Latest version: 0.1.0

# @stack-lint/react

React-specific ESLint flat configuration for ESLint v9+.  
Built on top of `@stack-lint/base` and includes Prettier integration.
Designed for ESLint's **flat config** system — export an array from `eslint.config.js` or `eslint.config.mjs`.

---

## 📦 Installation

```bash
npm install --save-dev eslint prettier @stack-lint/base @stack-lint/react
```

---

## 🚀 Usage

Create or update your `eslint.config.js` or `eslint.config.mjs` at the root of your project:

```js
import getFlatConfigs from '@stack-lint/base';
import reactConfigs from '@stack-lint/react';

export default getFlatConfigs(...reactConfigs);
```

---

### 2️⃣ Next Js

```sh
npm install --save-dev @next/eslint-plugin-next
# or
yarn add -D @next/eslint-plugin-next
# or
pnpm add -D @next/eslint-plugin-next
```

**eslint.config.js**:

```js
import getFlatConfigs from '@stack-lint/base';
import nextConfigs from '@stack-lint/react/next';

export default getFlatConfigs(...nextConfigs);
```

---

## 📖 Explanation

- **ESLint v9 Flat Configs**  
  ESLint v9+ only supports the new flat config system. Instead of `.eslintrc`, you now define an array of configs in `eslint.config.js`.  
  Read more: [ESLint New Config System – Part 2](https://eslint.org/blog/2022/08/new-config-system-part-2/)

- **Why `@stack-lint/react`?**
  - Pre-configured for React projects.
  - Based on `@stack-lint/base` rules.
  - Includes Prettier for formatting consistency.

- **`getFlatConfigs(...configs)`**
  - Helper from `@stack-lint/base` that merges multiple flat config objects into a single export. and also provide base configs

---

## 📝 Example Project Structure

```
my-react-app/
├── eslint.config.mjs
├── package.json
├── src/
│   ├── App.jsx
│   └── index.jsx
```

---

## ✅ Run ESLint

```bash
npx eslint .
```

---

## 📜 License

MIT
npm package: @stack-pulse/nestjs-stripe
Description: Injectable Stripe client for Nestjs And Create A Futres And Cards Payment flow
Author: Ahmed Ali
Latest version: 1.0.2

## Nestjs-Stripe
```
# nestjs-stripe

nestjs-stripe is a NestJS module for integrating Stripe into your application, and it provides some built-in payment flows for easy implementation.

```

## Instalation

```bash
 npm i @stack-pulse/nestjs-stripe
```

```bash
 yarn add @stack-pulse/nestjs-stripe
```
Nest.js and Stripe are peer dependencies.

## Quick Start



```typescript
import { StripeModule } from  '@stack-pulse/nestjs-stripe';
import { ConfigModule, ConfigService } from  '@nestjs/config';

@Module({
  imports: [
   StripeModule.forRootAsync({
	imports: [ConfigModule],
	useFactory: (configService: ConfigService) => ({
       apiKey: configService.get('STRIPE_SECRET_KEY'),
       config: { apiVersion: "2023-08-16" }
       }),
    inject: [ConfigService]
 })
  ],
  controllers: [YourController],
})
export class YourModule {}
```



Then, use the ervice:

```typescript
import { Controller, Get, Inject } from "@nestjs/common";
import { StripeService } from  '@stack-pulse/nestjs-stripe';

@Controller("your-route-path")
export class YourController {
  constructor(
    @Inject(StripeService)
	private  readonly  stripeService: StripeService
  ) {}

  @Get()
  public async yourRoute() {
  const  client  =  this.stripeService.client
  }
}
```

## Future Payments Flow Docs Coming Soon

## Built In Functions For Future Payments
```typescript
  //Stripe Client
  const  client  =  this.stripeService.client
```
```typescript

__create_customer()
__get_payment_methods()
__get_default_payment_method()
__set_default_payment_method()
__detach_payment_method()
payment_intent() //for futre and non future both
__check_payment_method(payment_method,customer_id)
```


## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details.
```
npm package: @stack-so/stack-js
Description: Stack.so JS client library
Author: Stack.so
Latest version: 1.2.2

# @stack-so/stack-js

[![npm package][npm-img]][npm-url]
[![Build Status][build-img]][build-url]
[![Downloads][downloads-img]][downloads-url]
[![Issues][issues-img]][issues-url]
[![Code Coverage][codecov-img]][codecov-url]
[![Commitizen Friendly][commitizen-img]][commitizen-url]
[![Semantic Release][semantic-release-img]][semantic-release-url]

> Stack JS Client Library

## Install the Stack client library

```bash
npm install "@stack-so/stack"
```

## Usage

### Import the Stack Library

```ts
import stack from "stack-so";

stack.init(apiKey);
```

### Track an event from a wallet

```javascript
stack.track("CONNECT_WALLET", {
    actor: {
        type: "wallet",
        address: "0x375892Bb243D35E4c12e8a87b95e24F7F53d493E"
    }
});
```

### Track an interaction

```javascript
stack.track("LIKED_NFT", {
    actor: {
        type: "wallet",
        address: "0x375892Bb243D35E4c12e8a87b95e24F7F53d493E"
    },
    object: {
        type: "contract",
        address: "0x5180db8f5c931aae63c74266b211f580155ecac8",
        id: 3
    };
})
```

### Enrich your information with metadata

```javascript
stack.track("VIEWED_COLLECTION", {
    actor: {
        type: "wallet",
        address: "0x375892Bb243D35E4c12e8a87b95e24F7F53d493E"
    },
    object: {
        type: "contract",
        address: "0x5180db8f5c931aae63c74266b211f580155ecac8",
        id: 3,
        extras: {
            device: "mobile",
            source: "homepage
        }
    };
})
```

### Specify related transactions

```javascript
stack.track("INITIATED_NFT_PURCHASE", {
    actor: {
        type: "wallet",
        address: "0x375892Bb243D35E4c12e8a87b95e24F7F53d493E"
    },
    object: {
        type: "contract",
        address: "0x5180db8f5c931aae63c74266b211f580155ecac8",
        id: 3,
        transactionHash: "0x5d0f516d4d526de5434dfe05a2fb6e93708e2f1d8910999059b46ae12b9331c3",
        extras: {
            device: "mobile",
            source: "homepage"
        }
    };
})
```