jaredpalmer/razzle

Split razzle core into razzle-webpack4 and razzle-webpack5

Open

#1641 opened on Jun 28, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (11,091 stars) (963 forks)batch import
breaking changehelp wantedrazzlewebpack

Description

Also do the same for plugins requiring a specific webpack

Contributor guide

Tech stack
javascriptnodejs
Domain
build systemtooling
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
JavaScriptRazzle frameworkWebpack configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Research the current Razzle core structure and identify how plugins interact with webpack. Look for examples of similar splits in other projects (e.g., create react app's webpack version separation). Check the Razzle issue tracker for any previous discussions. Given the lack of details, it is recommended to open a discussion or comment on the issue to clarify the expected architecture and scope.