jussi-kalliokoski/trine

Consider releasing as multiple separate modules

Open

#47 opened on Jul 20, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,417 stars) (45 forks)batch import
enhancementhelp wanted

Description

I used to think of the trine/boolean/and way of distributing modules as bullseye. Super simple, built into the language.

But I’ve recently had a very interesting conversation which led me to change my mind: https://github.com/mattdesl/module-best-practices/pull/2. The gist of it is “this breaks things”. It might convince you as well.

Contributor guide

Tech stack
javascript
Domain
releasedeveloper experience
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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.
clear
Prerequisites
Understanding of JavaScript module distribution
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review the linked PR #2 in the module best practices repo to understand the arguments against single module distribution. Then examine the current trine module structure and consider how to split it into separate npm packages. The issue body and any discussion comments may provide additional context. No specific files in trine are referenced.