webpack

Mentors: Student: ryzrr

The Problem When developers write custom webpack plugins, they need reliable API documentation. Currently, the generated docs drop critical function signatures, returning unhelpful {object} types instead of actual parameters. The new documentation infrastructure is also missing webpack's visual identity, essential navigation pages, and a safe review process for automated updates. The Solution I will complete the TypeDoc to doc-kit pipeline to finalize webpack's API documentation redesign. First, I will fix the AST renderers to properly map TypeScript function overloads so no signature data is lost. Then, I will configure the doc-kit UI with webpack brand tokens and build custom React components to cleanly display complex hooks. Finally, I will secure the CI/CD workflow and port the core website pages. Deliverables: Accurate API Output: A fixed TypeDoc theme that correctly renders function parameters and TypeScript overloads. Visual Identity: A custom doc-kit configuration with webpack branding and new React components (HookSignature, PluginInterface, DeprecationBanner). Automated CI/CD: A GitHub Actions workflow that safely opens pull requests for new docs instead of pushing directly. Core Navigation: Fully ported Home, Download, Guides, and About pages.

Mentors: Student: Mo_Shams

Webpack's extensive API definitions are currently locked inside raw types.d.ts files, creating a significant manual maintenance burden to keep the public documentation synced. My proposal solves this by building an automated, version-aware CI/CD pipeline. I will extract TypeScript ASTs using TypeDoc, format them via typedoc-plugin-markdown with a custom webpack-doc-kit theme, and integrate them into @node-core/doc-kit. The final deliverable is a polished, searchable React-based UI that matches Webpack's visual identity, completely removing the manual documentation overhead from the core team.

Mentors: Student: __tushar

Webpack currently lacks a modern, automated documentation site. Existing documentation is manually maintained, lacks API reference generation, and has no automated pipeline to stay in sync with webpack's source code. This project aims to build a fully automated documentation system for webpack using TypeDoc and @node-core/doc-kit. The pipeline extracts API documentation directly from webpack's types.d.ts, generates structured markdown, and renders a complete website - including API reference, guides, loaders, plugins, and core pages like Home and Download. Key deliverables: • A complete TypeDoc theme producing doc-kit-compatible markdown. • Webpack-branded site using doc-kit's theming system (#theme/* components) that aligns webpack's documentation with the OpenJS Foundation's design standards. • Multi-version documentation support (v5, v6 and beyond). • Fully automated CI/CD pipeline that syncs with webpack releases. The overarching goal is zero manual documentation maintenance - every webpack release automatically triggers doc regeneration and deployment, keeping the documentation accurate and fresh without human intervention.

Mentors: Student: Ryuya

This project aims to modernize Webpack by implementing comprehensive support for ECMAScript Modules (ESM) output. Webpack currently lacks robust ESM output capabilities, creating challenges for developers working with modern JavaScript. The implementation will focus on four key areas: parser and module analysis enhancements to detect strict mode compatibility issues and identify statically exportable modules; code generation improvements to properly transform CommonJS to ESM exports; runtime optimization to eliminate unnecessary boilerplate; and platform-specific feature support for CSS modules, URL handling, and ESM workers.

Mentors: Student: Uzair Khan

This proposal outlines the development of create-webpack-app, a webpack cli tool designed to streamline project setup for web development. Leveraging the power of Webpack, create-webpack-app will provide a user-friendly interface for selecting frameworks like React, Vue, or Svelte. Users can then generate a complete project structure pre-populated with essential files, configurations, and a tailored Webpack configuration for both development and production builds. The planned 12-week development utilizes Plop.js to create reusable templates, ensuring flexibility and customization. A core base template will be established, containing essential project files like package.json, README.md, and a foundational webpack.config.js. This will be complemented by framework-specific templates pre-filled with boilerplate code relevant to the chosen framework. Additionally, comprehensive user documentation will be created, guiding users through installation, usage, and framework-specific considerations. By prioritizing a lightweight and customizable approach, this proposal lays the groundwork for future enhancements, including broader framework support and potential community contributions.