open-index/open-npm huggingface dataset:
npm package: @mittirorg/svelte-datepicker
Description: Ultimate calendar for your Svelte app.
Author: Rahul Mitra
Latest version: 0.0.1

# svelte-datepicker

This repository hosts a customizable and responsive datepicker component built using the Svelte. Whether you're building a personal productivity app, a scheduling application, or just need a sleek and efficient datepicker UI, this project has you covered.

## Features

- **Flexible Customization**: Tailor the datepicker to your design needs with customizable themes, color schemes, and event markers.
- **Responsive Design**: The datepicker seamlessly adapts to various screen sizes, ensuring a consistent experience across devices.
- **Event Integration**: Easily integrate events, appointments, and important dates into the datepicker for a comprehensive scheduling solution.
- **Smooth Animations**: Enjoy smooth and engaging animations for seamless navigation and interaction with the datepicker.
- **User-friendly Interface**: The intuitive interface makes it easy for users to navigate, select dates, and manage their schedules.

## Getting Started

To start using the `svelte-datepicker` in your project, follow these simple steps:

1. Clone or download this repository.
2. Integrate the datepicker component into your Svelte application using the provided examples.

## Usage

Here's an example of how you can integrate the svelte-datepicker component into your Svelte application:

```svelte
<script>
  import Calendar from 'svelte-datepicker';
</script>

<Calendar />
```

## User guide

### Calendar

Displays a complete, interactive datepicker.

#### Props

| Prop name | Description | Example values |
| --- | --- | --- |
| `onChange` | Function called when the user clicks an item (day on month view, month on year view and so on) on the most detailed view available. | `(date) => {}` |
| `onViewChange` | Function called when the user navigates from one view to another using prev/next up button or by clicking a tile. `viewTypes` are `month`, `year` & `decade` | `(viewType) => {}` |
| `startDate` | The beginning of a period that shall be displayed by default. | `new Date(2017, 0, 1)` |
| `rootClass` | Class name that will be applied to a given datepicker wrapper | String: `"class1 class2"` |
| `calendarWrapperClass` | Class name that will be applied to different view type of datepicker wrapper,  | String: `"class1 class2"` |
| `defaultView` | Determines which datepicker view shall be opened initially. Does not disable navigation. Can be `"month"`, `"year"`, `"decade"`, it's optional. | `"month"` |
| `allowedViews` | Will be an array of views that should be displayed while user navigates the datepicker/datepicker, it's optional | initial value: `["month", "year", "decade"]` |
npm package: @mitto98/nuxt-auth-tmp
Description: Authentication module for Nuxt.js
Latest version: 5.0.0-dev

<h1 align="center" >🔑 Auth Module</h1>
<p align="center">Zero-boilerplate authentication support for Nuxt.js!</p>

<p align="center">
<a href="https://david-dm.org/nuxt-community/auth-module">
    <img alt="" src="https://david-dm.org/nuxt-community/auth-module/status.svg?style=flat-square">
</a>
<a href="https://standardjs.com">
    <img alt="" src="https://img.shields.io/badge/code_style-standard-brightgreen.svg?style=flat-square">
</a>
<a href="https://circleci.com/gh/nuxt-community/auth-module">
    <img alt="" src="https://img.shields.io/circleci/project/github/nuxt-community/auth-module.svg?style=flat-square">
</a>
<a href="https://codecov.io/gh/nuxt-community/auth-module">
    <img alt="" src="https://img.shields.io/codecov/c/github/nuxt-community/auth-module.svg?style=flat-square">
</a>
<br>
<a href="https://npmjs.com/package/@nuxtjs/auth-next">
    <img alt="" src="https://img.shields.io/npm/v/@nuxtjs/auth-next/latest.svg?style=flat-square">
</a>
<a href="https://npmjs.com/package/@nuxtjs/auth">
    <img alt="" src="https://img.shields.io/npm/dt/@nuxtjs/auth-next.svg?style=flat-square">
</a>
</p>

<p align="center">
<a href="https://auth.nuxtjs.org">Read Documentation</a>
</p>

