open-index/open-npm huggingface dataset:
npm package: @proxima-analytics/analytics
Description: Proxima Analytics' tracking component for React/Next.js applications
Author: Proxima Analytics
Latest version: 1.0.1

# Proxima Analytics Package

A simple analytics tracking solution for React and Next.js applications.

## Installation

```bash
# npm
npm install @proxima-analytics/analytics

# yarn
yarn add @proxima-analytics/analytics

# pnpm
pnpm add @proxima-analytics/analytics

# bun
bun add @proxima-analytics/analytics
```

## Usage

### Next.js (App Router)
```tsx
// app/layout.tsx
import { Analytics } from '@proxima/analytics';

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Analytics publicKey={process.env.NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY} />
      </body>
    </html>
  );
}
```

### Next.js (Pages Router)
```tsx
// pages/_app.tsx
import type { AppProps } from 'next/app';
import { Analytics } from '@proxima/analytics';

export default function App({ Component, pageProps }: AppProps) {
  return (
    <>
      <Analytics publicKey={process.env.NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY} />
      <Component {...pageProps} />
    </>
  );
}
```

### React
```tsx
// App.tsx or App.jsx
import { Analytics } from '@proxima/analytics';

function App() {
  return (
    <>
      <Analytics publicKey="your_website_key_here" />
      {/* Your app content */}
    </>
  );
}

export default App;
```

## Environment Variables

### About the Analytics Key
The Proxima Analytics key (`NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY`) is a public identifier for your website/application. While it's safe to expose this key in your client-side code, we recommend using environment variables for better management and flexibility across different environments (development, staging, production).

### Setting up the Key

#### Next.js Applications
1. Create a `.env.local` file in your project root
2. Add your analytics key:
```env
NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY=your_website_key_here
```

Note: The `NEXT_PUBLIC_` prefix is required for client-side access in Next.js applications.

#### React Applications
For standard React applications, you can either:
- Use environment variables with your build system (Vite, Create React App, etc.)
- Directly pass the key to the Analytics component
```tsx
<Analytics publicKey="your_website_key_here" />
```

### Security Note
The analytics key is designed to be public and is safe to expose in your client-side code. 

## Features
- Lightweight analytics tracking
- TypeScript support
- Compatible with React 16.8+ and all Next.js versions
- Zero dependencies
- Safe to use with Server-Side Rendering (SSR)

## Requirements
- React 16.8.0 or higher
- Node.js 14.0.0 or higher

## License
MIT © Proxima Analytics
npm package: @proxima-analytics/react
Description: Proxima Analytics' tracking component for React/Next.js applications
Author: Proxima Analytics
Latest version: 1.0.5

# Proxima Analytics Package

A simple analytics tracking solution for React and Next.js applications.

## Installation

```bash
# npm
npm install @proxima-analytics/react

# yarn
yarn add @proxima-analytics/react

# pnpm
pnpm add @proxima-analytics/react

# bun
bun add @proxima-analytics/react
```

## Usage

### Next.js (App Router)
```tsx
// app/layout.tsx
import { Analytics } from '@proxima-analytics/react';

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Analytics publicKey={process.env.NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY} />
      </body>
    </html>
  );
}
```

### Next.js (Pages Router)
```tsx
// pages/_app.tsx
import type { AppProps } from 'next/app';
import { Analytics } from '@proxima-analytics/react';

export default function App({ Component, pageProps }: AppProps) {
  return (
    <>
      <Analytics publicKey={process.env.NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY} />
      <Component {...pageProps} />
    </>
  );
}
```

### React
```tsx
// App.tsx or App.jsx
import { Analytics } from '@proxima-analytics/react';

function App() {
  return (
    <>
      <Analytics publicKey="your_website_key_here" />
      {/* Your app content */}
    </>
  );
}

export default App;
```

## Environment Variables

### About the Analytics Key
The Proxima Analytics key (`NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY`) is a public identifier for your website/application. While it's safe to expose this key in your client-side code, we recommend using environment variables for better management and flexibility across different environments (development, staging, production).

### Setting up the Key

#### Next.js Applications
1. Create a `.env.local` file in your project root
2. Add your analytics key:
```env
NEXT_PUBLIC_PROXIMA_ANALYTICS_KEY=your_website_key_here
```

Note: The `NEXT_PUBLIC_` prefix is required for client-side access in Next.js applications.

#### React Applications
For standard React applications, you can either:
- Use environment variables with your build system (Vite, Create React App, etc.)
- Directly pass the key to the Analytics component
```tsx
<Analytics publicKey="your_website_key_here" />
```

### Security Note
The analytics key is designed to be public and is safe to expose in your client-side code. 

## Features
- Lightweight analytics tracking
- TypeScript support
- Compatible with React 16.8+ and all Next.js versions
- Zero dependencies

## Requirements
- React 16.8.0 or higher
- Node.js 14.0.0 or higher

## License
MIT © Proxima Analytics
npm package: @proxima-oss/gulp-tasks
Description: a collection of common gulp tasks
Latest version: 3.0.4

# gulp-tasks

`gulp-tasks` represents a core collection of gulp tasks for Proxima's TypeScript
repositories.

## Motivation

We ought to DRY up our gulpfiles, and the easiest way to do that is to create a
repo that actually contains all of our common gulp tasks. If a particular
application (or service) needs bespoke tasks, they can still be written inside
that particular repo.

## Usage

This package is meant to used in such a way that individual tasks (typed as
`Gulp.TaskFunction`s) can be imported as needed. Checkout the `Gulpfile.ts` at
the root level for an example.

## Bonus

It turns out, there's no need to write our Gulpfile's in `js` -- properly
configuring `ts-node` and `tsconfig-paths` allows for Gulp to transpile
`Gulpfile.ts` with zero issues.

## Contributing

NPM releases are published automatically via a github workflow (read: whenever
anyone publishes a github release). So, the easiest way to prepare this package
 for publication is via `np`:

```bash
np --no-publish --branch prod
```

This will draft a github release for you to fill in and then publish,
triggering the workflow.