open-index/open-npm huggingface dataset:
npm package: @quinus/tailwind-zed-one-dark
Description: Reusable Tailwind v4 theme package based on Zed One Dark core UI colors.
Author: quinus
Latest version: 0.1.0

# @quinus/tailwind-zed-one-dark

Reusable Tailwind v4 theme package based on Zed One Dark core UI colors.

## Install

```bash
npm install @quinus/tailwind-zed-one-dark
```

## Use with Tailwind v4

Import the theme in your app CSS file:

```css
@import "tailwindcss";
@import "@quinus/tailwind-zed-one-dark/theme.css";
```

Then use semantic or namespaced color utilities:

```html
<main class="bg-background text-foreground border border-border">
  <button class="bg-primary text-background">Action</button>
  <p class="text-zed-one-text-muted">Muted text</p>
</main>
```

To scope the theme to a subtree, add `theme-zed-one-dark` on a container:

```html
<section class="theme-zed-one-dark">
  ...
</section>
```

## JavaScript/TypeScript exports

```ts
import { zedOneDark, zedOneDarkSemantic } from '@quinus/tailwind-zed-one-dark';
```

- `zedOneDark`: full snapshot with metadata and raw color tokens.
- `zedOneDarkSemantic`: convenience semantic token map.

## Token source

The package includes a checked-in snapshot from Zed’s official One theme JSON (`One Dark`, appearance `dark`):

- Source: https://raw.githubusercontent.com/zed-industries/zed/main/assets/themes/one/one.json
- Snapshot date: 2026-02-24

## Development

```bash
npm install
npm run check
npm run build
npm pack
```

## Publish from GitHub Actions

This package is configured to build and publish from GitHub (not your local machine).

1. In GitHub repo settings, add an Actions secret named `NPM_TOKEN` with an npm automation token.
2. Bump the package version and push:

```bash
npm version patch
git push && git push --tags
```

3. Create a GitHub Release from that tag.
4. The `Publish to npm` workflow will run `npm ci`, `npm run prepublishOnly`, and `npm publish --access public`.

## Example app

Run the minimal local example from the repository root:

```bash
cd example
npm install
npm run build
```

Then open the HTML file in your browser.

## License

MIT
npm package: @quipugmbh/react-datetimecombo
Description: A complete React datetime picker component with a convenient design.
Author: Goce Dokoski goce.dokoski@quipu.de
Latest version: 0.1.16

# react-datetimecombo

A React date and time picker written in ES6 with elegance and performance in mind.


## Installation

Install using npm:
```sh
npm install --save @quipugmbh/react-datetimecombo
```


## Example Usage

```jsx
import DateTimeCombo from '@quipugmbh/react-datetimecombo'
import '@quipugmbh/react-datetimecombo/react-datetimecombo.css'
...

render: function() {
    return <DateTimeCombo 
        
        // Important: Set either value or defaultValue!
        
        //connect state value to use datetimecombo picker as a controlled component
        value={this.state.value}
        
        //or: use default value to use datetimecombo picker as an uncontrolled component
        defaultValue={moment()}                     

        // any format supported by moment.js (for example: "hh:mm a" for a 12 hour clock)
        dateTimeFormat="DD.MM.YYYY HH:mm"

        // hide the datepicker after a day is selected
        closeOnSelect={true}
        placeholder="Select a date..."

        // the picker calls this function for every year, month and day that are currently
        // displayed, passing a moment object and a granularity string
        isValidDate={ (date, granularity) =>
            granularity==='day'                     
            && date.isAfter(moment("1995-12-25"))
        }

        // callback on every date change
        onChange={date =>
            alert('Day changed to ' + date.format())
        }

        // prevent callback when changing months or years
        fireCallbackOnYearChange = false
	    fireCallbackOnMonthChange = false

        // disable weekends (Saturday and Sunday)
        disabledDaysOfWeek = {[5,6]}

        // disable specific dates
        disabledDates = {[ "2015-12-10, 2018-05-05"]}

        // format in which disabled dates are specified
        disabledDatesFormat="YYYY-MM-DD"            
    />;
}
```


