open-index/open-npm huggingface dataset:
npm package: @nexray/app
Description: This template should help get you started developing with Tauri, Next.js and Typescript.
Latest version: 0.1.0-alpha.4

# Tauri + Next.js + Typescript

This template should help get you started developing with Tauri, Next.js and Typescript.

## Recommended IDE Setup

- [VS Code](https://code.visualstudio.com/) + [Tauri](https://marketplace.visualstudio.com/items?itemName=tauri-apps.tauri-vscode) + [rust-analyzer](https://marketplace.visualstudio.com/items?itemName=rust-lang.rust-analyzer)

Example of next.js project deployed as NPM package: https://github.com/grouparoo/grouparoo/tree/main/ui/ui-community, https://www.grouparoo.com/blog/distributing-nextjs-via-npm
npm package: @nexray/app-playground
Description: Next.js introduced the `app/` directory (beta). This is the result of the [Layouts RFC](https://nextjs.org/blog/layouts-rfc) previously published for community feedback. This includes support for:
Latest version: 0.1.0-alpha.4

# Next.js App Directory Playground

Next.js introduced the `app/` directory (beta). This is the result of the [Layouts RFC](https://nextjs.org/blog/layouts-rfc) previously published for community feedback. This includes support for:

- **Layouts:** Easily share UI while preserving state and avoiding re-renders.
- **Server Components:** Making server-first the default for the most dynamic applications.
- **Streaming:** Display instant loading states and stream in updates.
- **Suspense for Data Fetching:** `async`/`await` support and the `use` hook for component-level fetching.

The `app/` directory can coexist with the existing `pages` directory for incremental adoption. While you **don't need to use the `app/` directory** when upgrading to Next.js 13, we're laying the foundations to build complex interfaces while shipping less JavaScript.

## Running Locally

1. Install dependencies:

```sh
pnpm install
```

2. Start the dev server:

```sh
pnpm dev
```

## Documentation

https://beta.nextjs.org/docs

## Leave Feedback

https://github.com/vercel/next.js/discussions/41745
npm package: @nexrender/action-cache
Description: Cache your template source to a specified location and reuse it on subsequent runs
Author: dylangarcia
Latest version: 1.60.9

# Action: Cache

Cache your template source to a specified location and reuse it on subsequent runs

## Installation

```
npm i -g @nexrender/action-cache
```

## Usage

When creating your render job provide this module in **both** of the `predownload` and `postdownload` actions:

## Additional Params
- ttl (optional): a time-to-live in milliseconds for which after that the cached item is invalidated
- cacheAssets (optional): a boolean value that if true will cache the assets used by a job as well. Note that assets with the same filename will overwrite each other in the cache so should be avoided if using assets cache.

```js
// job.json
{
    "actions": {
        "predownload": [
            {
                "module": "@nexrender/action-cache",
                "cacheDirectory": "~/cache",
                "ttl": 3600000
            }
        ],
        "postdownload": [
            {
                "module": "@nexrender/action-cache",
                "cacheDirectory": "~/cache"
            }
        ],
    }
}
```