Switch razzle development to typescript

Description

Contributor guide

Tech stack

typescriptjavascript

Domain

toolingdeveloper experiencebuild system

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.

mostly clear

Prerequisites

Familiarity with Razzle codebaseTypeScript knowledgeNode.js development experience

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20

Research direction

The issue requests switching the development of Razzle to TypeScript. The linked directory (https://github.com/jaredpalmer/razzle/tree/alpha/packages/razzle5) contains the current codebase. The discussion in the issue likely covers migration strategy. First, assess the current JavaScript files and their dependencies. Then, propose a plan to convert core files to TypeScript, ensuring type safety without breaking existing functionality. Look for any previous attempts or maintainer guidance in the comments. Given the age of the issue, it may need revival with a detailed proposal.