**Please also import a copy of the [CSS stylesheet](https://raw.githubusercontent.com/gocedoko/react-datetimecombo/master/react-datetimecombo.css) in your application. Feel free to modify the styles according to your needs.**


## Developement
If you want to do developement:
1. git clone https://github.com/gocedoko/react-datetimecombo
2. cd react-datetimecombo
3. npm install
4. npm run dev

### [Changelog](CHANGELOG.md)

### [MIT Licensed](LICENSE.md)
npm package: @quipuswap/tokens-whitelist
Description: MadFish Whitelisted tokens
Author: MadFish Solutions
Latest version: 1.1.29

# Tezos tokens whitelist

This repo includes a JSON and schema for token lists.

The JSON schema represents the technical specification for a token list which can be used in a dApp interface, such as the QuipuSwap Interface.

## What are token lists?

QuipuSwap Token Lists is a specification for lists of token metadata (e.g. address, decimals, ...) that can be used by any dApp interfaces that needs one or more lists of tokens.

Anyone can create and maintain a token list, as long as they follow the specification.

Specifically an instance of a token list is a [JSON](https://www.json.org/json-en.html) blob that contains a list of
TZIP-12 / TZIP-16 token metadata for use in dApp user interfaces.
Token list JSON must validate against the [JSON schema](https://json-schema.org/) in order to be used in the QuipuSwap Interface.
Tokens on token lists, and token lists themselves, are tagged so that users can easily find tokens.

## Semantic versioning

Lists include a `version` field, which follows [semantic versioning](https://semver.org/).

List versions must follow the rules:

- Increment major version when tokens are removed
- Increment minor version when tokens are added
- Increment patch version when tokens already on the list have minor details changed (name, symbol, logo URL, decimals)

Changing a token address or chain ID is considered both a remove and an add, and should be a major version update.

Note that list versioning is used to improve the user experience, but not for security, i.e. list versions are not meant
to provide protection against malicious updates to a token list; i.e. the list semver is used as a lossy compression
of the diff of list updates. List updates may still be diffed in the client dApp.

## Examples

You can find a simple example of a token list in [schema/example.whitelist.json](schema/example.whitelist.json).
npm package: @quiq/react-linkify
Description: React component to parse links (urls, emails, etc.) in text into clickable links
Author: Tasti Zakarie
Latest version: 0.2.5

# [react-linkify](http://tasti.github.io/react-linkify/)
React component to parse links (urls, emails, etc.) in text into clickable links

## Examples

Live examples are available at [http://tasti.github.io/react-linkify/](http://tasti.github.io/react-linkify/).

### Basic

Any link that appears inside the `Linkify` component will become clickable.

```
<Linkify>See examples at tasti.github.io/react-linkify/.</Linkify>
```

Renders to:

See examples at `tasti.github.io/react-linkify/`.

### Advanced

If you're feeling lazy, you can wrap `Linkify` around anywhere that you want links to become clickable. Even with nested elements, it traverses the tree to find links.

```
<Linkify>
  <div>react-linkify <span>(tasti.github.io/react-linkify/)</span></div>
    <div>React component to parse links (urls, emails, etc.) in text into clickable links</div>
  See examples at tasti.github.io/react-linkify/.
    <footer>Contact: tasti@zakarie.com</footer>
</Linkify>
```

Renders to:

react-linkify (`tasti.github.io/react-linkify/`)  
React component to parse links (urls, emails, etc.) in text into clickable links  
See examples at `tasti.github.io/react-linkify/`.  
Contact: `tasti@zakarie.com`


## Installation

```
npm install react-linkify --save
```

## Usage

```js
var Linkify = require('react-linkify');

React.render(
  <Linkify>Examples are available at tasti.github.io/react-linkify/.</Linkify>,
  document.body
);
```

## Props

**component**  
The type of component to wrap links in.  
_type:_ `any`  
_default:_ `'a'`  

**properties**  
The props that will be added to every matched component.  
_type:_ `object`  
_default:_ `{}`

NOTE: Use `Linkify.MATCH` as a value to specify the matched link. The properties prop will always contain `{href: Linkify.MATCH, key: 'LINKIFY_KEY_#'}` unless overridden.


## Customization

You can access to the global `Linkify` instance used to linkify contents by importing it (`import { linkify } from 'react-linkify'`).
That way you can customize as needed (e.g. disabling existing schemas or adding new ones).

Note that any customization made to that instance will affect every `Linkify` component you use.

## Examples

All kind of links detectable by
[linkify-it](https://github.com/markdown-it/linkify-it) are supported. For
examples, visit [their website](http://markdown-it.github.io/linkify-it/).
npm package: @quire-io/n8n-nodes-quire
Description: n8n community node for Quire project management platform integration
Author: admin
Latest version: 0.1.2

# n8n-nodes-quire

This is an n8n community node. It lets you use quire service in your n8n workflows.

Quire is a project management applications that improve your productivity.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/reference/license/) workflow automation platform.

- [Installation](#installation)  
- [Operations](#operations)  
- [Credentials](#credentials)
- [Resources](#resources)  

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

### Task
- **Create**: Create a new task
- **Get**: Get a task by ID
- **Get by OID**: Get a task by OID
- **Get Many**: Get all tasks in a project
- **Update**: Update an existing task

### Comment
- **Create**: Create a new comment for a task
- **Get Many**: Get all comments for a task

### Project
- **Get Many**: Get all accessible projects

### User
- **Get Many**: Get all accessible users

### Tag
- **Get Many**: Get all tags in a project

### Sublist
- **Get Many**: Get all sublists in a project

### Partner
- **Get Many**: Get all partners in an organization

### Search
- **Find Task in Project**: Find tasks in a project
- **Find User**: Find a user by email or ID

## Credentials

To use this node, you need to set up OAuth2 credentials for Quire in n8n:

1. Log in to Quire and create a Quire App to obtain your Client ID and Client Secret.
2. In n8n, go to the **Credentials** page and add new credentials for **Quire OAuth2 API**.
3. Enter your Quire App's Client ID and Client Secret in the corresponding fields.
4. Copy the **OAuth Redirect URL** shown in n8n and add it to your Quire App's Redirect URI settings.
5. Save the credentials, then click **Connect my account** and authorize access to your Quire projects.

> Reference: [n8n credentials setup guide](https://docs.n8n.io/credentials/add-edit-credentials/)

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
* [Quire App Directory](https://quire.io/apps)