open-index/open-npm huggingface dataset:
npm package: @t2tx/nestjs-package-starter
Description: NestJS npm package starter
Author: Tei Jo
Latest version: 1.0.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

<h1 align="center"></h1>

<div align="center">
  <a href="http://nestjs.com/" target="_blank">
    <img src="https://nestjs.com/img/logo_text.svg" width="150" alt="Nest Logo" />
  </a>
</div>

<h3 align="center">NestJS npm Package Starter</h3>

<div align="center">
  <a href="https://nestjs.com" target="_blank">
    <img src="https://img.shields.io/badge/built%20with-NestJs-red.svg" alt="Built with NestJS">
  </a>
</div>

### Installation

1. Clone the repo
2. Run npm/yarn install

```bash
cd nestjs-package-starter
npm install
```

## Change Log

See [Changelog](CHANGELOG.md) for more information.

## Contributing

Contributions welcome! See [Contributing](CONTRIBUTING.md).

## Author

**John Biundo (Y Prospect on [Discord](https://discord.gg/G7Qnnhy))**

## License

Licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
npm package: @t3-oss/env-nextjs
Description: ![NPM Version](https://img.shields.io/npm/v/%40t3-oss%2Fenv-core) [![JSR](https://jsr.io/badges/@t3-oss/env-core)](https://jsr.io/@t3-oss/env-core) [![JSR Score](https://jsr.io/badges/@t3-oss/env-core/score)](https://jsr.io/@t3-oss/env-core) [![Socket Bad
Author: Julius Marminge
Latest version: 0.13.11

# Typesafe Envs made Simple

![NPM Version](https://img.shields.io/npm/v/%40t3-oss%2Fenv-core)
[![JSR](https://jsr.io/badges/@t3-oss/env-core)](https://jsr.io/@t3-oss/env-core)
[![JSR Score](https://jsr.io/badges/@t3-oss/env-core/score)](https://jsr.io/@t3-oss/env-core)
[![Socket Badge](https://socket.dev/api/badge/npm/package/@t3-oss/env-core)](https://socket.dev/npm/package/@t3-oss/env-core/overview)

The Next.js package comes preconfigured for Next.js and also enforces some extra rules by default to make sure you have out-of-the-box compatibility in all different Next.js runtimes.

> For full documentation, see https://env.t3.gg

## Installation

```bash
# npm
npm i @t3-oss/env-nextjs

# pnpm
pnpm add @t3-oss/env-nextjs

# bun
bun add @t3-oss/env-nextjs

# deno
deno add jsr:@t3-oss/env-nextjs
```

## Usage

> [!NOTE]
>
> You may use any [Standard Schema](https://standardschema.dev) compliant validator of your choice. This example uses Zod

```ts
// src/env.ts
import { createEnv } from "@t3-oss/env-nextjs";
import * as z from "zod";

export const env = createEnv({
  /*
   * Serverside Environment variables, not available on the client.
   * Will throw if you access these variables on the client.
   */
  server: {
    DATABASE_URL: z.url(),
    OPEN_AI_API_KEY: z.string().min(1),
  },
  /*
   * Environment variables available on the client (and server).
   *
   * 💡 You'll get type errors if these are not prefixed with NEXT_PUBLIC_.
   */
  client: {
    NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: z.string().min(1),
  },
  /*
   * Specify what values should be validated by your schemas above.
   *
   * If you're using Next.js < 13.4.4, you'll need to specify the runtimeEnv manually
   * For Next.js >= 13.4.4, you can use the experimental__runtimeEnv option and
   * only specify client-side variables.
   */
  runtimeEnv: {
    DATABASE_URL: process.env.DATABASE_URL,
    OPEN_AI_API_KEY: process.env.OPEN_AI_API_KEY,
    NEXT_PUBLIC_PUBLISHABLE_KEY: process.env.NEXT_PUBLIC_PUBLISHABLE_KEY,
  },
  // experimental__runtimeEnv: {
  //   NEXT_PUBLIC_PUBLISHABLE_KEY: process.env.NEXT_PUBLIC_PUBLISHABLE_KEY,
  // }
});
```
npm package: @t3-oss/env-nuxt
Description: ![NPM Version](https://img.shields.io/npm/v/%40t3-oss%2Fenv-core) [![JSR](https://jsr.io/badges/@t3-oss/env-core)](https://jsr.io/@t3-oss/env-core) [![JSR Score](https://jsr.io/badges/@t3-oss/env-core/score)](https://jsr.io/@t3-oss/env-core) [![Socket Bad
Author: Julius Marminge
Latest version: 0.13.11

# Typesafe Envs made Simple

![NPM Version](https://img.shields.io/npm/v/%40t3-oss%2Fenv-core)
[![JSR](https://jsr.io/badges/@t3-oss/env-core)](https://jsr.io/@t3-oss/env-core)
[![JSR Score](https://jsr.io/badges/@t3-oss/env-core/score)](https://jsr.io/@t3-oss/env-core)
[![Socket Badge](https://socket.dev/api/badge/npm/package/@t3-oss/env-core)](https://socket.dev/npm/package/@t3-oss/env-core/overview)

The Nuxt package comes preconfigured for Nuxt, and fills the runtimeEnv option automatically. All you need to do is define your schemas!

> For full documentation, see https://env.t3.gg

## Installation

```bash
# npm
npm i @t3-oss/env-nuxt

# pnpm
pnpm add @t3-oss/env-nuxt

# bun
bun add @t3-oss/env-nuxt

# deno
deno add jsr:@t3-oss/env-nuxt
```

## Usage

> [!NOTE]
>
> You may use any [Standard Schema](https://standardschema.dev) compliant validator of your choice. This example uses Zod

```ts
// src/env.ts
import { createEnv } from "@t3-oss/env-nuxt";
import * as z from "zod";

export const env = createEnv({
  /*
   * Serverside Environment variables, not available on the client.
   * Will throw if you access these variables on the client.
   */
  server: {
    DATABASE_URL: z.url(),
    OPEN_AI_API_KEY: z.string().min(1),
  },
  /*
   * Environment variables available on the client (and server).
   *
   * 💡 You'll get type errors if these are not prefixed with NUXT_PUBLIC_.
   */
  client: {
    NUXT_PUBLIC_CLERK_PUBLISHABLE_KEY: z.string().min(1),
  },
});
```
npm package: @t3/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.2.1

# React-scripts - T3

This project is a fork of `create-react-apps` `react scripts` directory.

## Changes from create-react-app:

1. SCSS - [sass loader](https://github.com/webpack-contrib/sass-loader) has been added and configured to compile any `.scss` file in the `src` directory

2. [webpack-bundle-tracker](https://github.com/ezhome/webpack-bundle-tracker) - webpack plugin that exposes the file names for output bundles for Django apps to consume

3. [webpack-bundle-analyzer](https://www.npmjs.com/package/webpack-bundle-analyzer) - webpack plugin that outputs an interactive mapping of the JavaScript bundle to describe JS library sizes

4. Testing libaries - includes [Enzyme](https://github.com/airbnb/enzyme), [Chai](http://chaijs.com/), and [Sinon](http://sinonjs.org/) by default for more advanced testing capability

5. CI - A [`.gitlabci.yml`](https://docs.gitlab.com/ee/ci/README.html) file that runs a simple build > test > lint pipeline over the project. By default linter failures will only output warnings.
npm package: @t3kit/t3kit-cli
Description: The t3kit command line interface
Author: t3kit team
Latest version: 0.2.0

# t3kit-cli [![npm version](https://badge.fury.io/js/t3kit.svg)](https://badge.fury.io/js/t3kit)
```
t3kit command line interface
```

The t3kit command line interface makes it easy to start with subtheme_t3kit, make t3kit release, etc...

Use the ` t3kit -h ` or ` t3kit --help ` command for more info about utility.

### [CHANGELOG](https://github.com/t3kit/t3kit/blob/master/CHANGELOG.md)
### [CONTRIBUTING](https://github.com/t3kit/t3kit/blob/master/CONTRIBUTING.md)


### Minimal `t3kit` requirements:
 - [Git](https://git-scm.com/)
 - [NodeJs](http://nodejs.org/) >= 6.10.3
 - [NPM](https://github.com/npm/npm) >= 3.10.10


## Install this globally and you'll have access to the t3kit command anywhere on your system.

```
[sudo] npm install -g @t3kit/t3kit-cli
```

_Note: You might need to use `sudo` before `npm` command to install package_ **globally**


## Starting:

To start using **t3kit** just use command `t3kit` and follow the instructions
```
t3kit
```

## Flags/options:

```
[ -s | --subtheme ]          generate new subtheme_t3kit_name
[ -h | --help ]              show t3kit CLI help
[ -v | --version ]           show t3kit CLI version
```
npm package: @t3kkitz/prettier-config
Description: My personal Prettier config
Author: Sergei @t3kkitz Bulgakov
Latest version: 1.2.0

# `@t3kkitz/prettier-config`
![npm (scoped)](https://img.shields.io/npm/v/@t3kkitz/prettier-config.svg)

> My personal [Prettier](https://prettier.io) config.

## Usage

**Install**:

```bash
$ yarn add --dev @t3kkitz/prettier-config
```

**Edit `package.json`**:

```jsonc
{
  // ...
  "prettier": "@t3kkitz/prettier-config"
}
```

**Or extend config by `.prettierrc.js`**:

```js
module.exports = {
  ...require("@t3kkitz/prettier-config"),
  semi: false
};
```