This is a Nuxt.js 2 authentication module that provides zero-boilerplate authentication support. It implements various authentication schemes (local, OAuth2, OpenID Connect, refresh tokens) and integrates with popular providers like Auth0, Google, Facebook, and Laravel-based systems. The module handles token storage, automatic refresh, user management, and provides middleware for route protection. It uses a modular architecture with core auth logic, scheme implementations, provider configurations, and utility functions.
This is a Nuxt 3 module that integrates Cloudflare Turnstile, a privacy-focused CAPTCHA alternative. It provides a Vue component (`<NuxtTurnstile>`) for client-side rendering of the Turnstile widget, a composable (`useScriptCloudflareTurnstile`) for script loading via `@nuxt/scripts`, and a server-side utility (`verifyTurnstileToken`) for token validation in Nitro endpoints. The module automatically handles script injection, token refresh, and exposes a reset method. It also supports an optional validation endpoint at `/_turnstile/validate`. The architecture follows the standard Nuxt module pattern: `src/module.ts` registers components, composables, and server handlers. External dependencies include Cloudflare's Turnstile API, `@nuxt/scripts`, `@nuxt/kit`, `defu`, and `pathe`. The codebase is well-structured, typed, and includes end-to-end tests with Playwright.
This is a Nuxt module for device detection that provides a reactive `$device` object and `useDevice()` composable. It determines device type (mobile, tablet, desktop), operating system (iOS, Android, Windows, macOS, Linux), browser (Chrome, Firefox, Edge, Safari, Samsung), and crawler status by parsing the User-Agent header and/or CDN-provided headers (Amazon CloudFront, Cloudflare). The core detection logic is encapsulated in `src/runtime/generateFlags.ts`, which is a standalone, well-tested function. The module is built for Nuxt 3+ (ESM-only) and uses `crawler-user-agents` for crawler detection with a build-time generated regex for performance. The codebase is small, focused, and demonstrates good engineering practices with clean separation of concerns, comprehensive tests, and proper use of Nuxt module APIs.
Nuxt Security is a Nuxt 3+ module that automatically configures applications to follow OWASP security patterns through HTTP headers and middleware. It provides security response headers (including CSP with nonce/hash support for SSR/SSG), request size and rate limiting, XSS validation, CORS support, and optional features like Basic Auth and CSRF protection. The architecture uses Nitro plugins to integrate with Nuxt's server lifecycle, separating concerns between configuration, middleware, build-time plugins, and runtime hooks. The module handles both SSR and SSG modes appropriately, using nonces for CSP in SSR and computed hashes for SSG, with proper strict-dynamic support.
This is a Nuxt 3 module that integrates Apollo GraphQL client into Nuxt applications. It provides a flexible configuration system for defining multiple Apollo clients with HTTP and WebSocket endpoints, authentication token management, and SSR support. The module auto-imports composables like useAsyncQuery, useQuery, useMutation, and useSubscription, and provides hooks for custom authentication and error handling. It also supports hot module replacement for Apollo client configuration files. The architecture uses Nuxt's module system (defineNuxtModule) to hook into the build process. It reads client configurations from nuxt.config or external files, generates runtime templates, and sets up a Nuxt plugin that creates ApolloClient instances with appropriate links (HTTP, WebSocket, auth, error). The composables layer provides SSR-friendly async query wrappers and authentication helpers. WebSocket support includes a restartable client for reconnection. Key entry points are src/module.ts (module setup), src/runtime/plugin.ts (client creation and plugin), and src/runtime/composables.ts (user-facing composables). External dependencies include @apollo/client, @vue/apollo-composable, graphql-ws, and @nuxt/kit.
This is a Nuxt module that integrates Swiper.js into Nuxt 3 applications using Web Components. It provides automatic registration of `<swiper-container>` and `<swiper-slide>` custom elements, a Vue composable (`useSwiper`) for reactive Swiper instance control, and support for both bundled and individual Swiper module imports. The module is minimal, well-typed, and leverages Nuxt's module system for configuration. It includes a playground and test fixture but no complex business logic. The codebase is clean and modern, with proper TypeScript types and a structured setup, though the test suite is practically empty. The composable is well-crafted and could be extracted as a standalone utility.
This repository is a Nuxt.js 2 module that integrates Sentry error tracking into Nuxt applications. It provides client-side and server-side Sentry initialization, lazy loading, performance tracing, release management, and extensive integration configuration. The module hooks into Nuxt's build process via a custom shim for @nuxt/kit, generating plugin templates and configuring webpack. It supports both JavaScript and TypeScript projects, with options for custom integrations and runtime configuration. The codebase is well-structured with clear separation of concerns (module entry, hooks, options resolution, utilities, templates) and includes a comprehensive test suite using vitest and playwright. However, it is specifically designed for Nuxt 2, which is now deprecated, and the official Sentry Nuxt module is recommended for Nuxt 3+. The repository appears to be in maintenance mode with the last release in September 2024 and no recent commits.
nuxt-purgecss is a Nuxt 3 module that integrates PurgeCSS to remove unused CSS from the final build. It hooks into Nuxt's PostCSS configuration to add the `@fullhuman/postcss-purgecss` plugin with sensible defaults tailored for Vue and Nuxt projects. The module automatically scans common Nuxt directories (components, layouts, pages, composables, app files, plugins, and nuxt.config) for used CSS classes, and includes a safelist of typical Nuxt classes (e.g., transition classes, nuxt-link classes, scoped style attributes) to prevent accidental removal. It also provides a custom default extractor that strips inline `<style>` blocks from Vue Single File Components before extraction, ensuring that only classes used in templates are considered. The module is disabled by default in development mode and can be configured via the `purgecss` key in `nuxt.config`. The codebase is small, well-structured, and includes integration tests using `@nuxt/test-utils` that verify correct purging behavior on a playground Nuxt project. However, the project has seen no releases since September 2022 and relies on outdated dependencies (e.g., Nuxt 3 RC, Node 16 in CI), indicating it is no longer actively maintained.
This repository is `@nuxtjs/dotenv`, a small Nuxt.js (v2) build-time module that reads a `.env` file, parses it with the `dotenv` library, and injects the variables into Nuxt's `this.options.env`. Nuxt then exposes those values to the application through `process.env` and `context.env`. The module supports custom filenames, custom paths, an allowlist via the `only` option, and optional merging of system environment variables via `systemvars`. It deliberately does not override environment values already defined in `nuxt.config.js`, and it warns instead of crashing when no `.env` file is present. Architecturally this is a tiny npm library, not an application or data pipeline: the core is a single Nuxt module function in `lib/module.js` plus a `consola`-based logger in `lib/logger.js`. It is invoked during Nuxt builds and has no CLI, web server, or long-running process. The test suite uses `@nuxtjs/module-test-utils` to boot fixture Nuxt applications and assert on rendered HTML, covering basic loading, custom file names, custom paths, missing files, and the `only` allowlist behavior. The code is clean, well-tested, and easy to understand, but the surrounding ecosystem has moved on. Nuxt 2 is end-of-life, and the README itself recommends migrating to Nuxt's built-in runtime config. Dependencies such as `dotenv@^8.2.0` and Nuxt 2 edge are old, and the project is effectively in maintenance limbo despite occasional repository activity.