open-index/open-npm huggingface dataset:
npm package: @sampettersson/reactxp
Description: Cross-platform abstraction layer for writing React-based applications a single time that work identically across web, React Native, and Electron distribution
Author: ReactXP Team
Latest version: 0.42.0-rc.9

# ReactXP
ReactXP is a library for cross-platform app development using React and React Native.  

## Why ReactXP
With React and React Native, your web app can share most its logic with your iOS and Android apps, but the view layer needs to be implemented separately for each platform. We have taken this a step further and developed a thin cross-platform layer we call ReactXP. If you write your app to this abstraction, you can share your view definitions, styles and animations across multiple target platforms. Of course, you can still provide platform-specific UI variants, but this can be done selectively where desired. 

## Getting Started
The [samples](/samples) directory contains a minimal “Hello World” app that demonstrates some basic ReactXP functionality. You can use this as a starting point. Just follow the build instructions in the README file.

Nader Dabit has created a helpful [video tutorial](https://medium.com/@dabit3/reactxp-first-look-d3dd1d08febd) that walks you through the steps to build the sample app.

You can read more about ReactXP and its APIs from the [ReactXP official Documentation](https://microsoft.github.io/reactxp/docs/getting-started.html).

### Prerequisites
* [Node.Js](https://nodejs.org/)
* [React Native](https://facebook.github.io/react-native/)

## Contributing

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 

You must sign a Contribution License Agreement (CLA) before your PR will be merged. This a one-time requirement for Microsoft projects in GitHub. You can read more about [Contribution License Agreements (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) on Wikipedia. You can sign the Microsoft Contribution License Agreement by visiting https://cla.microsoft.com/. Use your GitHub account to login.

## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
npm package: @sample-bilt-monorepo/console-snake
Description: A CLI that ???
Latest version: 1.0.11

# create

A CLI that ???

## Installation

```sh
npm install --global @sample-bilt-monorepo/templatemplate
```

The above installs a command with the name `console-snake`.

## Basic use

???

## CLI Parameters

`console-snake ???`

- `???`: ???

## Contributing

See the documentation on contributing code to packages in this monorepo
[here](../../CONTRIBUTING.md).

### License

MIT
npm package: @sample-bilt-monorepo/math-utils
Description: A library that ???.
Author: Gil Tayar
Latest version: 1.0.13

# math-utils

A library that ???.

This library is JSM-only (does not support `require`-ing it).

## Installation

```sh
npm install @sample-bilt-monorepo/math-utils
```

## Basic use

???

Example:

```js
import {} from '@sample-bilt-monorepo/math-utils'
???
```

## API

### `???(???)`

???

Example:

```js
import {} from '@sample-bilt-monorepo/math-utils'
???
```

## Contributing

See the documentation on contributing code to packages in this monorepo
[here](../../CONTRIBUTING.md).

### License

MIT
npm package: @sample-bilt-monorepo/promise-utils
Description: A library that ???.
Author: Gil Tayar
Latest version: 1.0.2

# promise-utils

A library that ???.

This library is JSM-only (does not support `require`-ing it).

## Installation

```sh
npm install @sample-bilt-monorepo/promise-utils
```

## Basic use

???

Example:

```js
import {} from '@sample-bilt-monorepo/promise-utils'
???
```

## API

### `???(???)`

???

Example:

```js
import {} from '@sample-bilt-monorepo/promise-utils'
???
```

## Contributing

See the documentation on contributing code to packages in this monorepo
[here](../../CONTRIBUTING.md).

### License

MIT
npm package: @sample-bilt-monorepo/snake
Description: A library that ???.
Author: Gil Tayar
Latest version: 1.0.22

# snake

A library that ???.

This library is JSM-only (does not support `require`-ing it).

## Installation

```sh
npm install @sample-bilt-monorepo/snake
```

## Basic use

???

Example:

```js
import {} from '@sample-bilt-monorepo/snake'
???
```

## API

### `???(???)`

???

Example:

```js
import {} from '@sample-bilt-monorepo/snake'
???
```

## Contributing

See the documentation on contributing code to packages in this monorepo
[here](../../CONTRIBUTING.md).

### License

MIT
npm package: @sample-packages/semantic-release-sample
Description: - VCS Root:   - Branch specification: `EMPTY` - VCS Settings:   - Allow builds in the default branch: `FALSE` - Build Steps:   - Command Line:
Author: Fernando Espinosa
Latest version: 1.1.1

# Build Configuration

- VCS Root:
  - Branch specification: `EMPTY`
- VCS Settings:
  - Allow builds in the default branch: `FALSE`
- Build Steps:
  - Command Line:
  
    ```
    #!/bin/bash

    GIT_HASH=%build.vcs.number%
    GIT_HASH_SHORT=${GIT_HASH:0:7}
    BUILD_COUNTER=%build.counter%

    echo "##teamcity[buildNumber '0.0.0-$GIT_HASH_SHORT.$BUILD_COUNTER']"

    exit 0
    ```

- VCS Trigger:
  - Branch filter: `EMPTY`

Blah...
npm package: @sample-stack/client-core
Description: Sample core for higher packages to depend on
Author: CDMBase LLC
Latest version: 0.0.37-3

# Client Core Package
Helper methods and interfaces that can be used by the client part of the packages 

What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
    This package can be installable in front-end webserver

What's not included
---
    It does not have any client UI components such as React
    It does have configured Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
npm package: @sample-stack/client-react
Description: browser plugin for git
Author: CDMBase LLC
Latest version: 0.0.39-alpha.63

# React Package
React components and containers

What does it include:
---
    1. exported react pure components
    2. exported react containers
    3. Typescript 2.0.0 => ES6
    4. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported components and containers
        index.spec.ts            - Tests file for main
        components               - All pure components which don't depend on backend data or external state such as redux
            index.ts             - References all the exported components
        containers               - Components with data to render. Tightly coupled with redux. 
            index.ts             - References all the exported containers
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library


Tutorials:
---
[react-jest-enzymes test](https://www.youtube.com/watch?v=bMmntkVM4wQ)

[testing react with enzyme tutorial](http://codeheaven.io/testing-react-components-with-enzyme/)

[react-redux-typescript-guide](https://github.com/piotrwitek/react-redux-typescript-guide)

Performance:
---
[Redux FAQ: Connecting multiple components](http://redux.js.org/docs/FAQ.html#react-multiple-components)

[React/Redux Links: Performance articles](https://github.com/markerikson/react-redux-links/blob/master/react-performance.md)

[React/Redux: Component re-rendering too often?](http://redux.js.org/docs/faq/ReactRedux.html#react-rendering-too-often)
npm package: @sample-stack/client-redux
Description: GraphQL for sample
Author: CDMBase LLC
Latest version: 0.0.37-3

# Redux Package
Redux npm package includes actions, action-types and reducers

  1. [TypeScript and Redux: getting started][article-1]
  2. [TypeScript and Redux: async actions][article-3]
  3. [TypeScript and Redux: unit testing with Jest][article-4]
  4. [Integrating TypeScript and redux-thunk][article-5]


What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver to use the reducers and actions.

The goal is to make a isolated and reusable module that is self-contained. In order to avoid name conflicts, following rules need to be abide.
1. MUST export a function call reducer()
2. MUST export its action creators as functions
3. MUST have action types in the form `@npm-module-or-app/ACTION_TYPE` eg. `@@sample-stack/INCREMENT_COUNTER`
4. MUST have reducer in the form `npm-module-or-app/reducer_name` eg. `@sample-stack/counter`

What's not included
---
- It does not have any client UI components such as React
- It does not configure Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
                 

[article-1]: https://rjzaworski.com/2016/08/getting-started-with-redux-and-typescript
[article-2]: https://rjzaworski.com/2016/08/typescript-redux-and-react
[article-3]: https://rjzaworski.com/2016/09/typescript-redux-async-actions
[article-4]: https://rjzaworski.com/2016/12/testing-typescript-with-jest
[article-5]: https://rjzaworski.com/2017/01/typescript-redux-thunk
npm package: @sample-stack/client-state
Description: GraphQL for sample
Author: CDMBase LLC
Latest version: 0.0.39-alpha.63

# Client State Package

All client(cache) state management will be done in this package. It not includes `Redux`,`Apollo Client`, `Redux-Epics` or anything that is used for managing the state.

Redux npm package includes actions, action-types and reducers

  1. [TypeScript and Redux: getting started][article-1]
  2. [TypeScript and Redux: async actions][article-3]
  3. [TypeScript and Redux: unit testing with Jest][article-4]
  4. [Integrating TypeScript and redux-thunk][article-5]


What does it include:
---
    1. exported reducers
    2. exported actions
    3. exported graphql queries
    4. Typescript 2.0.0 => ES6
    5. unit testing with jest

Purpose:
---
This package can be installable in front-end webserver to use the reducers and actions.

The goal is to make a isolated and reusable module that is self-contained. In order to avoid name conflicts, following rules need to be abide.
1. MUST export a function call reducer()
2. MUST export its action creators as functions
3. MUST have action types in the form `@npm-module-or-app/ACTION_TYPE` eg. `@@sample-stack/INCREMENT_COUNTER`
4. MUST have reducer in the form `npm-module-or-app/reducer_name` eg. `@sample-stack/counter`

What's not included
---
- It does not have any client UI components such as React
- It does not configure Redux Store

Useful commands:
---
    npm run build       - build the library files
    npm run test        - run tests once
    npm run test:watch  - run tests in watchmode (Useful for development)
    
Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported reducers and actions
        index.spec.ts            - Tests file for main
        actions                  - Contains Actions to transform the state tree
            index.ts             - References all the exported actions
        reducers                 - Contains reducers, pure function with (state, action) => state signature. 
            index.ts             - References all the exported reducers.
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library
                 

[article-1]: https://rjzaworski.com/2016/08/getting-started-with-redux-and-typescript
[article-2]: https://rjzaworski.com/2016/08/typescript-redux-and-react
[article-3]: https://rjzaworski.com/2016/09/typescript-redux-async-actions
[article-4]: https://rjzaworski.com/2016/12/testing-typescript-with-jest
[article-5]: https://rjzaworski.com/2017/01/typescript-redux-thunk
npm package: @sample-stack/graphql-schema
Description: Sample Schema Module
Author: CDMBase LLC
Latest version: 0.0.37-3

# @sample-stack/graphql-schema
This package is intended to be used with [Apollo Server](http://docs.apollostack.com/apollo-server/tools.html) to provide an easy way to setup a GraphQL server and connect it to your database. Note that Apollo Server is not a depenedency of this package. 

Usage
---

Sample Schema exports four things: **database**, **resolvers**, **subscriptions** and **typeDefs**.


*resolvers*
Resolvers are functions that tell the server how to find and return the data for each field in a GraphQL query. The resolving functions simply call your Database Connectors by passing in parameters and return the Connectors result (usually a Promise).

After creating your Database and Connectors from Database, you can call the resolvers function by passing in the Connectors and your public application settings (since settings are stored in the application state). Building on the previous examples:

*typeDefs* is a GraphQL Schema based on the queries provided to it from database. With the schema, you can do things like Find Posts by post_type, get the Postmeta of a Post by the post_id, and so on.

*subscriptions* 
GraphQL subscriptions allow developers to introduce new levels of interactivity to their apps with near-realtime updates. You can keep your app updated to the latest changes (that you subscribe to) between different users:

*database*
The first part of Sample Schema is **database**. This class provides an easy connection to your database using some connection settings, explained below.


Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported components and containers
        index.spec.ts            - Tests file for main
        modules                  - Fractal route for server-side application module splitting (schema definition, resolvers, subscription filters, database connectors )
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library


Setup
---
`modules` directory consists of the sub directories based on the criteria for module splitting. Each sub-directory may have schema definition, resolvers, subscriptions, database

Schema definition files should have suffix as `.graphql` or `.graphqls`. Resolvers file should be named as `resolvers.ts` and subscriptions filter file as `subscriptions.ts`.

All the files under modules are automatically bundled when you run `npm run build`, so the above naming convention should be followed.

## Reference:
https://github.com/ramsaylanier/WordExpressSchema
npm package: @sample-stack/hemera-counter
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.18

# hemera-counter

Your plugin description

# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const plugin = require('hemera-counter')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'counter',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @sample-stack/hemera-plugin
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.39-alpha.31

# hemera-plugin

Your plugin description

# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const plugin = require('hemera-plugin')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'counter',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @sample-stack/microservice-hemera-plugin
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.18

# hemera-container-manager

Your plugin description

# Requirements

Make sure to set following environment properties

```
    process.env.CLOUDFLARE_EMAIL,
    process.env.CLOUDFLARE_KEY,
    process.env.CLOUDFLARE_ZONE_ID,
```
# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const Plugin = require('hemera-container-manager')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(Plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'container-manager',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @sample-stack/microservice-nats
Description: This is Container Configuration Service hemera plugin
Latest version: 0.0.39-alpha.31

# hemera-container-manager

Your plugin description

# Requirements

Make sure to set following environment properties

```
    process.env.CLOUDFLARE_EMAIL,
    process.env.CLOUDFLARE_KEY,
    process.env.CLOUDFLARE_ZONE_ID,
```
# Prerequisites

[Install and run NATS Server](http://nats.io/documentation/tutorials/gnatsd-install/)

# Example

```js
'use strict'

const Hemera = require('nats-hemera')
const Plugin = require('hemera-container-manager')
const nats = require('nats').connect()

const hemera = new Hemera(nats, {
  logLevel: 'info'
})

hemera.use(Plugin)

hemera.ready(() => {
  hemera.act({
    topic: 'container-manager',
    cmd: 'add',
    a: 1,
    b: 2
  }, function (err, resp) {
    this.log.info(resp, 'Result')
  })
})

```

# Test

```
npm run test
```

# Code coverage

```
npm run coverage
```

# Linting

```
npm run lint
```
npm package: @sample-stack/schema
Description: Sample Schema Module
Author: CDMBase LLC
Latest version: 0.0.1

# @sample-stack/schema
This package is intended to be used with [Apollo Server](http://docs.apollostack.com/apollo-server/tools.html) to provide an easy way to setup a GraphQL server and connect it to your database. Note that Apollo Server is not a depenedency of this package. 

Usage
---

Sample Schema exports four things: **database**, **resolvers**, **subscriptions** and **typeDefs**.


*resolvers*
Resolvers are functions that tell the server how to find and return the data for each field in a GraphQL query. The resolving functions simply call your Database Connectors by passing in parameters and return the Connectors result (usually a Promise).

After creating your Database and Connectors from Database, you can call the resolvers function by passing in the Connectors and your public application settings (since settings are stored in the application state). Building on the previous examples:

*typeDefs* is a GraphQL Schema based on the queries provided to it from database. With the schema, you can do things like Find Posts by post_type, get the Postmeta of a Post by the post_id, and so on.

*subscriptions* 
GraphQL subscriptions allow developers to introduce new levels of interactivity to their apps with near-realtime updates. You can keep your app updated to the latest changes (that you subscribe to) between different users:

*database*
The first part of Sample Schema is **database**. This class provides an easy connection to your database using some connection settings, explained below.


Files explained:
---
     src                         - directory is used for typescript code that is part of the project
        index.ts                 - Index file of the package. Consists of exported components and containers
        index.spec.ts            - Tests file for main
        modules                  - Fractal route for server-side application module splitting (schema definition, resolvers, subscription filters, database connectors )
     package.json                - file is used to describe the library and packages that are required added under peer-dependencies section
     tsconfig.json               - configuration file for the library compilation
     webpack.config.js           - configuration file of the compilation automation process for the library


Setup
---
`modules` directory consists of the sub directories based on the criteria for module splitting. Each sub-directory may have schema definition, resolvers, subscriptions, database

Schema definition files should have suffix as `.graphql` or `.graphqls`. Resolvers file should be named as `resolvers.ts` and subscriptions filter file as `subscriptions.ts`.

All the files under modules are automatically bundled when you run `npm run build`, so the above naming convention should be followed.

## Reference:
https://github.com/ramsaylanier/WordExpressSchema
npm package: @sampled-ui/base
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Latest version: 0.0.79

# 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:

```js
export default tseslint.config({
  extends: [
    // Remove ...tseslint.configs.recommended and replace with this
    ...tseslint.configs.recommendedTypeChecked,
    // Alternatively, use this for stricter rules
    ...tseslint.configs.strictTypeChecked,
    // Optionally, add this for stylistic rules
    ...tseslint.configs.stylisticTypeChecked,
  ],
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})
```

You can also install [eslint-plugin-react-x](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-x) and [eslint-plugin-react-dom](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-dom) for React-specific lint rules:

```js
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'

export default tseslint.config({
  plugins: {
    // Add the react-x and react-dom plugins
    'react-x': reactX,
    'react-dom': reactDom,
  },
  rules: {
    // other rules...
    // Enable its recommended typescript rules
    ...reactX.configs['recommended-typescript'].rules,
    ...reactDom.configs.recommended.rules,
  },
})
```
npm package: @samplekit/preprocess-katex
Description: Svelte preprocessor for TeX using KaTeX.
Author: Tim Cohen
Latest version: 2.0.1

# Svelte KaTeX Preprocessor

<img alt="preprocess-katex logo" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/packages/preprocess-katex-vscode/static/sk-katex.png" width="128" />

## What is `preprocess-katex`?

`preprocess-katex` is a preprocessor for Svelte which allows you to write math (via KaTeX) directly in Svelte templates without disrupting other tools like svelte-check, Prettier, ESLint, TypeScript, etc.

This package has a corresponding [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-katex) to provide syntax highlighting.

## Member of the [@samplekit](https://github.com/timothycohen/samplekit) Preprocessor Family.

<img alt="preprocessor family example" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/sites/preprocessor-docs/static/overview-photo-1420w.webp" width="768" />

## Links

- [Docs](https://preprocessors.samplekit.dev/docs/math/)
- [NPM Package](https://www.npmjs.com/package/@samplekit/preprocess-katex)
- [NPM Package Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-katex)
- [Companion VSCode Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-katex)
- [Companion Extension Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-katex-vscode)
npm package: @samplekit/preprocess-markdown
Description: Svelte preprocessor for Markdown using Marked.
Author: Tim Cohen
Latest version: 2.0.0

# Svelte Markdown Preprocessor

<img alt="preprocess-markdown logo" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/packages/preprocess-markdown-vscode/static/sk-md.png" width="128" />

## What is `preprocess-markdown`?

`preprocess-markdown` is a preprocessor for Svelte which allows you to write Markdown (via Marked) directly in Svelte templates without disrupting other tools like svelte-check, Prettier, ESLint, TypeScript, etc.

This package has a corresponding [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-markdown) to provide syntax highlighting.

## Member of the [@samplekit](https://github.com/timothycohen/samplekit) Preprocessor Family.

<img alt="preprocessor family example" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/sites/preprocessor-docs/static/overview-photo-1420w.webp" width="768" />

## Links

- [Docs](https://preprocessors.samplekit.dev/docs/markdown/)
- [NPM Package](https://www.npmjs.com/package/@samplekit/preprocess-markdown)
- [NPM Package Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-markdown)
- [Companion VSCode Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-markdown)
- [Companion Extension Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-markdown-vscode)
npm package: @samplekit/preprocess-shiki
Description: Svelte preprocessor for code highlighting using Shiki.
Author: Tim Cohen
Latest version: 3.0.0

# Svelte Shiki Preprocessor

<img alt="preprocess-shiki logo" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/packages/preprocess-shiki-vscode/static/sk-shiki.png" width="128" />

## What is `preprocess-shiki`?

`preprocess-shiki` is a preprocessor for Svelte which allows you to write decorated code blocks (via Shiki) directly in Svelte templates without disrupting other tools like svelte-check, Prettier, ESLint, TypeScript, etc.

This package has a corresponding [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-shiki) to provide syntax highlighting.

## Member of the [@samplekit](https://github.com/timothycohen/samplekit) Preprocessor Family.

<img alt="preprocessor family example" src="https://raw.githubusercontent.com/timothycohen/samplekit/main/sites/preprocessor-docs/static/overview-photo-1420w.webp" width="768" />

## Links

- [Docs](https://preprocessors.samplekit.dev/docs/code-decoration/)
- [NPM Package](https://www.npmjs.com/package/@samplekit/preprocess-shiki)
- [NPM Package Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-shiki)
- [Companion VSCode Extension](https://marketplace.visualstudio.com/items?itemName=samplekit.svelte-pp-shiki)
- [Companion Extension Source](https://github.com/timothycohen/samplekit/tree/main/packages/preprocess-shiki-vscode)