Intern's dependent projects (cli, digdug, leadfoot, ...) are little used (if at all) outside of Intern itself, and maintaining them separately requires a fair amount of overhead. They're also closely tied together, so it rarely makes sense to release one without updating one or more of the others. We can make Intern easier to develop and maintain by moving to a unified codebase.
The dependent projects should be integrated into the Intern repo, directly rather than as separate packages (i.e., not a monorepo). The existing projects will be flagged as deprecated, but not removed, and they may continue to see bugfixes for Intern 4. Worthwhile issues (for existing bugs and enhancements) should be moved from dependent repos to Intern's issue tracker.
jason0x43
commented
4 years ago
Intern's dependent projects (cli, digdug, leadfoot, ...) are little used (if at all) outside of Intern itself, and maintaining them separately requires a fair amount of overhead. They're also closely tied together, so it rarely makes sense to release one without updating one or more of the others. We can make Intern easier to develop and maintain by moving to a unified codebase.
The dependent projects should be integrated into the Intern repo, directly rather than as separate packages (i.e., not a monorepo). The existing projects will be flagged as deprecated, but not removed, and they may continue to see bugfixes for Intern 4. Worthwhile issues (for existing bugs and enhancements) should be moved from dependent repos to Intern's issue tracker.
This task is already in-progress -- see #998.