Next.js Repository Documentation

The next-taskless crate provides Next.js utilities designed to operate without a dependency on turbo-tasks. This decoupling allows these utilities to be shared across different build toolchains, specifically webpack and rspack codepaths.

To ensure compatibility in environments where native bindings are unavailable, this crate is designed to be compilable to WebAssembly (WASM).

The turbo-unix-path crate provides utilities for the lexical manipulation of Unix-style (/-separated) paths represented as Unicode strings. These path types are used within Turbopack to represent platform-agnostic relative paths, which are frequently used for JavaScript imports.

Important Note: This crate is strictly for lexical manipulation and does not perform any I/O operations. If you need to interact with the file system, you should use the turbo-tasks-fs crate instead.

@next/third-parties is an experimental collection of components and utilities designed to help developers efficiently load third-party libraries into Next.js applications.

Note: This package is currently experimental and under active development.

The Turbopack Ecmascript Runtime provides the essential JavaScript code injected at runtime to enable Turbopack's core functionality. This includes responsibilities such as:

• Chunk loading: Managing how code chunks are fetched and executed.
• Module factory instantiation: Handling the creation of module instances.
• Hot Module Replacement (HMR): In development mode, the runtime includes code for Fast Refresh to enable real-time updates.

Note that the runtime code is specifically designed to be compiled and concatenated at Rust build-time rather than being distributed as standard EcmaScript (ESM) or CommonJS modules.

This example demonstrates the integration of Redux Toolkit within a Next.js application. It showcases standard RTK patterns such as:

• Store Setup: Using configureStore to initialize the Redux store.
• Creating Reducers: Writing immutable update logic.
• Creating Slices: Using createSlice to manage entire segments of state at once.

The implementation is specifically tailored for TypeScript environments.

When implementing a deployment adapter, you can address several common requirements for integrating Next.js with specific hosting environments or build pipelines. Common patterns include:

• Deployment Platform Integration: Automatically configuring build outputs to match the requirements of specific hosting platforms.
• Asset Processing: Transforming or optimizing build outputs during the deployment lifecycle.
• Monitoring Integration: Collecting build metrics and routing information for observability.
• Custom Bundling: Packaging application outputs into platform-specific formats.
• Build Validation: Implementing checks to ensure build outputs meet specific platform or project requirements.
• Route Generation: Using processed route information to generate platform-specific routing configurations (e.g., for edge functions or specific serverless providers).

The Bundle Analyzer is a Next.js application used to visualize bundle sizes and analyze dependencies through interactive treemaps. It allows developers to perform route-based analysis, track dependency import chains, and filter bundle data by environment (client vs. server) or file type (JS, CSS, JSON, or Assets). It also includes search functionality to locate specific files within a bundle.

Note: This package is not published to npm. It is built and vendored directly into the main next package during its build process.

If you prefer not to self-host or need advanced streaming features, several third-party services offer specialized components and SDKs for Next.js:

• next-video: An open-source component providing a <Video> component compatible with Vercel Blob, S3, Backblaze, and Mux.
• Cloudinary: Offers the <CldVideoPlayer> component for drop-in support and Adaptive Bitrate Streaming.
• Mux: Provides high-performance video embedding and starter templates for Next.js.
• ImageKit.io: Provides the <IKVideo> component for seamless video support.
• Fastly: Offers solutions for video on demand and streaming media.

The next-intl implementation in this example provides several core capabilities for internationalization:

• ICU Syntax Support: Uses standard ICU syntax for complex translations including interpolation, numbers, dates, times, plurals, and rich text.
• Format.JS Integration: Built on top of Format.JS building blocks for high-quality, low-level i18n APIs.
• Integrated Formatting: Built-in number and date formatting that works seamlessly with translations to ensure consistent global app formatting.
• Hooks-only API: Provides a consistent API via hooks that can be used for both React children and string attributes.
• Rendering Support: Fully integrates with both Static Site Generation (SSG) and Server-Side Rendering (SSR).