Iteration plan for April - June

[hardfist]

This issue serves as an Epic to provide transparency for our community and collaborators, internal and external, informed about our current goals and timelines.

We will be actively working on the tasks listed below, which have been aligned with our goals for the next three months (April - June 2023).

If you see something that is not in this list but is strongly needed. Please write a detailed requirement in this issue if you feel the need for feature prioritization. Also remember this is not a complete list so please search for relevant issues beforehand.

For broader collaboration, you can also find us on discord if you need a quick chat.

Loaders and Plugins

We are dedicated to investing significant time and resources into collaborating with the open source community on loaders and plugins. Pull requests are greatly welcomed and encouraged in this regard.

Unordered list:

Tasks

Preview Give feedback

1. [Tracking issue] vue support #2350
   4 of 4
   team tracking issue +2
   
2. [Feature Request]: Storybook support #2591
   feat team tracking issue +3
3. [Feature Request]: pitching loader support #2394
   p1-important team +2
   
4. [Tracking issue]: Progressive inline-loader-syntax support #1749
   p1-important team tracking issue +3
   
5. [Tracking issue] Angular support #2373
   5 of 5
   team +1

APIs

Some of the loaders and plugins require additional APIs, they are tracked separately.

Tasks

Preview Give feedback

1. [Feature Request]: support webpackChunkName #2385
   block: modern.js feat p1-signifincant-downstream-blocker team +4
   
2. [Feature Request]: support output.chunkLoadingGlobal #2388
   block: modern.js feat p1-signifincant-downstream-blocker team +4
   
3. [Feature Request]: Support DataURL import #2422
   feat p2-signifincant team +3
   

Performance

To pave the road for caching abilities, we will start small and improve our HMR time first. This is driven by some of the mega projects internally.

Tasks

Preview Give feedback

1. [Tracking issue] support incremental rebuild #2361
   team tracking issue +2
   

Engineering

Our current top priority is to improve build and test infrastructure to offer better stability, so the core can be improved over time without breaking.

Tasks

Preview Give feedback

1. [Tracking]: E2E test #2410
   4 of 4
   team +1
   
2. [Tracking issue]: Refactor ./x using zx and npm scripts #2581
   feat p1-important team +3
   
3. [Tracking Issue] Build infra #2472
   12 of 12
   team tracking issue +2
   
4. [Tracking issue] Test infra #2485
   7 of 16
   team tracking issue +2
5. [Feature Request]: HMR E2E environment #2413
   team +1
   
6. Overall webpack test samples Migration #2496
   6 of 6
   team +1
   
7. nightly release #2484
   p1-important team +2
   

Website

Tasks

Preview Give feedback

1. [Tracking issue] improve migration guide rspack-website#257
   3 of 3
   +0
   

Milestones

The iteration plan for tri-month divides into multiple milestones.

Release 0.2.0

Date	Event
April 6th	Rspack 0.2.0 Roadmap Release
May 16th	Rspack 0.2.0 Release

Features

Tasks

Preview Give feedback

1. [Tracking issue] vue support #2350
   4 of 4
   team tracking issue +2
   
2. [Tracking issue]: Progressive inline-loader-syntax support #1749
   p1-important team tracking issue +3
   
3. [Feature Request]: pitching loader support #2394
   p1-important team +2
   

[ityuany]

Can snapshots be continuously released, for example:

I noticed that inline-loader has already been merged, and I want to try it out directly, but there is no version available for me to try.

[hardfist]

Can snapshots be continuously released, for example:

I noticed that inline-loader has already been merged, and I want to try it out directly, but there is no version available for me to try.

you can always use nightly version to test nightly build, just try @rspack/cli@nightly

[ityuany]

Is there an rspack feedback group?

[hardfist]

Is there an rspack feedback group?

you can give feedback on dicsord channel or join chinese lark group

[zackarychapple]

@hardfist should we add the second Angular tracking issue to this list?