jussi-kalliokoski/trine

Consider releasing as multiple separate modules

Open

#47 创建于 2015年7月20日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)JavaScript (1,417 star) (45 fork)batch import
enhancementhelp wanted

描述

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.

贡献者指南

技术栈
javascript
领域
releasedeveloper experience
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of JavaScript module distribution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
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.