[NPMCLI-64] Merge npm-build-tools with magnolia-cli package Created: 17/Jan/17  Updated: 24/Jan/17

Status: Open
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Robert Kowalski Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Story Points: 2

 Description   

What do you think of unifying `npm-build-tools`?

Are there any other modules depending on it?

The problem I see with them separated is the overhead it creates when you release a new version, so there is a good amount of publishing overhead involved, and some cognitive load as a part of the code is in another module.

Maybe I missed it, is there a specific use case for `npm-build-tools` as a standalone?

If not I think merging both packages could make development easier in the future.


Generated at Mon Feb 12 04:46:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.