open-index/open-npm huggingface dataset:
npm package: @joezx/jtgis
Description: 江泰gis组件
Latest version: 2.0.0

# jt-components-pc

## Project setup
```
yarn install
```

### Compiles and hot-reloads for development
```
yarn serve
```

### Compiles and minifies for production
```
yarn build
```

### Lints and fixes files
```
yarn lint
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
npm package: @joffarex/ng-bootstrap-datetime-angular
Description: Angular Bootstrap Date Time Picker
Author: Danilo Meneses
Latest version: 0.1.27

# ng-bootstrap-datetime-angular

# Angular Date Time Picker

[![npm](https://img.shields.io/npm/v/ng-bootstrap-datetime-angular.svg?maxAge=2592000?style=flat-square)](https://www.npmjs.com/package/ng-bootstrap-datetime-angular)
[![npm](https://img.shields.io/npm/dm/ng-bootstrap-datetime-angular.svg)](https://www.npmjs.com/package/ng-bootstrap-datetime-angular)

**This package supports Angular 10**

Description

---

This picker is responsive design, so feel free to try it in your desktops, tablets and mobile devices.

## Dependencies
[@ng-bootstrap/ng-bootstrap ^1.0.0](https://www.npmjs.com/package/@ng-bootstrap/ng-bootstrap)

[moment ^2.24.0](https://www.npmjs.com/package/moment)

[bootstrap ^4.0.0](https://www.npmjs.com/package/bootstrap)

## Live Demo
[https://ng-bootstrap-datetime-angular.stackblitz.io](https://stackblitz.com/edit/ng-bootstrap-datetime-angular)

## How to Use

1.  Install with [npm](https://www.npmjs.com):`npm install ng-bootstrap-datetime-angular --save`

2.  Add NgBootstrapDatetimeAngularModule to your **@NgModule** like example below

    ```typescript
    import { BrowserModule } from "@angular/platform-browser";
    import { NgModule } from "@angular/core";

    import { AppComponent } from "./app.component";
    import { FormsModule, ReactiveFormsModule } from "@angular/forms";
    import { CommonModule } from "@angular/common";

    import { NgBootstrapDatetimeAngularModule } from "ng-bootstrap-datetime-angular";

    @NgModule({
      declarations: [AppComponent],
      imports: [
        BrowserModule,
        FormsModule,
        ReactiveFormsModule,
        NgBootstrapDatetimeAngularModule,
        CommonModule
      ],
      providers: [],
      bootstrap: [AppComponent]
    })
    export class AppModule {}
    ```

3.  Add your input into **form** like example below

    ```html
    <form>
      <div [formGroup]="formGroup">
        <ng-bootstrap-datetime-angular
          inputDatetimeFormat="dd/MM/yyyy hh:mm a"
          formControlName="activeEndDate"
          name="activeEndDate"
        ></ng-bootstrap-datetime-angular>
      </div>
    </form>
    ```

4.  Connect to your __component__

    ```typescript
    import { Component, OnInit } from "@angular/core";
    import { FormGroup, FormControl, Validators } from "@angular/forms";

    @Component({
      selector: "app-root",
      templateUrl: "./app.component.html",
      styleUrls: ["./app.component.scss"]
    })
    export class AppComponent implements OnInit {
      title = "Date";
      formGroup: FormGroup;

      ngOnInit() {
        this.formGroup = new FormGroup({
          activeEndDate: new FormControl(null, {
            validators: [Validators.required]
          })
        });
      }
    }
    ```

License
-------
* License: MIT

Author
-------
**Danilo Meneses Loaisiga**
npm package: @joffotron/relay-testing-utils
Description: Easy to use relay mock and unit testing tool (works with Jest & Enzyme)
Author: Toni Meuschke
Latest version: 1.0.4

# relay-testing-utils
Easy to use relay mock and unit testing tool (works with Jest &amp; Enzyme)



## Install

`npm install relay-testing-utils`


## Getting started

In order to unit test your relay containers you need a tool that provides you mocking & testing functionality.
I recommend to use Jest but you can use any kind of testing library.

#### Mocking Relay with Jest

With Jest you can define manual mocks in a `__mocks__` directory.
Please create `__mocks__/react-relay.js` in your project repository and add the following code.

```javascript
import relayTestingUtils from 'relay-testing-utils'
const relay = jest.genMockFromModule('react-relay');


