Transition from JavaScript to TypeScript for improved maintainability
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Topic
Introduce TypeSafety, Lint Checking for Organisation.
I saw that some of code was in typescript, since typescript provide compile time type checking, more strictness, command over the project, hence I propose under GSoC 2025 a project:
migrate the codebase to TypeScript
Advantages:
- Explicit Typing, Support for OOPs
- Makes more enhanced development since has so many features which JavaScript lacks
Also had one more idea,
Basically processing is a large codebase with vast community, so for different people contributing there should be a common way to start the application locally, hence I suggest to containerise the application via Docker.
Again looking forward for more input & feedback
@ksen0 @limzykenneth @lmccart @Qianqianye @outofambit @mcturner1995
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the p5.js codebase and clarifying whether TypeScript migration, lint checking, Docker containerization, or all three are in scope; done would require an agreed scope and completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, typescript
- Domain
- build-system, frontend, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100