open-index/open-npm huggingface dataset:
npm package: @graphicscove/cms
Description: Lightweight CMS package for Next.js + Supabase projects.
Author: Graphics Cove
Latest version: 0.1.0

# @graphicscove/cms

Lightweight, opinionated CMS package for Next.js + Supabase projects.

## MVP scope

- Local `/admin` mount inside your app
- Built-in content models: pages, posts, navigation, settings, media
- Draft/published states
- Admin/editor role checks
- SQL migration for core tables
- Typed content query helpers

## Install

```bash
npm install @graphicscove/cms
```

## Required environment variables

```env
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
```

## Setup flow

1. Apply SQL migration from `migrations/001_init.sql` in your Supabase project.
2. Ensure your auth role source exists (default: `profiles.role` with values `admin` or `editor`).
3. Add `cms.config.ts` in your host project root.
4. Mount CMS under `app/admin/page.tsx`.
5. Create a Supabase storage bucket named `cms-media` (public) for image uploads.

## Example config

```ts
import { defineCMSConfig } from "@graphicscove/cms";

export default defineCMSConfig({
  siteName: "Graphics Cove",
  admin: { title: "Graphics Cove CMS" },
  collections: {
    pages: true,
    posts: true,
    navigation: true,
    media: true,
    settings: true
  },
  auth: {
    roleSource: "profiles.role",
    allowedRoles: ["admin", "editor"],
    allowEditorPublish: false
  }
});
```

## Example admin route (App Router)

```tsx
import config from "@/cms.config";
import { CMS } from "@graphicscove/cms";

export default function AdminPage() {
  return <CMS config={config} />;
}
```

## Auth expectations

- Host app handles sign-in/session lifecycle.
- `CMS` checks the current Supabase session and resolves role.
- Default role source: `profiles.role`.
- Optionally provide `auth.resolveRole` in config for custom logic.

## Content helper usage

```ts
import {
  getNavigationMenu,
  getPageBySlug,
  getPostBySlug,
  getPublishedPosts,
  getSiteSettings
} from "@graphicscove/cms";
```

Each helper accepts an existing Supabase client instance from your host app.

## Build / publish

```bash
npm run build
```

This package emits ESM output and type definitions into `dist/`.
npm package: @graphikartistry/cursor-doc-automation
Description: Cursor IDE extension for autonomous documentation and ticket management
Author: graphikartistry
Latest version: 1.0.1

# Cursor Documentation Automation Extension

This extension for Cursor IDE automates the process of generating documentation and managing tickets based on code changes.

## Features

- Automatic documentation generation from code changes
- Integration with Jira for ticket management
- GitHub pull request automation
- Technical documentation analysis
- Related components identification

## Installation

1. Clone this repository:
```bash
git clone https://github.com/yourusername/cursor-doc-automation.git
cd cursor-doc-automation
```

2. Install dependencies:
```bash
npm install
```

3. Build the extension:
```bash
npm run build
```

4. Create a `.env` file in the root directory with the following variables:
```env
FUELIX_API_URL=your_fuelix_api_url
FUELIX_API_KEY=your_fuelix_api_key
FUELIX_MODEL_NAME=your_model_name
JIRA_PROJECT_KEY=your_jira_project_key
JIRA_API_TOKEN=your_jira_api_token
JIRA_EMAIL=your_jira_email
JIRA_DOMAIN=your_jira_domain
GITHUB_TOKEN=your_github_token
GITHUB_REPOSITORY=your_github_repository
```

## Usage

1. Start the extension:
```bash
npm start
```

2. The extension will automatically:
   - Monitor code changes
   - Generate documentation
   - Create pull requests
   - Update Jira tickets

## Testing

Run the documentation automation test:
```bash
npm run test-docs
```

## Development

1. Make changes to the source code in the `src` directory
2. Build the extension:
```bash
npm run build
```
3. Test your changes:
```bash
npm run test-docs
```

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## License

