Notes on/for v3 / v4
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript, typescript
- Domain
- build-system, ci-cd, documentation, tooling
Research direction
This issue is a broad v3/v4 planning list and names no implementation files, tests, or entry points. Start by reviewing the repository structure and splitting one proposed change into a separate, scoped issue; there is no single completion criterion defined here.
Written by the indexing model from the issue text.
Description
workspaces/
- formidable
- formidable-plugins?
- formidable-helpers
- formidable-mini - an experimental minimal & modern idea
- formidable-utils
- formidable-storage
- memory (VolatileFile)
- disk (PersistentFile)
- serverless (formidable-serverless)
misc
- minimize dep weight
- monorepo
(turborepo /nx.dev + lerna ^5.1 + yarn workspaces)- Hela v6 - written in typescript, drop / deprecated external packages
- kodiak - merge automation & better PRs and commits (https://kodiakhq.com/)
- Dependabot, make it auto-update and auto-merge all versions and branches (latest-2, latest, latest-3, next-2, next-3)
- GitHub CodeQL action
- go async/await and promises; possibly drop callback APIs entirely
- document Release Process, Lines, and dist-tags & branches
- latest-1, latest-2, next-2, latest-3, latest-4, next-4);
latestas master
- better / real benchmarks
- analyze old tests & rethink and probably drop them
- some benchmarks here at busboy v1 - https://github.com/mscdex/busboy/issues/266
- standard Web API
File
- Dominant language
- JavaScript
- Stars
- 7.2k
- Forks
- 689
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
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.
More from node-formidable/formidable
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
node-formidable/formidable#1120 ·
-
Priority: Medium Type: Maintenance
Difficulty 3/5 1-2 days Newbie friendliness 48/100
node-formidable/formidable#1098 · 2 comments ·
-
Area: streams bug Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
node-formidable/formidable#1092 · 5 comments ·
-
Status: Accepted Type: Documentation Type: Enhancement Type: Question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
node-formidable/formidable#1029 · 11 comments ·
-
Area: streams bug Status: Accepted Type: Bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
node-formidable/formidable#1011 · 8 comments ·
All issues in node-formidable/formidable
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100