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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions