open-index/open-npm huggingface dataset:
npm package: @tamperan/zerocms
Description: JS client library for the zeroCMS headless content management platform
Author: Tamperan
Latest version: 0.0.3

# zerocms

zeroCMS is a headless/decoupled CMS focused on fast and easy editing, and straightforward integration into
your development processes. Find out more at https://zerocms.dev

This library wraps the content serving API for easier consumption in Javascript-based apps and web sites.
For documentation on what all the configuration options and doc fields mean see the online docs at
https://zerocms.dev/integrations

If you use React or Vue, try one of the framework-specific libraries for better integration with your
UI framework.

Note: This library is written in Typescript, and Typescript bindings are included.

## Getting started

### Install

First, install the package with npm or yarn:

```shell
npm i @tamperan/zerocms
```

### The zeroCMS object

To retrieve content, you'll need a `zeroCMS` object.  You can have many of these if you need to pull from
multiple repos, but in most cases you'll just need one.

Before you start, you'll need a repo in zeroCMS and you'll need to know its 'slug' - which you will have 
chosen when creating the Repo and is displayed in the Deploy section in the UI.

```javascript
import {ZeroCMS, create} from "@tamperan/zerocms";

const options = {
    dev: false, // set to true in dev mode for console log output when content is retrieved
    region: 'us',
    repo: 'my_repo_slug',
    //target: '_',  - set this if you approve/publish to a specific Target for your UI
    locale: 'en', // fetch content in this locale
}

const zerocms = create(options);
```

### Retrieving content

Content is retrieved asynchronously, so the `get()` method returns a `Promise`.

If your repo has a doc type with slug `pages` and a doc with slug `about-us` then the following can be used
to retrieve the document:

```javascript
zerocms.get('pages', 'about-us').then(res => {
    // the result - res - will be a Doc object
})
```

Of course you should also `catch()` as well, in case of connectivity errors or accidentally providing
non-existent doc slugs.


### Displaying content

Once you have retrieved a `Doc` object, you can interrogate it for renderable content.

The `elements` property will contain an ordered array of the structured content elements in the doc; e.g.
`plaintext`, `richtext`, `image` or `video` elements.  Iterate through these to render them to your UI.

See https://zerocms.dev/integrations for documentation on all the elements.


### Internal links

Note that internal links, i.e. links from one doc to another, will have a `data-slug` property that references
the doc being linked to.

If your repo is configured to allow internal/doc links, then you will need to interpret and handle these references
to implement appropriate navigation from doc to doc in your UI.
npm package: @tamtamchik/app-store-server-typings
Description: Type definitions and interfaces for App Store APIs.
Author: Yuri Tkachenko
Latest version: 0.9.2

# Apple App Store Server Typings

[![Buy Me A Coffee][ico-coffee]][link-coffee]
[![Latest Version on NPM][ico-version]][link-npm]
[![Software License][ico-license]](./LICENSE)
[![Total Downloads][ico-downloads]][link-downloads]

Type definitions and interfaces for App Store APIs.

Supports the following APIs:

- [App Store Server Notifications](https://developer.apple.com/documentation/appstoreservernotifications) – Version 2.8 and below.
- [App Store Server API](https://developer.apple.com/documentation/appstoreserverapi) – Version 1.8 and below.

## Installation

Using npm:

```shell
npm install @tamtamchik/app-store-server-typings
```

Using yarn:

```shell
yarn add @tamtamchik/app-store-server-typings
```

## Contributing

Pull requests are always welcome. If you have bigger changes in mind, please open an issue first to discuss your ideas.

## License

Apple Receipt Parser is [MIT licensed](./LICENSE).

[ico-coffee]: https://img.shields.io/badge/Buy%20Me%20A-Coffee-%236F4E37.svg?style=flat-square
[ico-version]: https://img.shields.io/npm/v/@tamtamchik/app-store-server-typings.svg?style=flat-square
[ico-license]: https://img.shields.io/npm/l/@tamtamchik/app-store-server-typings.svg?style=flat-square
[ico-downloads]: https://img.shields.io/npm/dt/@tamtamchik/app-store-server-typings.svg?style=flat-square

[link-coffee]: https://www.buymeacoffee.com/tamtamchik
[link-npm]: https://www.npmjs.com/package/@tamtamchik/app-store-server-typings
[link-downloads]: https://www.npmjs.com/package/@tamtamchik/app-store-server-typings
npm package: @tamu-dor/babel-plugin-import-md-to-js
Description: Babel plugin to convert md imports into js objects
Author: Matt Voss
Latest version: 1.0.3

# babel-plugin-import-md-to-js

This is a simple babel plugin to inline markdown into js via marked and js-yaml.

This plugin is very much experimental due to use of the Babel6 API - largely undocumented. Contributions are welcome.

## Install

```shell
npm i @tamu-dor/plugin-import-md-to
```

## Usage

Place in plugins section of babel config

```javascript
plugins: [
  ...
  '@tamu-dor/babel-plugin-import-md-to-js',
  ...
],
```

The following command will convert everything in the `src` folder to `lib` using babel and our plugin.

    babel src/ -d lib/ --presets stage-0,es2015,react --plugins @tamu-dor/babel-plugin-import-md-to

Every js file that has a statement such as:

```javascript
import page from './page.md'
```

will be roughtly translated to:

```javascript
var page = {
    ...metadata
    contents: `...` // the md file without the metadata converted to html
}
```

You can also import markdown pages raw by placing the ! symbol at the end of the file. For example:

```javascript
import page from './page.md!'
```

will be roughtly translated to:

```javascript
var page = {
    ...metadata
    contents: `...` // the md file without the metadata
}
```

Notice that in both examples we split the metadata. This is done via the js-yaml module. Consider the following page:

```markdown
---
a: 1
b: 2
---

# Hello
```

will be translated to:

```javascript
var page = {
    a: 1,
    b: 2
    contents: `<h1>Hello</h1>`
}
```

## Use Cases

The only use case of this plugin is to be able to bundle markdown pages with your js components. It is good for portability.