Skip to content

Replacing webpack.js.org #158

Description

@avivkeller

We can replace webpack.js.org when the following issues are complete, let's consider these our priority issues, with the remainder being things that can happen after we replace the current site:

@webpack/gsoc-2026

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions