open-index/open-npm huggingface dataset:
npm package: @glimmer/app-compiler
Description: Broccoli tooling for Glimmer-VM based applications
Latest version: 1.1.2

# @glimmer/app-compiler

A broccoli plugin that wraps Glimmer's optimizing compiler for producing the required pre-computed objects for Glimmer VM based applications.

## Basic Usage

For most apps the plugin can be used as the following:

```ts
import { BundleCompiler } from '@glimmer/app-compiler';
...

let optimizedApp = BundleCompiler(app, {
  projectPath: 'my-app',
  mode: 'module-unification'
});

return optimizedApp;
```

## Advanced Usage

If you need to do more advanced things like registering AST plugins or using custom project layout you can do something like the following:

```ts
import { BundleCompiler } from '@glimmer/app-compiler';
import { BundleCompilerDelegate } from '@glimmer/compiler-delegates'
...

class MyCustomCompilerDelegate implements BundleCompilerDelegate {
  ...
}

let optimizedApp = BundleCompiler(app, {
  projectPath: 'my-app',
  delegate: MyCustomCompilerDelegate,
  outputFiles: {
    heapFile: 'snowflake/location/template.gbx',
    dataSegment: 'snowflake/data.js'
  },
  bundleCompiler: {
    plugins: [MyASTPlugin]
  }
});

return optimizedApp;
```

### Options

```ts
interface GlimmerBundleCompilerOptions {
  projectPath: string;                      // where the project is at
  bundleCompiler: BundleCompilerOptions;    // Options specifically for the compiler
  outputFiles?: OutputFiles;                // Where to write the output
  delegate?: BundleCompilerDelegateConstructor; // Delegate to discover information about templates
  mode?: 'module-unification';              // Builtin delegate
}

interface BundleCompilerDelegateConstructor {
  new(): BundleCompilerDelegate;
}

export interface OutputFiles {
  dataSegment: Option<string>;
  heapFile: Option<string>;
}

interface BundleCompilerOptions {
  plugins?: ASTPluginBuilder[];
}
```
npm package: @glimmer/application
Description: Glimmer standalone applications
Latest version: 1.1.2