export default relayTestingUtils.relayMock(relay)

```

#### Test a Relay Container


#### Simple Query

If your container has a fragment like:

```
fragments: {
  benutzer: () => Relay.QL
    fragment on BenutzerType {
      id
      prename
      surname
  }
```

You can test it with the following code:

```javascript
import relayTestingUtils from 'relay-testing-utils'
import { mount } from 'enzyme';
import Example from '../Example';

// relay graph
const fixtures = {
  benutzer: {
    id: "007",
    prename: "James",
    surname: 'Bond'
  }
};

test('Relay testing wrap', () => {
  const wrapper = mount(
    relayTestingUtils.relayWrap(<Example {...fixtures} />)
  );
});

```

### Testing Mutation

You are able to spy a mutation and test the passed props that are expected.

``` javascript
test('Test mutation', () => {
  // use a spy / mock fn
  const spy = jest.fn();
  Relay.Store.mockCommitUpdate(spy)

  const container = mount(
      relayTestingUtils.relayWrap(<Mutation {...fixtures} />)
  );
  // test if the mutation was commited with the expected variables
  expect(spy.mock.calls[0][0].getVariables().text).toBe('abc')
})
```

### Examples

You will find more detail and working examples in the `example` folder.
Run the command `npm test` to execute them.


### API

`.relayMock(relay)` => returns a Relay mock implementation

`.relayWrap(<YourContainer />, [{OPTIONS}])` => wraps your container with relay mock environment and passes `this.props.relay`


## Roadmap

- auto generating fixture data based on schema
npm package: @jofu/calendar
Description: A flexible React library for displaying monthly calendars
Author: LqhResearch
Latest version: 0.0.6

# @jofu/calendar

## Introduction

`@jofu/calendar` is a flexible React library for displaying monthly calendars

![@jofu/calendar](./ui/advanced-calendar-usage.png)

## Installation

Install the package using npm or yarn:

```sh
npm install @jofu/calendar@latest
```

or

```sh
yarn add @jofu/calendar@latest
```

## Usage

Here’s an example of how to use `JofuCalendar` in a React project:

```tsx
import React from 'react';
import JofuCalendar from '@jofu/calendar';
import '@jofu/calendar/style';

const App: React.FC = () => {
    return <JofuCalendar />;
};

export default App;
```

[See more examples](./examples/)
npm package: @joggr/marathon
Description: Standard markdown documentation templates, with a programmatic interface.
Author: Joggr Team
Latest version: 0.3.2

<div>
    <p align="center">
        <img src="/logo.png" align="center" width="240" />
    </p>
    <hr>
    <blockquote align="center">
        "It's a marathon, not a sprint." - <a href="https://en.wikipedia.org/wiki/Matt_Campbell_(American_football_coach)">Coach Campbell</a>
    </blockquote>
</div>

<br>

<p align="center">
  <a href="https://badge.fury.io/js/@joggr%2Fmarathon">
    <img src="https://badge.fury.io/js/@joggr%2Fmarathon.svg" alt="npm version">
  </a>
  <a href="https://github.com/joggrdocs/marathon/actions/workflows/github-code-scanning/codeql">
    <img alt="CodeQL" src="https://github.com/joggrdocs/marathon/actions/workflows/github-code-scanning/codeql/badge.svg">
  </a>
  <a href="https://github.com/joggrdocs/marathon/actions/workflows/npm-publish.yaml">
    <img alt="Publish to npm" src="https://github.com/joggrdocs/marathon/actions/workflows/npm-publish.yaml/badge.svg">
  </a>
  <a href="https://github.com/joggrdocs/marathon/actions/workflows/ci.yaml">
    <img alt="CI" src="https://github.com/joggrdocs/marathon/actions/workflows/ci.yaml/badge.svg">
  </a>
  <br/>
  <a href="https://github.com/standard/semistandard">
    <img alt="JS Semi-standard Style" src="https://img.shields.io/badge/code%20style-semistandard-brightgreen.svg">
  </a>
  <a href="https://github.com/prettier/prettier">
    <img alt="Prettier Style" src="https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square">
  </a>
</p>

## Overview

Library of markdown templates for engineering documentation with a programmatic interface.

# Getting Started

## `npm`

```shell
npm install @joggr/marathon
```

## `yarn`

```shell
yarn add @joggr/marathon
```

## Example

```typescript
import fs from 'node:fs/promises';
import marathon from '@joggr/marathon';

const result = marathon.run('api-basic', {
    title: 'This is a title'
});

fs.writeFile('API.md', result);
```
npm package: @jogit/tmp-react-server-dom-nodeless
Description: React Server DOM bindings for Nodeless runtimes. This package is very unstable, use at your own risk.
Latest version: 19.0.1

# @jogit/tmp-react-server-dom-nodeless

> [!CAUTION]
> This is a temporary solution to run React's Server Components on Nodeless runtimes. It is not production-ready and should not be used in production.

It based on Kent C. Dodds' [tmp-react-server-dom](https://www.npmjs.com/package/@kentcdodds/tmp-react-server-dom-esm) which is a temporary solution to run React Server Components on the server with ESM. Which is based on [React Server Components](https://github.com/facebook/react/blob/c86542b/packages/react-server-dom-esm/package.json), an unpublished version of React Server DOM available in React's main repository.

## Usage

```sh
    deno run -A compile.ts
```


## Description

It uses a `unenv` to remove all node-specific code from the React Server DOM package. It also uses `esbuild` to bundle the React Server DOM package and the React Server Components package into a single file. This results in a single file that can be imported and ran in Deno.

## License

Please consult the orginal packages for their licenses.
The code in this repository is MIT licensed.
npm package: @jogs/cross-env-file
Description: Run scripts that set environment across platforms via JSON file
Author: Marco Jakob
Latest version: 0.0.1

<div align="center">
<h1>cross-env-file</h1>

Run scripts that set environment across platforms via JSON file.

This is a fork of [cross-env](https://github.com/kentcdodds/cross-env) that uses a JSON file to
read the environment variables.

</div>

<hr />

## Installation

This module is distributed via [npm][npm] which is bundled with [node][node] and
should be installed as one of your project's `devDependencies`:

```
npm install --save-dev cross-env-file
```

## Usage

I use this in your npm scripts:

```json
{
  "scripts": {
    "build": "cross-env-file -p ./.my-env.json webpack --config build/webpack.config.js"
  }
}
```

Ultimately, the command that is executed (using [`cross-spawn`][cross-spawn])
is:

```
webpack --config build/webpack.config.js
```

If no path is
specified with `-p` the default name `.env` is used.

This is how a JSON environment file could look like:

```json
{
  "base_url": "https://example.com",
  "aws": {
    "my_secret": "my-nested-secret"
  }
}
```

This will add the following environment variables to `process.env`:

```
base_url=https://example.com
aws_my_secret=my-nested-secret
```

## `cross-env-file` vs `cross-env-file-shell`

The `cross-env-file` module exposes two bins: `cross-env-file` and `cross-env-file-shell`. The
first one executes commands using [`cross-spawn`][cross-spawn], while the
second one uses the `shell` option from Node's `spawn`.

The main use case for `cross-env-file-shell` is when you need an environment
variable to be set across an entire inline shell script, rather than just one
command.

For example, if you want to have the environment variable apply to several
commands in series then you will need to wrap those in quotes and use
`cross-env-file-shell` instead of `cross-env-file`.

## LICENSE

MIT
npm package: @joguel63/shared-modules
Description: Shared modules for the Joguel63 project
Latest version: 1.0.1

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

- Configure the top-level `parserOptions` property like this:

```js
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json', './tsconfig.app.json'],
    tsconfigRootDir: __dirname,
  },
}
```

- Replace `plugin:@typescript-eslint/recommended` to `plugin:@typescript-eslint/recommended-type-checked` or `plugin:@typescript-eslint/strict-type-checked`
- Optionally add `plugin:@typescript-eslint/stylistic-type-checked`
- Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and add `plugin:react/recommended` & `plugin:react/jsx-runtime` to the `extends` list