open-index/open-npm huggingface dataset:
npm package: @msyuan/js-lib-cli
Description: 一个快速创建JavaScript库开发项目的CLI工具
Author: Lao Yuan
Latest version: 1.0.6

# JS Lib CLI 快速创建JS库开发的CLI工具

一个方便快速创建JavaScript库开发项目的CLI工具

## 一、功能

* 支持可持续构建到github。
* 支持eslint和prettier。
* 支持commitlint。
* 支持单元测试，可选择vite和jest。
* 提供issue_template。
* 提供好vscode的配置。
* 使用rollup打包。
* 支持输出多种模块的（CJS、UMD、ESM）规范格式。

## 二、使用者指南

### 1、通过pnpm等下载全局安装

```bash
pnpm i -g @msyuan/js-lib-cli ||  npm i -g @msyuan/js-lib-cli
```

### 2、如何初始化一个JS开发库项目

#### 2.1、运行以下命令来创建一个新项目

mylib为您的项目名

```js
js create mylib
```

#### 2.2、你会被提示选取一个preset

![preset](./public/demo.png)

### 3、自主安装依赖说明

* 如果在提示预选阶段没有选择package manager，创建项目成功后，需执行下面的命令自主安装依赖。
* 如果在提示预选阶段选择了husky，则需先初始化git仓库, 然后再安装依赖。

```js
git init
pnpm install
```

如果在提示预选阶段选择了package manager为pnpm\yarn\npm, 则会自动git init，然后自动安装依赖。

### 4、其他说明

lib文件夹中的入口文件，文件名需修改成自己实际的JS库名, dist也是如此（它们只是一个demo，build后可删除demo文件）。

### 5、可选项帮助命令

```js
js --help
```

## 三、参与贡献

1.  Fork 本仓库
2.  新建 Feat-xxx 分支
3.  提交代码
4.  新建 Pull Request
npm package: @mszgs/day-time
Description: Lightweight library for operations with time in a day
Author: MSZGs
Latest version: 1.1.3

# DayTime

