open-index/open-npm huggingface dataset:
npm package: @softeng-761-2025-team-10/aframe-inspector
Description: A visual inspector tool for A-Frame.
Latest version: 1.0.8

# A-Frame Inspector

A visual inspector tool for [A-Frame](https://aframe.io) scenes. Just hit
`<ctrl> + <alt> + i` on any A-Frame scene to open up the Inspector.

- [Documentation / Guide](https://aframe.io/docs/master/introduction/visual-inspector-and-dev-tools.html)
- [Example](https://aframe.io/aframe-inspector/examples/)

Also check out:

- [A-Frame Watcher](https://github.com/supermedium/aframe-watcher) - Companion server to sync changes to HTML files.

![Inspector Preview](https://user-images.githubusercontent.com/674727/50159991-fa540c80-028c-11e9-87f1-72c54e08d808.png)

## Using the Inspector

### Keyboard Shortcut

A-Frame comes with a **keyboard shortcut** to inject the inspector. Just open
up any A-Frame scene (running at least A-Frame v0.3.0) and press **`<ctrl> +
<alt> + i`** to inject the inspector, just like you would use a DOM inspector:

### Specifying Inspector Build

This is done with the `inspector` component. By default, this is set on the
scene already. If we want, we can specify a specific build of the Inspector to
inject by passing a URL. For debugging:

```html
<a-scene inspector="url: http://localhost:3333/dist/aframe-inspector.js">
  <!-- Scene... -->
</a-scene>
```

To use the master branch of the Inspector:

```html
<a-scene inspector="url: https://cdn.jsdelivr.net/gh/aframevr/aframe-inspector@master/dist/aframe-inspector.min.js">
</a-scene>
```

## Local Development

```bash
git clone git@github.com:aframevr/aframe-inspector.git
cd aframe-inspector
npm install
npm start
```

Then navigate to __[http://localhost:3333/examples/](http://localhost:3333/examples/)__

## Self-hosting the sample-assets directory

The textures modal is using https://aframe.io/sample-assets/dist/images.json
to get the available textures.
The GitHub repository for those assets is https://github.com/aframevr/sample-assets

If you want to self-host this directory, do the following:

```bash
cd examples
git clone git@github.com:aframevr/sample-assets.git
```

edit `index.html` and define before any script tag this global variable:

```html
<script>window.AFRAME_SAMPLE_ASSETS_ROOT = "./sample-assets/";</script>
```

## Config overrides

Since A-Frame 1.7.0, the inspector perspective camera position is kept in sync with the A-Frame
active camera. This means you can move around the scene, toggle the inspector and you will be at the same position.
If you want to disable that behavior, you can do that by defining a global variable like this:

```html
<script>
  window.AFRAME_INSPECTOR_CONFIG = { copyCameraPosition: false };
</script>
```
npm package: @softengy/classnames
Description: A package to evaluate an array and convert to a string
Author: Wilbert Bocanegra Velazquez / Core Team
Latest version: 2.0.1


# A package to evaluate an array and convert to a string

A minimal package based to classNames package

## Authors

- [@WilbertBocanegra](https://www.github.com/WilbertBocanegra)


## Usage/Examples

```javascript
classNames('foo', 'bar'); // => 'foo bar'
classNames('foo', { bar: true }); // => 'foo bar'
classNames({ 'foo-bar': true }); // => 'foo-bar'
classNames({ 'foo-bar': false }); // => ''
classNames({ foo: true }, { bar: true }); // => 'foo bar'
classNames({ foo: true, bar: true }); // => 'foo bar'

// lots of arguments of various types
classNames('foo', { bar: true, duck: false }, 'baz', { quux: true }); // => 'foo bar baz quux'

// other falsy values are just ignored
classNames(null, false, 'bar', undefined, 0, 1, { baz: null }, ''); // => 'bar 1'

var arr = ['b', { c: true, d: false }];
classNames('a', arr); // => 'a b c'

let buttonType = 'primary';
classNames({ [`btn-${buttonType}`]: true });
```
npm package: @softeq/angular-mls-ri
Description: Reference implementation of @softeq/mls contract
Latest version: 1.0.0-beta.1

# @softeq/angular-mls-ri

Reference implementation of [`@softeq/mls`](../mls-lib/README.md) contract.

`@softeq/angular-mls-ri` is based on
* `@ngx-translate/core` to provide translations
* embedded Angular capabilities for number & date formatting
* and implements the simplest parsing of number & date values. 

## Setup

To work with this library it should be properly initialized.

1. First of all you have to initialize `TranslateModule` from `@ngx-translate/core` library.
   ```typescript
   @NgModule({
     imports: [
       TranslateModule.forRoot({
         ...
       }),
     ],
     ...   
   })
   ```
2. Define number and date formats used to format/parse dates and numbers.
 If you store your translations (used by `@ngx-translate` library) in the `json` file its content may look like
   ```json
   {
    "$localization": {
      "numberFormat": {
        "decimalSeparator": ".",
        "groupSeparator": ",",
        "grouping": true
      },
      "dateFormat": {
        "shortDate": "M/d/yyyy",
        "dayMonth": "MMM d",
        "monthYear": "M/yyyy",
        "dateA11y": "MMMM/d/yyyy",
        "monthYearA11y": "MMMM/yy",
        "shortMonthYear": "MMM yy",
        "shortTime": "h:mm a",
        "shortDatetime": "M/d/yyyy h:mm a",
        "mediumDateAndWeekday": "MMM d yyyy, EE"
      }
    },
    ...
   }
   ```
   All formats should be defined under `$localization` field.
   The main idea is to make localization structure available when it is retrieved by `TranslateService`
    using `$localization` key
   ```typescript
   this.translate.instant('$localization'); // should retrieve localization structure
   ```
   Localization structure MUST define number & date formats under the corresponding fields as in the example above.
   Read here below about structure of these fields
3. Add `SofteqMlsRiModule` module into `imports` section of root `NgModule`
   ```typescript
   @NgModule({
     imports: [
       TranslateModule.forRoot({
         ...
       }),
       SofteqMlsRiModule.forRoot(),
     ],
     ...   
   })
   ```

#### Number Format

Number format should consist of the following fields
* `decimalSeparator` is a decimal separator
* `grouping` whether to use grouping
* `groupSeparator` is a character used to separate groups

#### Date Format

Date format defines set of named formats, like `M/d/yyyy` or `MMM d`.
* formatting of dates works according to the rules used by `DatePipe`
* parsing of dates currently supports only digit-only formats, like `M/d/yyyy` or `h:mm a`.

## Restrictions

* Date and number formats are retrieved using `TranslateService#instant` call.
 This means that translations should be loaded before `MlsProvider` is used first time.
 You should care about this yourself.
npm package: @softeq/mls
Description: Contract for locale-dependent operations
Latest version: 1.0.0-beta.1

# @softeq/mls

`@softeq/mls` defines **CONTRACT** for main locale-dependent operations.
 The primary focus of this library is other locale-dependent libraries that require multi-language support (**MLS**).
 Such libraries can rely on operations defined in `@softeq/mls` library and does not depend on specific MLS implementation.  
It is important to note that **`@softeq/mls` defines only contract rather than implementation**.

`@softeq/mls` provides the following locale-dependent operations:
* number & date formatting/parsing,
* providing of text translation,
* providing of current locale.

It is implementation of `@softeq/mls` contract that provides these operations.
List of current implementations can be found here below.

Although this library was initially designed for Angular, now it does not depend on Angular core
 and can be used for other frameworks or core libraries (just in theory).

## Implementations of `@softeq/mls` contract

* [`@softeq/angular-mls-ri`](../angular-mls-ri-lib/README.md) is a reference implementation for Angular that relies on
  * `@ngx-translate/core` to provide translations
  * embedded Angular capabilities for number & date formatting
  * and implements the simplest parsing of number & date values.
npm package: @softerist/heuristic-mcp
Description: An enhanced MCP server providing intelligent semantic code search with find-similar-code, recency ranking, and improved chunking. Fork of smart-coding-mcp.
Author: Softerist
Latest version: 3.2.13

# Heuristic MCP Server

Heuristic MCP adds smart code search to your editor or MCP client.

## Requirements

- Node.js `18+`
- npm (for global install)
- Internet access at least once to download the embedding model (if install-time download is skipped, it downloads on first run)
- 64-bit Node.js recommended for native ONNX performance; on Windows, install Microsoft Visual C++ 2015-2022 Redistributable (x64) if native bindings fail

## Install

```bash
npm install -g @softerist/heuristic-mcp
```

Then enable it for your client:

```bash
heuristic-mcp --start
```

If your editor was already open, reload it once.

## How It Works

1. The server scans your workspace and builds a searchable index of your code.
2. IDE AI models/MCP tools query that index using plain language so you can find relevant code quickly.
3. Results improve as your index stays up to date with project changes.

## Basic Commands

```bash
heuristic-mcp --status
heuristic-mcp --logs
heuristic-mcp --stop
```

Use `heuristic-mcp --status` first if something looks off.
Use `heuristic-mcp --cache` to see the cache status or file index progress.

## Advanced Docs

Detailed configuration, tool reference, troubleshooting, and release notes are in:

- [`docs/GUIDE.md`](docs/GUIDE.md)
- [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md)

License: MIT
npm package: @softfix/code-standards
Description: Company code standards for naming conventions in React, Next.js, Node.js, and TypeScript
Author: VIKAS KUMAR VERMA
Latest version: 1.0.0

# @softfix/code-standards

🚀 **Enforce Consistent Code Standards Across Projects**

This package ensures consistent naming conventions for files, functions, variables, and interfaces in React, Next.js, Node.js, and TypeScript projects.

---

## 📦 Installation

```bash
npm install --save-dev @softfix/code-standards
```

---

## 🚀 Usage

### Run Pre-commit Checks Manually
```bash
npx softfix-precommit
```
This command performs the following checks:
- **File Names:** Must be lowercase and kebab-case (e.g., `my-component.tsx`).
- **Functions:** Must use camelCase (e.g., `fetchData`).
- **Variables:** Must use camelCase or UPPER_CASE.
- **Interfaces:** Must use PascalCase and start with `I` (e.g., `IUserProfile`).

✅ If any rule is violated, the pre-commit will fail and show the list of issues.

---

## 🧩 Examples

### ✅ File Names
- **Correct:** `user-profile.ts`, `order-list.component.tsx`
- **Incorrect:** `UserProfile.ts`, `order_list.tsx`

### ✅ Function Names
```ts
// ✅ Correct
function getUserDetails() {}

// 🚫 Incorrect
function GetUserDetails() {}
function get_user_details() {}
```

### ✅ Variable Names
```ts
// ✅ Correct
const userName = 'John';
const API_KEY = '12345';

// 🚫 Incorrect
const UserName = 'John';
const apiKey = '12345';
```

### ✅ Interface Names
```ts
// ✅ Correct
interface IUser {
  id: number;
  name: string;
}

// 🚫 Incorrect
interface user {
  id: number;
  name: string;
}
interface UserInterface {} // Should start with 'I'
```

---

## 🛠️ Why Use This Package?
✅ Automates code standard checks for faster development workflows
✅ Reduces code review time and improves code quality
✅ Seamlessly enforces company-wide coding standards
✅ Keeps naming conventions consistent across all projects
✅ Easily integrates with existing development pipelines and tools
✅ Prevents common naming mistakes before code is committed
✅ Saves time by catching issues early in the development cycle
✅ Enhances team collaboration through standardized code practices
✅ Provides clear, actionable feedback for quick fixes
✅ Supports scalable codebases by maintaining clean and organized code
✅ Works out of the box with minimal configuration
✅ Increases project maintainability and reduces technical debt

---

💻 **Keep your codebase clean, consistent, and error-free with @softfix/code-standards!**
npm package: @softfix/frontend-structurecli
Description: CLI tool to generate a React and Next.js project folder structure with TypeScript, ES6 modules, and feature-based architecture.
Author: VIKAS KUMAR VERMA
Latest version: 1.4.1

# Softfix Frontend Structure CLI

## 🚀 Description
**Softfix Frontend Structure CLI** is a command-line tool that helps you quickly scaffold a clean and scalable folder structure for React and Next.js projects using TypeScript and ES6 modules. It follows a feature-based architecture to enhance maintainability and scalability.

---

## 📦 Installation
Install the CLI globally using npm:

```bash
npx @softfix/frontend-structurecli
```

---



### 💡 Steps:
1. Run the command above.
2. Enter your desired project name when prompted.
3. The tool will create a fully structured project folder with a `README.md` inside.

---

## 📁 Folder Structure Example
```
my-project-name/
├── public/
│   └── assets/
├── src/
│   ├── app/
│   │   ├── routes/
│   │   ├── app.tsx
│   │   ├── provider.tsx
│   │   └── router.tsx
│   ├── components/
│   ├── config/
│   ├── features/
│   │   └── awesome-feature/
│   │       ├── api/
│   │       ├── assets/
│   │       ├── components/
│   │       ├── hooks/
│   │       ├── stores/
│   │       ├── types/
│   │       └── utils/
│   ├── hooks/
│   ├── lib/
│   ├── stores/
│   ├── testing/
│   ├── types/
│   └── utils/
└── README.md
```

---

## 📝 License
MIT License

---

## 🙌 Contributing
Contributions are welcome! Feel free to open an issue or submit a pull request.

---

## 🌐 Links
- **npm:** [@softfix/frontend-structurecli](https://www.npmjs.com/package/@softfix/frontend-structurecli)
- **GitHub:** [Repository Link](#) *(replace with actual repo link if available)*