Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Shared chunks are included multiple times

Open
#51 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
build-system

Research direction

Start with the linked reproduction and compare rspack-dist/index.html with webpack-html/index.html, focusing on the duplicated runtime.js script and other shared chunks. Trace the HTML generation path from the reproduction, then verify that each shared chunk appears only once in the generated output.

Written by the indexing model from the issue text.

Description

Current behaviour 💣

All the shared chunks are included multiple times as scripts in the output html page

Expected behaviour ☀️

Each chunk is included only once

Reproduction Example 👾

https://github.com/flipatlas/rspack-repro-html-plugin-broken-chunks/tree/main

You can see that runtime.js for example has been included twice in rspack-dist/index.html but only once in webpack-html/index.html

Environment 🖥

Same as in repro

Dominant language
JavaScript
Stars
19
Forks
4
Avg merge
7h 17m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstackjs/html-rspack-plugin

All issues in rstackjs/html-rspack-plugin

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.