open-index/open-npm huggingface dataset:
npm package: @say8425/ra-language-korean
Description: Korean messages for react-admin, the frontend framework for building admin applications on top of REST/GraphQL services
Author: Cheon Park
Latest version: 3.16.1

# Korean Messages for React-Admin

[![npm version](https://img.shields.io/npm/v/@say8425/ra-language-korean?color=cb3837&logo=npm)](https://www.npmjs.com/package/@say8425/ra-language-korean)
[![GitHub Actions Test](https://github.com/say8425/ra-language-korean/workflows/Test/badge.svg)](https://github.com/say8425/ra-language-korean/actions?query=workflow%3ATest)
[![GitHub Actions Release](https://github.com/say8425/ra-language-korean/workflows/Release/badge.svg)](https://github.com/say8425/ra-language-korean/actions?query=workflow%3ARelease)
[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/say8425/ra-language-korean/blob/master/LICENSE)

Korean messages for [react-admin](https://github.com/marmelab/react-admin).

react-admin 한국어 번역입니다.

기존 번역된 i18n 을 참고하여 최대한 매끄럽게 작성하였으며,<br>
어투 또한 통일하였습니다. 

번역 제안등은 [issue](https://github.com/say8425/ra-language-korean/issues) 로 남겨주십시오.

## Installation

### Yarn

```shell
yarn add @say8425/ra-language-korean
```

### NPM

```shell
npm install --save @say8425/ra-language-korean
```

## Usage

```typescript jsx
import koreanMessages from 'ra-language-korean';
import polyglotI18nProvider from 'ra-i18n-polyglot';

const messages = {
    ko: koreanMessages
};
const i18nProvider = polyglotI18nProvider(locale => messages[locale], 'ko');

<Admin locale="ko" i18nProvider={i18nProvider}>
  ...
</Admin>
```

## License

MIT License
npm package: @sayan-dev/ghd
Description: Deploy to gh pages using cli
Author: Sayanta Bhattacharjee
Latest version: 1.0.3

# Deploy To Github
Push your code in 1 line with commit message and branch name

### Install   
-    `npm i @sayan-dev/ghd`

### Usage
- ghd commit  
    `ghd commit -m "Commit Message"`
- ghd push   
    `ghd push -b branch`
- ghd deploy  
    `ghd deploy -m "Commit Message" -b branch`

![npm (scoped)](https://img.shields.io/npm/v/@sayan-dev/ghd)
npm package: @sayanbiswas/typedcache
Description: Typesafe cache for Node.js
Author: Sayan Biswas
Latest version: 0.0.2

# typedcache

Typesafe in-memory caching for Node.js

## Installation

```sh
npm install @sayanbiswas/typedcache
```

## Usage

```ts
import { TypedCache } from 'typedcache';

const cache = new TypedCache<string, number>({
    debug: true,
    timeoutMs: 3000,
})

cache.set('foo', 1);
cache.set('bar', 2);

console.log(cache.get('foo')); // 1
console.log(cache.get('bar')); // 2
console.log(cache.get('baz')); // undefined
```

### Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

### License

This project is licensed under the terms of the [MIT license](LICENSE).
npm package: @sayankundu009/cypress-reporter
Description: A custom Cypress test reporter
Author: Sayan Kundu
Latest version: 2.0.4

# Cypress Test Reporter

A Cypress test reporter that generates structured test run data and can integrate with any custom test management API.

## Installation

```bash
npm install @sayankundu009/cypress-reporter
```

## Prerequisites

To use the Cypress Reporter, you will need to set up the following environment variables:

```
REPORTER_HOST: Test API instance domain name
REPORTER_API_KEY: Test API key
REPORTER_PROJECT_ID: Test project ID where test runs and results will be added
REPORTER_SUITE_ID: The Test suite ID associated with the test cases
REPORTER_RUN_NAME: The name of the test run (the execution time will be appended to this name when created)
```

Additionally, you may provide the `REPORTER_RUN_ID` environment variable to use an existing test run instead of creating a new one.

## Usage

Add the reporter to your Cypress configuration file (`cypress.config.ts` or `cypress.config.js`):

### ES Modules

```typescript
import { defineConfig } from 'cypress';
import CypressTestReporter from '@sayankundu009/cypress-reporter';

export default defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      CypressTestReporter(on, {
        host: process.env.REPORTER_HOST || "",
        apiKey: process.env.REPORTER_API_KEY || "",
        runId: process.env.REPORTER_RUN_ID || "",
        runName: process.env.REPORTER_RUN_NAME || "",
        outputFolder: "test-results/reporter",
        html: true, // Generates visual report
      });
    },
  },
});
```

### CommonJS

```javascript
const { defineConfig } = require('cypress');
const CypressTestReporter = require('@sayankundu009/cypress-reporter');

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      CypressTestReporter(on, {
        host: process.env.REPORTER_HOST || "",
        apiKey: process.env.REPORTER_API_KEY || "",
        runId: process.env.REPORTER_RUN_ID || "",
        runName: process.env.REPORTER_RUN_NAME || "",
        outputFolder: "test-results/reporter",
        html: true, // Generates visual report
      });
    },
  },
});
```
npm package: @sayankundu009/playwright-reporter
Description: A custom Playwright test reporter
Author: Sayan Kundu
Latest version: 2.0.3

# Playwright Test Reporter

A Playwright test reporter that generates structured test run data and can integrate with any custom test management API.

## Installation

```bash
npm install @sayankundu009/playwright-reporter
```

# Prerequisites

To use Reporter Reporter, you will need to set up the following environment variables:

```
REPORTER_HOST: Test api instance domain name
REPORTER_USERNAME: Test email 
REPORTER_PASSWORD: Test API key
REPORTER_PROJECT_ID: Test project ID where test runs and results will be added
REPORTER_SUITE_ID: The Test suite ID associated with the test cases
REPORTER_RUN_NAME: The name of the test run. (the execution time will be appended to this name on when created on Reporter)
````
Additionally, you may provide the REPORTER_RUN_ID environment variable to use an existing test run instead of creating a new one.


## Usage

```typescript
const config: PlaywrightTestConfig = {
  reporter: [
     ['@sayankundu009/playwright-reporter', { outputFolder: "test-results/reporter", html: true }]
  ]
  // ...
};

export default config;
```
npm package: @sayanriju/apidoc2postman
Description: A tool to generate Postman Collection scaffolds from Apidoc documentation.
Author: Sayan "Riju" Chakrabarti
Latest version: 1.1.7

A simple NPM cli/bin package to generate Postman Collection scaffolds from Apidoc documentations.

## Usage

* `cd` into a documentation folder generated by the `apidoc` application. By default, such folders are named `docs/` and contain the files `api_data.json` & `api_project.json` among others.

* Run the command `npx @sayanriju/apidoc2postman` inside the folder. It will write a JSON text to STDOUT, which may be written to a file using the shell's piping mechanism, like so:

  `npx @sayanriju/apidoc2postman > ~/myProject.postman_collection.json`
 
* The `~/myProject.postman_collection.json` file may now be imported into Postman as usual.
 Note that, the imported Postman Collection is just a skeleton/scaffold and as such will need to be heavily edited/fine-tuned.
npm package: @sayanriju/how-many-days-on-git-project
Description: A PoC Node CLI app to list how many days one has spent (tops!) on a git project
Author: Sayan "Riju" Chakrabarti
Latest version: 1.1.0

how-many-days-on-git-project
============================

A PoC Node CLI app to list how many days one has spent (tops!) on a git projec

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/how-many-days-on-git-project.svg)](https://npmjs.org/package/how-many-days-on-git-project)
[![CircleCI](https://circleci.com/gh/sayanriju/how-many-days-on-git-project/tree/master.svg?style=shield)](https://circleci.com/gh/sayanriju/how-many-days-on-git-project/tree/master)
[![Appveyor CI](https://ci.appveyor.com/api/projects/status/github/sayanriju/how-many-days-on-git-project?branch=master&svg=true)](https://ci.appveyor.com/project/sayanriju/how-many-days-on-git-project/branch/master)
[![Codecov](https://codecov.io/gh/sayanriju/how-many-days-on-git-project/branch/master/graph/badge.svg)](https://codecov.io/gh/sayanriju/how-many-days-on-git-project)
[![Downloads/week](https://img.shields.io/npm/dw/how-many-days-on-git-project.svg)](https://npmjs.org/package/how-many-days-on-git-project)
[![License](https://img.shields.io/npm/l/how-many-days-on-git-project.svg)](https://github.com/sayanriju/how-many-days-on-git-project/blob/master/package.json)

<!-- toc -->
# Usage
<!-- usage -->
# Commands
<!-- commands -->
npm package: @sayanriju/scaffold-crud-from-mongoose-model
Description: scaffold-crud-from-mongoose-model ======== [![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io) [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
Author: Sayan Riju Chakrabarti
Latest version: 1.2.5

scaffold-crud-from-mongoose-model
========
[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
[![License](https://img.shields.io/npm/l/mynewcli.svg)](https://github.com/sayanriju/mynewcli/blob/master/package.json)

Generates an opinionated set of REST route handlers (annotated with Apidoc syntax) for Node/Express to perform CRUD operations upon a Mongoose Model.

# Usage

### With npx
```
npx @sayanriju/scaffold-crud-from-mongoose-model /path/to/models/model1.js /path/to/rest/handlers
```
### Or, Install Globally
```
npm i -g @sayanriju/scaffold-crud-from-mongoose-model
scaffold-crud-from-mongoose-model /path/to/models/model1.js /path/to/rest/handlers
```
npm package: @sayaww/nomi-mono
Description: ```bash pnpm i @sayaww/nomi-mono" ```
Author: Leo Lin
Latest version: 0.0.46

# Installation

```bash
pnpm i @sayaww/nomi-mono"
```

## Usage

Set up styles and fonts in your root file:

```jsx
import '@sayaww/nomi-mono/style';
import '@fontsource/inter/400.css'; // optional
import '@fontsource/inter/500.css'; // optional
import '@fontsource/inter/700.css'; // optional
```

Import components:

```jsx
import { Button } from '@sayaww/nomi-mono';
```

## With storybook

```jsx
import '../src/style.css';
import '@fontsource/inter/400.css';
import '@fontsource/inter/500.css';
import '@fontsource/inter/700.css';
```

## Development

```bash
turbo dev
#http://localhost:6006
```

## Import themes

- In Tokens Studio in Figma, select `light` theme
- Export from Figma, choose Tools > Export > single file
- Uncheck `all token set`
- check `include parent key`
- save as `Light.json` and put into `figma-output` folder, then repeat for dark theme
- put all files into figma-output folder
- run `turbo build-token`
- Access theme in `src/themes/tokens.json`
- Migrate tokens manually to `tailwind.config.cjs `
  - See `/tokens/tokens-transformed-[dark | light].json`

## Developing UI

### Adding a new component

Use [shadcn/ui](https://ui.shadcn.com/docs/components/alert-dialog) to add components you want.

Or

1. Duplicate from "Template" folder in `src/components` with the component name.
2. Add the component name to `src/components/index.tsx`.

### Working on UI + your own project

If you are developing UI and other preoject at the same time, you'll need to let Tailwind knows when to compile your new class names.

`tailwind.config`

```ts
content: [
		"./index.html",
		"./*.mdx",
		"./src/components/*.{js,ts,jsx,tsx,mdx}",
		"./src/components/**/*.{js,ts,jsx,tsx,mdx}",
		"./src/components/**/*.{js,ts,jsx,tsx,mdx}",
		"../perp-onboarding/app/**/*.{js,ts,jsx,tsx,mdx}",
		"../otc-maker-ui/app/**/*.{js,ts,jsx,tsx,mdx}",
        // add new files to watch here
],
```

`package.json`

```json
		"dev": "tsup src/components/index.tsx --format esm,cjs --dts --watch src --watch ../perp-onboarding/app --watch <your path>  & storybook dev -p 6006",
```

## Publish

```
turbo ship
```

## Publish storybook to Chromatic

```bash
turbo chromatic
```

## Embed Story in website

Get `url` from the [top right corner of a story](https://nomi-workshop.vercel.app/?path=/story/atomic-button--default).