# @glimmer/application
[![npm version](https://badge.fury.io/js/%40glimmer%2Fapplication.svg)](https://badge.fury.io/js/%40glimmer%2Fapplication)
[![Build Status](https://secure.travis-ci.org/glimmerjs/glimmer-application.svg?branch=master)](http://travis-ci.org/glimmerjs/glimmer-application)

## Installation

Add this package to your project with Yarn:

```bash
yarn add @glimmer/application
```

Or alternatively with npm:

```bash
npm install --save-dev @glimmer/application
```


## Development

For the development of this project, Yarn is preferred over npm. However, any Yarn command can be replaced by the npm equivalent.
See [Migration from npm](https://yarnpkg.com/lang/en/docs/migrating-from-npm/) in the Yarn documentation for a list of the equivalent commands.

* Clone repository locally: `git clone https://github.com/glimmerjs/glimmer-application.git`
* Install dependencies: `yarn`, or `yarn install`
* Open project in your editor of choice and make your changes
* Run tests: `yarn run test`

## Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/glimmerjs/glimmer-application.


## Acknowledgements

Thanks to [Monegraph](http://monegraph.com) for funding the initial development
of this library.

## License

MIT License.
npm package: @glimmer/application-test-helpers
Description: Test helpers for developing @glimmer/component and @glimmer/application
Latest version: 1.1.2

# @glimmer/application-test-helpers

[![npm version](https://badge.fury.io/js/%40glimmer%2Fapplication-test-helpers.svg)](https://badge.fury.io/js/%40glimmer%2Fapplication-test-helpers)

This project contains test helpers used to develop the
[@glimmer/application](https://github.com/glimmerjs/glimmer-application) and
[@glimmer/component](https://github.com/glimmerjs/glimmer-component)
packages.

This project _is not_ intended for testing Glimmer applications.

## Installation

Add this package to your project with Yarn:

```bash
yarn add @glimmer/application-test-helpers
```

Or alternatively with npm:

```bash
npm install --save-dev @glimmer/application-test-helpers
```

## Development

For the development of this project, Yarn is preferred over npm. However, any Yarn command can be replaced by the npm equivalent.
See [Migration from npm](https://yarnpkg.com/lang/en/docs/migrating-from-npm/) in the Yarn documentation for a list of the equivalent commands.

* Clone repository locally: `git clone https://github.com/glimmerjs/glimmer-application-test-helpers.git`
* Install dependencies: `yarn`, or `yarn install`
* Open project in your editor of choice and make your changes
* Run tests: `yarn run test`

## Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/glimmerjs/glimmer-application-test-helpers.

## Acknowledgements

Thanks to [Monegraph](http://monegraph.com) for funding the initial development
of this library.

## License

MIT License.
npm package: @glimmer/build
Description: Build tooling for Glimmer packages.
Latest version: 0.10.3

# glimmer-build [![Build Status](https://secure.travis-ci.org/glimmerjs/glimmer-build.svg?branch=master)](http://travis-ci.org/glimmerjs/glimmer-build)

Build tooling for Glimmer libraries.

## Acknowledgements

Thanks to [Monegraph](http://monegraph.com) for funding the initial development
of this library.

## License

MIT License.
npm package: @glimmer/component
Description: Glimmer component library
Latest version: 2.1.1

# @glimmer/component

[![npm version](https://badge.fury.io/js/%40glimmer%2Fcomponent.svg)](https://badge.fury.io/js/%40glimmer%2Fcomponent)
[![CI](https://github.com/emberjs/ember.js/workflows/CI/badge.svg)](https://github.com/emberjs/ember.js/actions?query=workflow%3ACI)

## Installation

Add this package to your project:

```bash
npm install --save-dev @glimmer/component
```

## Usage

To use this in a Glimmer application, import the package and export an extended class:

```glimmer-ts
import Component from '@glimmer/component';

export default class MyComponent extends Component {
  get doubled() {
    return this.args.foo * 2;
  }

  <template>
    {{@foo}} * 2 === {{this.doubled}}
  </template>
}
```

## Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/emberjs/ember.js

## License

MIT License.
npm package: @glimmer/inline-precompile
Description: Use tagged template strings to precompile glimmer templates inside your JS files.
Author: Robert Jackson
Latest version: 1.0.1

# @glimmer/inline-precompile

Allows compile time replacement of inline templates (inside your *.ts or *.js files) via:

```js
import hbs from '@glimme/inline-precompile';

let template = hbs`some template {{here}}`;
```
npm package: @glimmer/resolver
Description: Resolver for Glimmer apps.
Latest version: 0.4.3

# glimmer-resolver [![Build Status](https://secure.travis-ci.org/glimmerjs/glimmer-resolver.svg?branch=master)](http://travis-ci.org/glimmerjs/glimmer-resolver)

A resolver for both Ember and Glimmer applications that is compliant with the
interfaces defined in [glimmer-di](https://github.com/glimmerjs/glimmer-di) and
the expectations of Ember's
[module unification RFC](https://github.com/emberjs/rfcs/blob/master/text/0143-module-unification.md).

## Acknowledgements

Thanks to [201 Created](http://www.201-created.com/),
[Monegraph](http://monegraph.com), and [Cerebris](http://www.cerebris.com) for
funding the initial development of this library.

## License

MIT License.
npm package: @glimmer/resolver-configuration-builder
Description: Broccoli plugin for building a resolver configuration compatible with the @glimmerjs/resolver.
Latest version: 0.1.2

# resolver-configuration-builder [![Build Status](https://secure.travis-ci.org/glimmerjs/resolver-configuration-builder.svg?branch=master)](http://travis-ci.org/glimmerjs/resolver-configuration-builder)

A Broccoli plugin for building a resolver configuration compatible with
[@glimmerjs/resolver](https://github.com/glimmerjs/glimmer-resolver).

## License

MIT License.
npm package: @glimmer/test-helpers
Description: Test helpers for Glimmer applications
Latest version: 0.31.2

# @glimmer/test-helpers

[![npm version](https://badge.fury.io/js/%40glimmer%2Ftest-helpers.svg)](https://badge.fury.io/js/%40glimmer%2Ftest-helpers)

[![Build Status](https://travis-ci.org/glimmerjs/glimmer-test-helpers.svg?branch=master)](https://travis-ci.org/glimmerjs/glimmer-test-helpers)

## Installation

Add this package to your project with Yarn:

```bash
yarn add @glimmer/test-helpers
```

Or alternatively with npm:

```bash
npm install --save-dev @glimmer/test-helpers
```

## Development

For the development of this project, Yarn is preferred over npm. However, any Yarn command can be replaced by the npm equivalent.
See [Migration from npm](https://yarnpkg.com/lang/en/docs/migrating-from-npm/) in the Yarn documentation for a list of the equivalent commands.

* Clone repository locally: `git clone https://github.com/glimmerjs/glimmer-test-helpers.git`
* Install dependencies: `yarn`, or `yarn install`
* Open project in your editor of choice and make your changes
* Run tests: `yarn run test`

## Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/glimmerjs/glimmer-test-helpers.

## License

MIT License.
npm package: @glimmer/vm-babel-plugins
Description: Compiles out VM assertion and deprecation utilities and debug tooling based on environment
Author: Tom Dale
Latest version: 0.93.5

# @glimmer/vm-babel-plugins

This package is meant to be used by hosting environments which use the Glimmer VM.
It exports a function which returns an array of babel plugins that should be
added to your Babel configuration.

```js
let vmBabelPlugins = require("@glimmer/vm-babel-plugins");

module.exports = {
  plugins: [...vmBabelPlugins({ isDebug: true })],
};
```

These plugins will remove debug tooling and assertions based on the `isDebug`
option. Currently, this is the only available option.
npm package: @glimmer/web-component
Description: Render Glimmer components with custom elements
Latest version: 0.3.1

# @glimmer/web-component [![Build Status](https://secure.travis-ci.org/glimmerjs/glimmer-web-component.svg?branch=master)](http://travis-ci.org/glimmerjs/glimmer-web-component)

## Installation

Add this package to your project with Yarn:

```
yarn add --dev @glimmer/web-component
```

Or alternatively with npm:

```
npm install --save-dev @glimmer/web-component
```

## Usage

Add this import to your `src/index.ts` or wherever you are instantiating your Glimmer app:

```ts
import initializeCustomElements from '@glimmer/web-component';
```

And then after `app.boot()`:

```ts
initializeCustomElements(app, {
  'button-list': 'ButtonList',
  'x-button': 'Button'
});
```

This will register custom elements for each of the items defined in the hash passed to `initializeCustomElements` and will replace the custom element with your Glimmer component once the custom element connects. For example, if you provide the hash `{ 'foo-bar': 'FooBar' }`, you can then use the custom element `<foo-bar>` anywhere in the DOM and have your `<FooBar>` Glimmer component render in its place.

## Browser Support

Browser support for the `WebComponents` spec is not [not great yet](http://caniuse.com/#feat=custom-elementsv1).  If you want to use `customElements.define` where it is not yet supported natively, you'll need to install the [polyfill](https://github.com/webcomponents/custom-elements).

## License

MIT License.
npm package: @glimmerx/blueprint
Description: Ember CLI blueprint for initializing a new GlimmerX application.
Author: Tom Dale
Latest version: 0.6.8

# @glimmerx/blueprint

[![npm version](https://badge.fury.io/js/%40glimmerx%2Fblueprint.svg)](https://badge.fury.io/js/%40glimmerx%2Fblueprint)

This repository holds the blueprint for generating a new GlimmerX project.

To generate a project using this blueprint:

```bash
npx ember-cli new hello-glimmer --blueprint @glimmerx/blueprint
```
npm package: @glimmerx/eslint-plugin
Description: ESLint Plugin to enable and streamline glimmerx development
Author: Kyle Blomquist
Latest version: 0.6.8

# @glimmerx/eslint-plugin

## Background

[ESLint](https://eslint.org/docs/about) is an open source JavaScript [linting](https://en.wikipedia.org/wiki/Lint_\(software\)) utility.

## Introduction

This project exists to provide ESLint rules that either:
- fix issues between inline templates and the core ESLint rules
- Enable enhanced development experience for GlimmerX component authors/maintainers

## Installation and Usage

```
yarn add -D @glimmerx/eslint-plugin
```

For configuration, ESLint generally uses files named `.eslintrc.json` or `.eslintrc.js`.
The examples in this README will use js syntax, but you can read [the configuration docs for ESLint](https://eslint.org/docs/user-guide/configuring) for information on other formats / methods

To enable the Plugin, you will need to add the `@glimmerx` plugin to your list of plugins:
```js
module.exports = {
  plugins: [
    // ...existing plugins, if any
    '@glimmerx'
  ],
  // ...Other configuration settings
}
```

You will also need to enable any rules in the list of rules present in that same configuration. For example, if you wanted to use the rule `@glimmerx/template-vars`:
```js
module.exports = {
  plugins: [
    // ...existing plugins, if any
    '@glimmerx'
  ],
  // ...Other configuration settings
  rules: {
    '@glimmerx/template-vars': 'error'
  }
}
```

For details on what specific rules do and full configuration options, refer to [The Rules Docs](docs/rules)

## Development

For information on developing ESLint rules, see [the ESLint Rule Development Documentation](https://eslint.org/docs/developer-guide/working-with-rules)

### Testing

Testing is done by mocha and (when possible) uses [ESLint's built-in RuleTester](https://eslint.org/docs/developer-guide/nodejs-api#ruletester)
```
yarn test
```
npm package: @glimmerx/prettier-plugin-component-templates
Description: A prettier formatter for glimmer component templates
Author: Matt Edwards
Latest version: 0.6.8

# @glimmerx/prettier-plugin-component-templates

## Background

[Prettier](https://prettier.io/docs/en/index.html) is an opinionated code formatter. In Prettier `>2.0` there is support for `*.hbs` glimmer files, but does not support the experimental syntaxes that `glimmerx` components are authored in.

## Introduction

This plugin extends the internal printers to add an embedded syntax for glimmer template in an `hbs` TaggedTemplateExpressions.

## Installation and Usage

```bash
yarn add -D @glimmerx/prettier-plugin-component-templates
```

Once added prettier will discover and use the plugin to format any `hbs` tagged template expression.

### Options

In your prettier config options (e.g. `.prettierrc`, `prettier.config.js`, etc.)

`.prettierrc`

```json
{
  "hbsSingleQuote": true
}
```

Defaults to `false` forcing double-quotes for all attributes in an hbs embed. When `true` will rewrite all quotes to single-quotes.

## Development

Generate a test case, add it to the tests file,

Add `PRETTIER_DEBUG=true` to the environment when running the plugin in order to get complete stack traces on errors.

### Debugging

#### Debugging

```
PRETTIER_DEBUG=true node --inspect-brk  node_modules/.bin/prettier --config=./test/fixtures/basic/config.js ./test/fixtures/basic/code.js
```

### Generate a snapshot

```
node node_modules/.bin/prettier --ignore-path --config=./test/fixtures/simple-formatted/config.js ./test/fixtures/simple-formatted/code.js > ./test/fixtures/simple-formatted/output.js
```

### Testing

#### Run all tests

```
yarn test
```

## TODO

- [ ] Add support for `<template>` tag semantics.
npm package: @glimr/loom
Description: Client runtime for Glimr's Loom template engine
Latest version: 1.0.1

# Glimr Loom JS ✨

Client runtime for Glimr's Loom template engine, providing WebSocket management, DOM patching, SPA navigation, and event forwarding. This package is meant to be used alongside the `glimr-org/framework` package and the `glimr-org/glimr` starter repository.

If you'd like to stay updated on Glimr's development, Follow [@migueljarias](https://x.com/migueljarias) on X (that's me) for updates.

## About

> **Note:** This repository contains the client-side runtime for Loom. If you want to build an application using Glimr, visit the main [Glimr repository](https://github.com/glimr-org/glimr).

## Features

- **WebSocket Management** - Persistent connection for server-driven reactivity
- **DOM Patching** - Efficient diffing and patching via morphdom
- **SPA Navigation** - Intercepts link clicks for instant page transitions
- **Event Forwarding** - Captures browser events and sends them to the server

## Installation

```sh
npm install @glimr/loom
```

Then import it in your `app.ts`:

```ts
import "../css/app.css";
import "@glimr/loom";
```

The runtime auto-initializes on page load — no setup required.

## Learn More

- [Glimr](https://github.com/glimr-org/glimr) - Main Glimr repository
- [Glimr Framework](https://github.com/glimr-org/framework) - Core framework

### Built With

- [**morphdom**](https://github.com/patrick-steele-iber/morphdom) - Fast and lightweight DOM diffing/patching

## Contributing

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

## License

Glimr Loom JS is open-sourced software licensed under the [MIT](https://opensource.org/license/MIT) license.
npm package: @glincker/palrun
Description: AI command palette for your terminal - discover and run project commands instantly
Author: GLINR
Latest version: 0.1.0-beta.1

# @glinr/palrun

> AI command palette for your terminal - discover and run project commands instantly

This is the npm wrapper package for [Palrun](https://github.com/GLINCKER/palrun). It downloads the pre-built binary for your platform during installation.

## Installation

```bash
npm install -g @glinr/palrun
```

Or with yarn:

```bash
yarn global add @glinr/palrun
```

Or with pnpm:

```bash
pnpm add -g @glinr/palrun
```

## Usage

After installation, you can run:

```bash
palrun
# or
pal
```

## Features

- Fuzzy search across all your project commands
- Auto-discovers npm scripts, Cargo targets, Make tasks, and more
- AI-powered command generation (Claude + Ollama)
- Runbooks for team workflows
- Works with monorepos (npm, pnpm, yarn, Nx, Turbo)

## Alternative Installation Methods

If npm installation fails, you can install Palrun using:

### Cargo (Rust)

```bash
cargo install palrun
```

### From Source

```bash
git clone https://github.com/GLINCKER/palrun.git
cd palrun
cargo build --release
```

### Direct Download

Download pre-built binaries from the [GitHub Releases](https://github.com/GLINCKER/palrun/releases) page.

## Supported Platforms

- macOS (x64, ARM64)
- Linux (x64, ARM64)
- Windows (x64)

## License

MIT - see [LICENSE](https://github.com/GLINCKER/palrun/blob/main/LICENSE)

## Links

- [GitHub Repository](https://github.com/GLINCKER/palrun)
- [Documentation](https://glinr.com/palrun)
- [Issues](https://github.com/GLINCKER/palrun/issues)
npm package: @glinda93/coinvise
Description: Coinvise SDK to interact with the Coinvise API (beta)
Author: Coinvise
Latest version: 0.3.3

# Coinvise JS SDK

SDK for interacting with the coinvise API (closed beta)

## Documentation

[Docs](https://www.notion.so/coinvise/Coinvise-API-bf23e380567d46748115722f15020354)

## Contributors ✨

<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->

[![All Contributors](https://img.shields.io/badge/all_contributors-2-orange.svg?style=flat-square)](#contributors-)

<!-- ALL-CONTRIBUTORS-BADGE:END -->

Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):

<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore-start -->
<!-- markdownlint-disable -->
<table>
  <tr>
    <td align="center"><a href="https://github.com/mihirgupta0900"><img src="https://avatars.githubusercontent.com/u/37367148?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Mihir Gupta</b></sub></a><br /><a href="https://github.com/coinvise/sdk-js/commits?author=mihirgupta0900" title="Code">💻</a> <a href="https://github.com/coinvise/sdk-js/commits?author=mihirgupta0900" title="Documentation">📖</a> <a href="#infra-mihirgupta0900" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a></td>
    <td align="center"><a href="https://jenilt.com/"><img src="https://avatars.githubusercontent.com/u/22861609?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Jenil Thakker</b></sub></a><br /><a href="#business-jenil04" title="Business development">💼</a></td>
  </tr>
</table>

<!-- markdownlint-restore -->
<!-- prettier-ignore-end -->

<!-- ALL-CONTRIBUTORS-LIST:END -->

This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
npm package: @glinkis/jslib
Description: A modular javascript utility library.
Author: Victor Glindås
Latest version: 2.0.0

# jslib-utils

[![npm](https://img.shields.io/npm/v/jslib-utils.svg)](https://www.npmjs.com/package/jslib-utils)
[![license](https://img.shields.io/npm/l/jslib-utils.svg)](https://www.npmjs.com/package/jslib-utils)
[![Build Status](https://travis-ci.org/Glinkis/jslib.svg?branch=master)](https://travis-ci.org/Glinkis/jslib)
[![Codacy Badge](https://api.codacy.com/project/badge/Grade/e267d9e793eb490e84b232827cbe062b)](https://www.codacy.com/app/Glinkis/jslib?utm_source=github.com&utm_medium=referral&utm_content=Glinkis/jslib&utm_campaign=Badge_Grade)
[![Help Contribute to Open Source](https://www.codetriage.com/glinkis/jslib/badges/users.svg)](https://www.codetriage.com/glinkis/jslib)

A modular javascript utility library.

[Documentation](https://glinkis.github.io/jslib/)

## Installation

```bash
npm install jslib-utils --save
```

## Usage

The library is built to allow for tree shaking (the elimination of unused code).

To access the modules, import through either `jslib-utils/lib`(commonjs modules)
or `jslib-utils/es`(es2015 modules).

There is also a minimized version available through
`jslib-utils/dist/jslib-utils.min` if you prefer that.

### Tree Shaking

Imports the whole library, and doesn't allow for tree shaking.

```js
import * as utils from "jslib-utils/dist/jslib-utils.min";
import * as utils from "jslib-utils/lib";
import * as utils from "jslib-utils/es";
```

Imports only the relevant modules, and thus allows for tree shaking. Keep in
mind that importing a whole module won't strip any unused functions inside of
that particular module.

```js
import { array, math } from "jslib-utils/lib";
import { array, math } from "jslib-utils/es";
```

Imports can have any level of granularity, and so importing only the specific
functions you need will allow for the the greatest amount of code elimination.

```js
import { easing } from "jslib-utils/lib";
import * as easing from "jslib-utils/lib/easing";
import { linear } from "jslib-utils/lib/easing";
```

Please feel free to contribute.
npm package: @glint-solar/mbview
Description: Watch mbtiles in your localhost
Author: Rodolfo Wilhelmy
Latest version: 5.1.2

[![Build Status](https://travis-ci.org/mapbox/mbview.svg?branch=master)](https://travis-ci.org/mapbox/mbview)

# mbview

Watch MBTiles in your localhost

![demo](https://raw.githubusercontent.com/mapbox/mbview/master/demo.gif)

```bash
% npm install
% export MAPBOX_ACCESS_TOKEN='pk.0000.1111' # replace value with your mapbox public access token
% node cli.js --port 9000 ~/roads.mbtiles ~/taco-places.mbtiles
```
You can obtain a mapbox public token by signing up [here](https://www.mapbox.com/signup/).

Global install

```bash
% npm install -g @mapbox/mbview
% mbview
```

Or just try the demo

```bash
% cd examples
% ./try.sh
```

Type `mbview --help` to see the parameters available.

**Awesome stuff**

![awesome 1](https://cloud.githubusercontent.com/assets/58878/15119908/fc49b9b8-15c7-11e6-99b8-8a590df46c37.png)

![awesome 2](https://cloud.githubusercontent.com/assets/58878/15119925/0a974634-15c8-11e6-852b-a7d411cd407f.png)

![awesome 3](https://cloud.githubusercontent.com/assets/58878/15120006/61715756-15c8-11e6-8219-3fb3c8389462.png)
npm package: @glint-ui/react
Description: a React component library
Author: huayemao4g@gmail.com
Latest version: 0.1.1

# Your Package Name

A customized React component library built with TypeScript and Tailwind CSS.

## Installation

```bash
npm install @glint-ui/react
# or
yarn add @glint-ui/react
# or
pnpm add @glint-ui/react
```

## Usage

```tsx
import { BaseButton, BaseCard } from '@glint-ui/react';

function App() {
  return (
    <BaseCard>
      <BaseButton>Click me</BaseButton>
    </BaseCard>
  );
}
```

## Components

This library includes the following components:

- **Base Components**: Button, Card, Avatar, Input, etc.
- **Form Components**: Checkbox, Radio, Select, etc.
- **Layout Components**: Accordion, Tabs, Pagination, etc.

## Requirements

- React >= 18
- Next.js >= 13
- Tailwind CSS

## License

MIT
npm package: @glint/cli
Description: A CLI for performing typechecking on Glimmer templates
Author: Dan Freeman
Latest version: 0.2.1
Deprecated: The `glint` CLI is now built into `@glint/core`

# `@glint/cli`

This package contains a CLI to execute template-aware typechecking on a [glint] project.

[glint]: https://github.com/typed-ember/glint

## Usage

```sh
glint [--watch|-w] [--declaration|-d] [--project path/to/tsconfig.json]
```

## Flags

- `--watch` If passed, `glint` will perform a watched typecheck, re-checking your project as files change.
- `--declaration` If passed, `glint` will emit `.d.ts` files according to the configuration in your `tsconfig.json`
- `--project` Overrides where `glint` will look to find your project's `tsconfig.json`
npm package: @glint/config
Description: Tools to read configuration for @glint packages
Author: Dan Freeman
Latest version: 0.9.7
Deprecated: Now a part of @glint/core

# `@glint/config`

This package is used by various other [Glint] packages to locate any custom configuration.

[glint]: https://github.com/typed-ember/glint

## Config Specification

`@glint/config` searches for your Glint configuration under a `"glint"` key in your project's `tsconfig.json` or `jsconfig.json`.

## Config Options

See the [Configuration guide](https://typed-ember.gitbook.io/glint/configuration) in the Glint docs for further details on configuring Glint.
npm package: @glint/ember-tsc
Description: A CLI for performing typechecking on Glimmer templates
Author: Dan Freeman
Latest version: 1.5.0

# `@glint/ember-tsc`

This package contains core functionality to power template-aware typechecking on a [glint] project. Two binaries are provided:

- `glint-language-server` - the Language Server that the VSCode (and other IDE) extension communicates with
- `ember-tsc` (see below) - a thin wrapper around TypeScript's `tsc` which provides support for .gts/.gjs files

[glint]: https://github.com/typed-ember/glint

## `ember-tsc`

The `ember-tsc` CLI tool is a thin wrapper around `tsc` and hence all documentation / use cases / flags that apply to `tsc` also apply to `ember-tsc`.

Because `ember-tsc` is only used for type-checking purposes (or generating declaration files), and not for producing compiled JS output, the emitting of JS should always be disabled by providing either the `--noEmit` or `--emitDeclarationOnly` flags, depending on your use case.

### Usage

General Usage:

```sh
ember-tsc --noEmit [--build] [--watch|-w] [--declaration|-d] [--emitDeclarationOnly] [--project path/to/tsconfig.json]
```

Type-checking:

```sh
ember-tsc [--build] --noEmit
```

Type-checking in watch mode:

```sh
ember-tsc [--build] --noEmit --watch
```

Build declaration files:

```
ember-tsc --build --declaration --emitDeclarationOnly
```

Build declaration files in watch mode:

```
ember-tsc --build --declaration --emitDeclarationOnly --watch
```

Please refer to `tsc` docs for other use cases and flags.
npm package: @glint/environment-glimmerx
Description: A Glint environment to support GlimmerX projects
Author: Dan Freeman
Latest version: 1.5.2

# `@glint/environment-glimmerx`

This package contains the information necessary for glint to typecheck a [glimmer-experimental](https://github.com/glimmerjs/glimmer-experimental) project.

See [the Glint documentation](https://typed-ember.gitbook.io/glint/using-glint/glimmerx/installation) for more detailed instructions on working with GlimmerX projects in Glint.
npm package: @glint/transform
Description: Transforms Glimmer templates into TypeScript code that approximates their semantics
Author: Dan Freeman
Latest version: 0.9.7
Deprecated: Now a part of @glint/core

# `@glint/transform`

This package contains tools for rewriting Glimmer templates as a TypeScript approximation of their semantics, used by other [glint] packages.

[glint]: https://github.com/typed-ember/glint
npm package: @glint/tsserver-plugin
Description: TypeScript Server Plugin for Glint
Latest version: 2.4.0

# @glint/tsserver-plugin

The TypeScript server plugin that performs type-checking. Uses Volar.

## Setup

### VSCode

install the extension from here: https://marketplace.visualstudio.com/items?itemName=typed-ember.glint2-vscode 

### Open VSX

install the extension from here: https://open-vsx.org/extension/typed-ember/glint2-vscode

### neovim

This plugin is part of [ember.nvim](https://github.com/NullVoxPopuli/ember.nvim), but can be configured manually via similar setup to [here](https://github.com/NullVoxPopuli/ember.nvim/blob/0cec0eb3641e10df0a32e1e81206efaff22f1974/lua/ember/lsp/typescript.lua#L49)
npm package: @glints-dev/glints-aries
Description: Glints ui-kit for frontend
Author: Glints
Latest version: 0.0.12

# glints-aries
Glints-aries UI-kit

[https://github.com/glints-dev/glints-aries](https://github.com/glints-dev/glints-aries)

## installation
```bash
npm install -S @glints-dev/glints-aries
```

## usage

### Button
```javascript
import React from 'react';
import { Button } from '@glints-dev/glints-aries';

const MyComponent = () => {
  return(
    <Button variant="default">Im a button</Button>
  )
}

export default MyComponent;
```

## npm scripts
```bash
npm run storybook
```
then open your browser on port 9001

## development
all components lived on `src` folder. once you done adding component on `src` folder include it on `src/index.js` file
```javascript
export {default as Button} from './Button';
export {default as MyAwesomeComponent} from './MyAwesomeComponent';
export {Uikit as default, UikitConsumer, UikitProvider} from './Provider';
```

## Todos
- [x] better documentation
- [ ] more better documentation
- [ ] refactoring existing component so it can be more flexible and reliable

## Coming soon
- [ ] another awesome component
npm package: @glints/eslint-config
Description: ESLint rules for Glints projects.
Author: Wong Yong Jie
Latest version: 5.0.0

# ESLint Configs for Glints [![npm version](https://badge.fury.io/js/%40glints%2Feslint-config.svg)](https://badge.fury.io/js/%40glints%2Feslint-config)

This repository contains shared rules for ESLint.

It is used across many of our internal and external projects.

# Usage Instructions

To integrate this into your project, install the package:

```
npm install --save-dev @glints/eslint-config  # If using npm
yarn add --dev @glints/eslint-config          # If using Yarn
```

Then add the following to your ESLint configuration:

```js
"extends": [
  "@glints/eslint-config",

  // Rules below are for projects that use React/JSX.
  "@glints/eslint-config/react",
  "@glints/eslint-config/jsx-control-statements"
]
```

For TypeScript support, add the following rules:
```js
"overrides": {
  "files": ["**/*.ts", "**/*.tsx"],
  "extends": ["@glints/eslint-config/typescript"]
}
```

# Contribution Guidelines

**Please do not bump version before your changes have been merged into the master branch. Also, please do not push git tags on this repo for commits that have not been merged to master yet, pushing these tags would cause an un-intended release to the NPM registry. Version bumps are supposed to be a shared global entity.**

Refer to [this link](https://eslint.org/docs/developer-guide/shareable-configs) for documentation about sharable configurations and rules.

Before modifying the rules, please notify the codebase owners because it may impact many downstream projects.

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/hapi-geolocation-plugin
Description: A plugin that attempts to determine the location of the client.
Author: Wong Yong Jie
Latest version: 1.0.0

# geolocation-plugin [![npm version](https://badge.fury.io/js/%40glints%2Fhapi-geolocation-plugin.svg)](https://badge.fury.io/js/%40glints%2Fhapi-geolocation-plugin)

This plugin resolves the client's location using Maxmind's GeoIP databases.

# Usage Instructions

To integrate this into your project, install the package:

```
npm install --save @glints/hapi-geolocation-plugin  # If using npm
yarn add @glints/hapi-geolocation-plugin            # If using Yarn
```

Then register the plugin with hapi:

```js
import { GeolocationPlugin } from '@glints/hapi-geolocation-plugin';

// Register the plugin with the hapi server.
await hapiServer.register({
  plugin: GeolocationPlugin,
  options: {
    // Downloadable at https://dev.maxmind.com/geoip/geoip2/geolite2/
    dbPath: 'GeoLite2-Country.mmdb',
  },
});
```

# Contribution Guidelines

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/hapi-real-ip-plugin
Description: A plugin that attempts to determine the real IP of the client.
Author: Wong Yong Jie
Latest version: 4.0.1

# real-ip-plugin [![npm version](https://badge.fury.io/js/%40glints%2Fhapi-real-ip-plugin.svg)](https://badge.fury.io/js/%40glints%2Fhapi-real-ip-plugin) [![Greenkeeper badge](https://badges.greenkeeper.io/glints-dev/hapi-real-ip-plugin.svg)](https://greenkeeper.io/)

This plugin resolves client's IP address from the `X-Forwarded-For` header if
any downstream proxies are present. The resolved addresses are stored in
`request.plugins.RealIPPlugin.ip`.

# Usage Instructions

To integrate this into your project, install the package:

```
npm install --save @glints/hapi-real-ip-plugin  # If using npm
yarn add @glints/hapi-real-ip-plugin            # If using Yarn
```

Then register the plugin with hapi:

```js
import { RealIPPlugin } from '@glints/hapi-real-ip-plugin';

// Register the plugin with the hapi server.
await hapiServer.register({
  plugin: RealIPPlugin,
  options: {
    numProxies: 1, // Indicates the expected number of downstream proxies.
  },
});
```

# Contribution Guidelines

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/hapi-url-plugin
Description: A plugin that attempts to construct a complete URL object for an incoming request.
Author: Wong Yong Jie
Latest version: 3.0.1

# url-plugin [![npm version](https://badge.fury.io/js/%40glints%2Fhapi-url-plugin.svg)](https://badge.fury.io/js/%40glints%2Fhapi-url-plugin) [![Greenkeeper badge](https://badges.greenkeeper.io/glints-dev/hapi-url-plugin.svg)](https://greenkeeper.io/)

By default, hapi does not have the complete URL information as sent from a
browser. Therefore, `request.url` doesn't provide information such as the
protocol used. This plugin attempts to check other sources such as the
`X-Forwarded-Proto` header to construct a complete URL object.

# Usage Instructions

To integrate this into your project, install the package:

```
npm install --save @glints/hapi-url-plugin  # If using npm
yarn add @glints/hapi-url-plugin            # If using Yarn
```

Then register the plugin with hapi:

```js
import { URLPlugin } from '@glints/hapi-url-plugin';

// Register the plugin with the hapi server.
await hapiServer.register({
  plugin: URLPlugin,
  options: {
    numProxies: 1, // Optional, indicates the number of downstream proxies.
  },
});

// In a request handler:
server.route({
  ...
  handler: (request, h) => {
    // request.plugins.URLPlugin.url is a URL object.
    return request.plugins.URLPlugin.url.pathname;
  },
});
```

# Contribution Guidelines

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/hapi-webpack-dev-server-plugin
Description: A plugin for hapi to expose webpack-dev-server.
Author: Wong Yong Jie
Latest version: 4.0.1

# webpack-dev-server-plugin [![npm version](https://badge.fury.io/js/%40glints%2Fhapi-webpack-dev-server-plugin.svg)](https://badge.fury.io/js/%40glints%2Fhapi-webpack-dev-server-plugin) [![Greenkeeper badge](https://badges.greenkeeper.io/glints-dev/hapi-webpack-dev-server-plugin.svg)](https://greenkeeper.io/)

This allows `webpack-dev-middleware` to be used with hapi.

# Usage Instructions

To integrate this into your project, install the package:

```
npm install --save @glints/hapi-webpack-dev-server-plugin  # If using npm
yarn add @glints/hapi-webpack-dev-server-plugin            # If using Yarn
```

Then register the plugin with hapi:

```js
// Create an instance of the Webpack compiler.
const compiler = Webpack({
  // Compiler options here.
});

// Register the plugin with the hapi server.
await hapiServer.register({
  plugin: WebpackDevServerPlugin,
  options: {
  compiler,
    devMiddlewareOptions: {
      // Define options for webpack-dev-middleware
      publicPath: webpackConfig.output.publicPath,
      stats: {
        modules: false,
      },
    },
  },
});
```

# Contribution Guidelines

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/poppins
Description: Localized Poppins typeface
Author: Francis Goh
Latest version: 1.0.2

# glints-poppins

Localized Poppins typeface.

# Usage Instructions

Install the package:

```
npm install --save @glints/poppins  # If using npm
yarn add @glints/poppins            # If using Yarn
```

To use, simply import the package in your project’s entry file e.g.

`index.js`
```js
import '@glints/poppins';
```

# Localization

These are the current languages we support:
- Latin
- Vietnamese

By default, Poppins (Latin) will be loaded. We use the [`unicode-range` CSS descriptor](https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/unicode-range) to load SVN Poppins (Vietnamese) only when there are Vietnamese characters. This allows the browser to load the smaller Poppins (Latin) font file unless it needs to display Vietnamese characters.

# Contribution Guidelines

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.
npm package: @glints/tslint-rules
Description: Shared rules for the TypeScript Linter, TSLint.
Author: Wong Yong Jie
Latest version: 1.0.6

# TSLint Rules for Glints

This repository contains shared rules for the TypeScript linter by Palantir, TSLint.

It is used across many of our internal and external projects.

# Contribution Guidelines

Refer to [this link](https://palantir.github.io/tslint/2016/03/31/sharable-configurations-rules.html) for documentation about sharable configurations and rules.

Before modifying the rules, please notify the codebase owners because it may impact many downstream projects.

We use [EditorConfig](https://editorconfig.org) to maintain consistent line-ending and indentation rules across all our projects. Ensure that you have the appropriate plugin installed in your preferred editor, or refer to `.editorconfig`.

# About Glints

Glints is an online talent recruitment and career discovery platform headquartered in Singapore. It is a platform for young talent to build up their career readiness through internships and graduate jobs; developing skill sets required in different careers.

**P.S.** We deal with quite a number of interesting engineering problems centered on matching the right talent to employers. Sounds interesting? Send your resume to tech@glints.com.