**🚧 please see [status page](http://auth.nuxtjs.org/status) in documentation.**

## Development

Running demo for development:

```bash
$ yarn install
$ yarn dev
```

Running tests for development:

```bash
$ yarn build
$ yarn nuxt build test/fixture
$ yarn jest
```

## License

[MIT License](./LICENSE) - Copyright (c) Nuxt Community
npm package: @mittwald/api-client-commons
Description: Common types and utilities for mittwald API clients
Author: Mittwald CM Service GmbH & Co. KG
Latest version: 4.343.0

Common code base used by `@mittwald/api-client-*` package.

## API

### assertStatus, assertOneOfStatus

The API client does not validate any response status by design, to give you the
most flexibility while handling also erroneous responses. If you want to assert
some desired response status, you can use the `assertStatus` resp.
`assertOneOfStatus` function.

#### assertStatus(response, expectedStatus)

Returns: void

This method throws an `ApiClientError` if the given `response` does not match
the `expectedStatus`.

When you are using TypeScript this function also asserts the correct response
type.

```ts
const response = await client.project.getProject({
  pathParameters: {
    projectId: "...",
  },
});

assertStatus(response, 200);

const project = response.data;
// Project properties can now be accessed safely
const name = project.name;
```

#### assertOnOfStatus(response, expectedStatus)

Returns: void

This method throws an `ApiClientError` if the given `response` does not match
the `expectedStatus`.

When you are using TypeScript this function also asserts the correct response
type.

```ts
const response = await client.project.getProject({
  pathParameters: {
    projectId: "...",
  },
});

assertOneOfStatus(response, [200, 404]);

if (!response.data) {
  console.log("Project not found");
}
```

### Common interceptors

To make it easy to opt in to some API mechanisms, a few
[interceptors](https://axios-http.com/docs/interceptors) can be easily
configured.

#### withAccessToken

In most cases you want to add the users access token to every API-Request as a
request header. This can be tedious if you need to do this on your own. To
automatically set the request header use `withAccessToken` for your `APIClient`
instance.

```ts
const client = new APIClient({ baseURL });
const authenticatedClient = withToken(client, token);
```

#### withEventConsistencyHandling

To opt in into the
[event consistency handling](https://developer.mittwald.de/docs/v2/api/intro/#eventual-consistency)
you might use `withEventConsistencyHandling`. This will set automatically handle
the `etag` response header and set its value as `if-event-reached` request
header for GET requests:

```ts
const client = new APIClient({ baseURL });
const authenticatedClient = withEventConsistencyHandling(client);
```
npm package: @mittwald/api-code-generator
Description: Common code base used by `@mittwald/api-client-*` package.
Latest version: 4.343.0

Common code base used by `@mittwald/api-client-*` package.

## CLI

Use the CLI commands provided by this package to build your API client and
validate the OpenAPI-Spec:

```shell
acg validate spec/openapi.json
acg generate --name MittwaldAPIV2 spec/openapi.json src/generated --optionalHeader x-access-token
```

## TypeScript API

If you need to generate the client in code, you can use the TypeScript API
demonstrated in this template:

```typescript
import * as path from "path";
import { UniversalContentLoader } from "@mittwald/api-code-generator/js";
import { UniversalFileLoader } from "@mittwald/api-code-generator/js";
import { OpenApiSpec } from "@mittwald/api-code-generator/js";
import { CodeGenerationModel } from "@mittwald/api-code-generator/js";
import { prepareTypeScriptOutput } from "@mittwald/api-code-generator/js";
import { writeIfChangedAsync } from "@mittwald/api-code-generator/js";

const name = "MittwaldAPIV2";
const inout = `${process.cwd()}/spec/openapi.json`;
const output = `${process.cwd()}/src/generated`;

// Loading OpenAPI spec
const loader = new UniversalContentLoader(new UniversalFileLoader(input));
const openApiDoc = await loader.load();

// Parsing OpenAPI spec
const spec = await OpenApiSpec.parse(openApiDoc, {
  skipValidation: flags.skipValidation,
});

// Building transformation model
const model = CodeGenerationModel.fromDoc(name, spec.document);

// Generating descriptors
const descriptorsFileContent = model.paths.compileDescriptors();
await writeIfChangedAsync(
  path.join(output, "descriptors.ts"),
  await prepareTypeScriptOutput(descriptorsFileContent),
);

// Generating types
const typesFileContent = await model.compileTypes({
  rootNamespace: flags.name,
  optionalHeaders: ["x-access-token"],
});
await writeIfChangedAsync(
  path.join(output, "types.ts"),
  await prepareTypeScriptOutput(typesFileContent),
);

// Generating client
const clientFileContent = model.paths.compileClient();
await writeIfChangedAsync(
  path.join(output, "client.ts"),
  await prepareTypeScriptOutput(clientFileContent),
);

// if needed: Generating React client
const reactClientFileContent = model.paths.compileReactClient();
await writeIfChangedAsync(
  path.join(output, "client-react.ts"),
  await prepareTypeScriptOutput(reactClientFileContent),
);
```