This project is licensed under the MIT License - see the LICENSE file for details.
npm package: @graphikartistry/ide-doc-tool
Description: Cursor IDE extension for autonomous documentation and ticket management
Author: graphikartistry
Latest version: 1.0.0

# Cursor Documentation Automation Extension

This extension for Cursor IDE automates the process of generating documentation and managing tickets based on code changes.

## Features

- Automatic documentation generation from code changes
- Integration with Jira for ticket management
- GitHub pull request automation
- Technical documentation analysis
- Related components identification

## Installation

1. Clone this repository:
```bash
git clone https://github.com/yourusername/cursor-doc-automation.git
cd cursor-doc-automation
```

2. Install dependencies:
```bash
npm install
```

3. Build the extension:
```bash
npm run build
```

4. Create a `.env` file in the root directory with the following variables:
```env
FUELIX_API_URL=your_fuelix_api_url
FUELIX_API_KEY=your_fuelix_api_key
FUELIX_MODEL_NAME=your_model_name
JIRA_PROJECT_KEY=your_jira_project_key
JIRA_API_TOKEN=your_jira_api_token
JIRA_EMAIL=your_jira_email
JIRA_DOMAIN=your_jira_domain
GITHUB_TOKEN=your_github_token
GITHUB_REPOSITORY=your_github_repository
```

## Usage

1. Start the extension:
```bash
npm start
```

2. The extension will automatically:
   - Monitor code changes
   - Generate documentation
   - Create pull requests
   - Update Jira tickets

## Testing

Run the documentation automation test:
```bash
npm run test-docs
```

## Development

1. Make changes to the source code in the `src` directory
2. Build the extension:
```bash
npm run build
```
3. Test your changes:
```bash
npm run test-docs
```

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## License

This project is licensed under the MIT License - see the LICENSE file for details.
npm package: @graphile-contrib/constraint-error-tags
Description: A PostGraphile plugin for writing nicer error messages on constraints.
Author: Denis Badurina
Latest version: 1.1.0

# @graphile-contrib/constraint-error-tags

A PostGraphile plugin for writing nicer error messages on constraints. Adding the `@error <message>` smart tag to constraints will replace generic Postgres constraint violation message.

## Installation:

```bash
npm install --save @graphile-contrib/constraint-error-tags
```

or

```bash
yarn add @graphile-contrib/constraint-error-tags
```

## Usage:

**Library:**

```js
const {
  ConstraintErrorTagsPlugin,
  handleErrors,
} = require("@graphile-contrib/constraint-error-tags");

app.use(
  postgraphile(process.env.POSTGRES_ENDPOINT, process.env.POSTGRES_SCHEMA, {
    appendPlugins: [ConstraintErrorTagsPlugin],
    handleErrors: (errors) => handleErrors(errors),
  })
);
```

- `ConstraintErrorTagsPlugin` introspects all your constraints and extracts the ones with the `@error <message>` smart tag.
- `handleErrors` violating a constraint with the above mentioned signature will replace the generic error with the `<message>` from the `@error` smart tag.

## Example table constraint:

SQL schema:

```sql
create table public.user (
  id         serial primary key,
  first_name text not null,
  last_name  text not null,

  age int not null,
  constraint age_check check(age >= 18)
);

comment on constraint "age_check" on "public.user" is '@error The user has to be at least 18 years of age.';
```

GraphQL mutation:

```graphql
mutation {
  createUser(input: { firstName: "John", lastName: "Doe", age: 16 }) {
    clientMutationId
  }
}
```

Response:

GraphQL error with the message: `The user has to be at least 18 years of age.`

## Example type constraint:

SQL schema:

```sql
create domain strong_password as text
constraint "symbol" check (value ~ '[!@#$%^&*()]');

comment on constraint "symbol" on domain "strong_password" is '@error password must contain at least one symbol of !@#$%^&*()';
```

GraphQL mutation:

```graphql
mutation {
  setPassword(input: {userId: "100", newPass: "weakpassword"}) {
    clientMutationId
  }
}
```

Response:

