open-index/open-npm huggingface dataset:
npm package: @mark-magic/core
Description: ## Introduction
Latest version: 0.22.0

# mark-magic

## Introduction

A markdown-based data connection and conversion tool to solve data conversion between different tools and coordination between some common tools.

Some use cases

1. Publish some notes online, for example, generate content required by hexo blog from joplin note tool and publish it online
2. Publish a novel online, for example, generate a novel website from local markdown files and publish it
3. Package a novel into an epub file, for example, package "Flying to the Stars" into an epub file for offline reading after downloading

Some use cases from the community

1. joplin => hugo generating a blog
2. joplin => jekyll generating a blog
3. There may be others...

## Why not use existing tools

We have now used many tools to handle different tasks, but they are all based on markdown, such as

- Use joplin to record notes
- Use hexo to write a blog
- Use vitepress to generate documentation websites
- Use docusaurus to generate SEO-friendly novel websites
- Use pandoc to generate epub

What really makes us feel painful is that when using docusaurus, each novel requires a lot of configuration, which is very annoying. So we hope to have better tools that can be used out of the box.

## Getting Started

For more information, please read the [documentation](https://mark-magic.rxliuli.com/en/)
npm package: @mark-magic/epub
Description: A library for generating epub files, providing low-level API to generate epub files. If you need to generate epub from markdown, please use [@mark-magic/plugin-epub](https://mark-magic.rxliuli.com/en/plugin/plugin-epub.html).
Latest version: 0.4.0

# @mark-magic/epub

A library for generating epub files, providing low-level API to generate epub files. If you need to generate epub from markdown, please use [@mark-magic/plugin-epub](https://mark-magic.rxliuli.com/en/plugin/plugin-epub.html).

> For standards and template files, refer to <https://github.com/IDPF/epub3-samples>.
npm package: @mark-npm/schema
Description: A blank schematics.
Author: Mark R.
Latest version: 0.0.41

# AgSchematics

[![npm (scoped)](https://img.shields.io/npm/v/@agnpm/schema.svg?color=green)](https://www.npmjs.com/package/@agnpm/schema)

Custom schematics implementation.

# How to use

#### 📁️ Add to project

```bash
npm install @mark-npm/schema --save-dev
yarn add @mark-npm/schema --dev
```

#### 📁 Generate component

```bash
ng generate @mark-npm/schema:{SCHEMA_NAME}
ng g @mark-npm/schema:{SCHEMA_NAME}
```

👍 Currenty supported `{SCHEMA_NAME}`

-   ✔️ ag-page
-   ✔️ ag-sifrant
-   ❌ ag-modal

When generating schemas, all standard flags are available. To see all flags use following command

```bash
ng g c --help
```

# Development

## Basics

#### 📁 Clone repository

```bash
git clone https://github.com/arupnik/ag-schematics.git
```

#### 📁 Install dependencies

```bash
npm install
yarn install
```

#### 📁 Create new schema

```bash
schematics blank {name}
```

New entry will be added to `collection.json` file.

#### 📁 Build

```bash
npm run build
```

#### 🌐 Publish package

```bash
npm login (enter npmjs.org credentials)
np
```

## Schematics debugging

In VSCode, open launch.json file and add next entry

```json
{
	"type": "node",
	"request": "launch",
	"name": "Debug schematic",
	"program": "${workspaceFolder}/node_modules/@angular-devkit/schematics-cli/bin/schematics.js",
	"args": [
		".:ag-page",
		"--name=test",
		"--module=common.module.ts",
		"--customPath=src/app/blabl"
	],
	"outFiles": []
}
```
npm package: @mark-small/eslint-config-ms
Description: - [Node Project Config](#node-project-config)   - [Overview](#overview)   - [Usage](#usage)
Author: Mark Small
Latest version: 1.0.0

# Node Project Config

- [Node Project Config](#node-project-config)
  - [Overview](#overview)
  - [Usage](#usage)

## Overview

The project is an NPM project to manage my preferred ESLint and Prettier configuation.
For more info, see the `README.md` files in each package.

## Usage

To use this library in your application's ESLint config file `eslint.config.js`, then do:

```javascript
  // eslint.config.js
  import myconfig from "eslint-config-ms";

  export default [
    ...myconfig,
  ]
```
npm package: @mark-wiemer/luanti-api
Description: Luanti API TypeScript definitions for TypeScriptToLua
Author: Mark Wiemer
Latest version: 0.1.0

# Luanti API

Type definitions for using the Luanti ([formerly Minetest](https://blog.luanti.org/2024/10/13/Introducing-Our-New-Name/)) API via TypeScriptToLua

## Usage

Install dev dependency in your TypeScript project:

```sh
npm i @mark-wiemer/luanti-api --save-dev
```

And use:

```ts
import type {} from "@mark-wiemer/luanti-api";
```

The module declares the Luanti global the same way you'd use it in Lua

You can also utilize the types it provides in your own code by importing them:

```ts
import type { LtVec3 } from "@mark-wiemer/luanti-api";

let myVec: LtVec3 = { x: 0, y: 0, z: 0 };
```

`core` is the only supported namespace alias, `minetest` will not work:

```ts
core.register_on_joinplayer((player) => {
  const playername = player.get_player_name();

  core.chat_send_player(playername, "Welcome!");
});
```

Users of Luanti's Lua api will notice a lack of `:` in TypeScript

Lua uses `obj:method` and `obj.func` to differentiate with `obj` is passed as `self` as the first argument

For instance:

```lua
local obj = {
  method = function (self)
    --"self" refers to obj, similar to "this" in TypeScript
  end

  func = function ()
    --no self variable here
  end
};

obj.method() -- self will be nil
obj:method() -- self will be obj

obj.func() -- self will be nil
obj:func() -- self will still be nil because its not declared in function args
```

In TypeScript this is handled by providing a `this` definition:

```ts
interface LuantiGlobal {
  register_on_joinplayer (this: void, cb: LtPlayerJoinCallback): void;
}
declare global core: LuantiGlobal;
```

Because

```ts
this: void
```

TypeScript calls to `core.register_on_joinplayer()` will properly output:
`core.register_on_joinplayer()` in lua

Without providing `this: void`, this would generate:
`core:register_on_joinplayer()` as TypeScriptToLua assumes we want to provide a `self` reference as first argument

On the flip-side:

```lua
function handle_player_join (player) --player is ObjRef
  player:get_player_name() -- passes player as first arg to get_player_name code
end

core.register_on_joinplayer ( handle_player_join )
```

In TypeScript definitions:

```ts
interface ObjRef {
  //implicit this: ObjRef
  get_player_name(): string;
  //same as
  get_player_name(this: ObjRef): string;
}
```

Which both properly output:

```lua
player:get_player_name()
```

## Acknowledgements

This project is a fork of [@repcomm/mt-api](https://github.com/RepComm/mt-api) from 2023.
npm package: @mark.anthony987654321/calculator-mcp
Description: A Model Context Protocol server for calculator operations
Latest version: 1.0.19

# Calculator MCP Server

A Model Context Protocol (MCP) server that provides calculator operations (add, subtract, multiply, divide).

## Installation

### Via npx (recommended)

```bash
npx calculator-mcp
```

### Local Installation

```bash
npm install
npm start
```

## Available Tools

- **add**: Add two numbers together
- **subtract**: Subtract the second number from the first number
- **multiply**: Multiply two numbers together
- **divide**: Divide the first number by the second number

## Usage

This MCP server is designed to be used with MCP-compatible clients. Configure your MCP client to use this server.

### Example Configuration

For use with Claude Desktop or other MCP clients, add to your MCP configuration:

```json
{
  "mcpServers": {
    "calculator": {
      "command": "npx",
      "args": ["calculator-mcp"]
    }
  }
}
```

## Development

```bash
# Install dependencies
npm install

# Run the server
npm start
```

## License

MIT