![npm (scoped)](https://img.shields.io/npm/v/@mszgs/day-time?style=flat-square)
![GitHub](https://img.shields.io/github/license/MSZGs/day-time?style=flat-square)
![Code style](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)
![npm](https://img.shields.io/npm/dt/@mszgs/day-time?style=flat-square)

Lightweight library for operations with time in a day in 24hr format.

## Installation

Install via `npm`:

```bash
npm install @mszgs/day-time
```

## License

Distributed under the MIT license. See LICENSE for details.
npm package: @mszgs/timetable
Description: ![npm (scoped)](https://img.shields.io/npm/v/@mszgs/timetable?style=flat-square) ![GitHub](https://img.shields.io/github/license/MSZGs/timetable?style=flat-square) ![Code style](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square
Author: MSZGs
Latest version: 0.2.0

# Timetable
![npm (scoped)](https://img.shields.io/npm/v/@mszgs/timetable?style=flat-square)
![GitHub](https://img.shields.io/github/license/MSZGs/timetable?style=flat-square)
![Code style](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)
![npm](https://img.shields.io/npm/dt/@mszgs/timetable?style=flat-square)

Responsive timetable element.

## Installation

Load from a CDN:

```html
<script src="https://cdn.jsdelivr.net/npm/@mszgs/timetable"></script>
```

Install via `npm`:

```bash
npm install @mszgs/timetable
```

## Usage

```html
<mszgs-timetable>
    <mszgs-timetable-item data-title="Subject 1" data-time-start="10:20" data-time-end="12:00" data-day="MON">...</mszgs-timetable-item>
    <mszgs-timetable-item data-title="Subject 3" data-time-start="14:00" data-time-end="20:00" data-day="WED">...</mszgs-timetable-item>
    <mszgs-timetable-item data-title="Subject 2" data-time-start="10:00" data-time-end="12:00" data-day="TUE">...</mszgs-timetable-item>
    <mszgs-timetable-item data-title="Subject 4" data-time-start="15:00" data-time-end="00:120" data-day="THU">...</mszgs-timetable-item>
    ...
</mszgs-timetable> 
```

```javascript
import { Timetable, TimetableItem } from "@mszgs/timetable";

const timetable = new Timetable();
document.body.appendChild(timetable);

const subject = new TimetableItem({
  day: "MON",
  timeStart: "08:00",
  timeEnd: "10:00",
  title: "subjectTitle",
});

timetable.appendChild(subject);
```

## Customization

### Locals
```html
<link href="https://cdn.jsdelivr.net/npm/@mszgs/timetable/locales/[language].css" rel="stylesheet">
```
Currently supported languages:
* English
* Hungarian
* German


### Style

Custom CSS properties:
* --mszgs-timetable-background
* --mszgs-timetable-border-color
* --mszgs-timetable-color
* --mszgs-timetable-font-family
* --mszgs-timetable-header-background
* --mszgs-timetable-item-border-radius
* --mszgs-timetable-item-primary-color
* --mszgs-timetable-min-width


## License
Distributed under the MIT license. See LICENSE for details.
npm package: @mszu/pixi-ssr-shim
Description: A shim that allows PixiJS to be imported (but not run) in a server-side-rendering context
Author: Mark Szumowski
Latest version: 1.0.2

# @mszu/pixi-ssr-shim

![Screenshot showing SvelteKit app with PixiJS](https://raw.githubusercontent.com/mszu/svelte-kit-pixi-sample/main/docs/screenshot.png "SvelteKit + PixiJS")

## What is this?

A basic shim that stubs out enough browser context (`window`, `document`, etc.)
to allow the [PixiJS library](https://pixijs.com/) to be imported in Node without
errors.

**Note that this does not let you USE Pixi from Node (e.g. to render images on the
server), just to import it.**

## Why would I want this?

You're trying to use PixiJS with a framework like [SvelteKit](https://kit.svelte.dev/)
that does server-side rendering, but you're getting errors like
`ReferenceError: self is not defined` during the build or starting the preview server.

## How do I use this?

> See [https://github.com/mszu/svelte-kit-pixi-sample](https://github.com/mszu/svelte-kit-pixi-sample) for a complete example.

1. Add this library as a dependency (`npm i @mszu/pixi-ssr-shim`)
2. Import it before your first Pixi import

```javascript
// Sample SvelteKit script block
//
<script>
  import '@mszu/pixi-ssr-shim'; // <----------------- IMPORTANT
  import { Application, Sprite, Texture } from 'pixi.js';
  import { onMount } from 'svelte';
  
  let app;
  
  onMount(async () => {
    app = new Application({
      width: window.innerWidth,
      height: window.innerHeight,
      resolution: 1,
      backgroundColor: 0x1099bb,
    });

    document.body.appendChild(app.view);

    const sprite = new Sprite(Texture.WHITE);
    sprite.tint = 0xff0000;
    sprite.width = sprite.height = 100;
    sprite.x = sprite.y = 100;

    app.stage.addChild(sprite);
  });
</script>
```

## Important Notes

This is kind of a hacky work-around since it depends on the framework (like SvelteKit)
generating output code which imports the shim before `pixi.js` or any of the `@pixi/...`
modules. Putting it before the Pixi imports in your own code is important, but even then
the SvelteKit/Vite/rollup/esbuild configuration might decide to hoist things around, or
inline them -- it's a bit of a black box.

For SvelteKit specifically:
* Make sure not to call or instantiate anything from Pixi outside of an `onMount(...)` handler.
* Don't import this shim (or the Pixi modules) in a `<script context="module">` but then use
Pixi in a separate `<script>` tag -- this reliably outputs imports in the wrong order.
* To debug, look at the top of the file `.svelte-kit/output/server/app.js` after running
`svelte-kit build`. The imports are near the top -- make sure the shim comes before anything
Pixi.