GraphQL error with the message: `password must contain at least one symbol of !@#$%^&*()`
npm package: @graphile-contrib/pg-order-by-multi-column-index
Description: Order by multi-column indexes on PostGraphile connections
Author: Matt Bretl
Latest version: 1.0.0

# @graphile-contrib/pg-order-by-multi-column-index

[![Package on npm](https://img.shields.io/npm/v/@graphile-contrib/pg-order-by-multi-column-index.svg)](https://www.npmjs.com/package/@graphile-contrib/pg-order-by-multi-column-index)

This Graphile Engine plugin adds enum values to the `orderBy` argument on connections, allowing you to order by multi-column indexes.

> Requires `postgraphile@^4.1.0` or `graphile-build-pg@^4.1.0`

> NOTE: If you're not using `ignoreIndexes: false`, then you probably don't need this plugin.

PostGraphile's `ignoreIndexes: false` option only exposes the first column of each multi-column index on `orderBy`. This prevents clients from sending queries with an array of column names/directions that can't make use of the multi-column index. This plugin adds enum values to `orderBy` that match forward and backward scans of the index.

Example:

```sql
create index on p.person (last_name ASC, first_name ASC);
```

```graphql
{
  allPeople(orderBy: LAST_NAME_ASC__FIRST_NAME_ASC) {
    nodes {
      id
      firstName
      lastName
    }
  }
}
```

## Usage

Append this plugin and the additional `orderBy` enum values will be added to your schema.

### CLI

```bash
yarn add postgraphile
yarn add @graphile-contrib/pg-order-by-multi-column-index
npx postgraphile --append-plugins @graphile-contrib/pg-order-by-multi-column-index
```

### Library

```js
const express = require("express");
const { postgraphile } = require("postgraphile");
const PgOrderByMultiColumnIndexPlugin = require("@graphile-contrib/pg-order-by-multi-column-index");

const app = express();

app.use(
  postgraphile(process.env.DATABASE_URL, "app_public", {
    appendPlugins: [PgOrderByMultiColumnIndexPlugin],
    graphiql: true,
  })
);

app.listen(5000);
```
npm package: @graphile/lru
Description: Extremely simple zero-dependencies ES6 LRU (you probably want lru-cache instead)
Author: Benjie Gillam
Latest version: 5.0.0

# @graphile/lru

**You probably want [lru-cache](https://github.com/isaacs/node-lru-cache)
instead.**

This is an obsessively optimized LRU cache for Node.js, it forgoes features in
favour of performance, and is very marginally faster than node-lru-cache v6 in
certain circumstances (namely those that we care about inside the Graphile
internals). A performance comparison versus node-lru-cache v7 has not yet been
performed.

## Usage

```js
import LRU from "@graphile/lru";

// Construct an LRU cache
const lru = new LRU({
  // Maximum number of items to store (required)
  maxLength: 500, // Must be an integer at least 2

  // Optional callback to handle when a value is removed (both when LRU becomes
  // full and when LRU is reset)
  dispose(key, value) {
    console.log(`Disposing of key '${key}' with value '${inspect(value)}'`);
  },
});

const ANY_KEY_HERE = { foo: "bar" };
const ANY_VALUE_HERE = { randomNumber: () => 4 };
// Store a value
lru.set(ANY_KEY_HERE, ANY_VALUE_HERE);

// Retrieve a value
const value = lru.get(ANY_KEY_HERE);

// Clear the cache
lru.reset();
```

## Considering a pull request?

Pull requests that add features that aren't required by the Graphile suite are
unlikely to be entertained - use node-lru-cache instead!

Pull requests that improve performance should come with benchmarks, benchmark
scripts and explanation of technique. And if you pull it off without breaking
anything - YES PLEASE.

Pull requests that add documentation are welcome.
npm package: @graphinx/markdown
Description: To install dependencies:
Author: Ewen Le Bihan
Latest version: 0.11.0

# @graphinx/markdown

To install dependencies:

```bash
bun install
```

To run:

```bash
bun run index.ts
```

This project was created using `bun init` in bun v1.1.12. [Bun](https://bun.sh) is a fast all-in-one JavaScript runtime.