erming/shout

Managing client-side libraries

Open

#479 创建于 2015年9月26日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)JavaScript (3,640 star) (293 fork)batch import
enhancementhelp wanted

描述

Server-side libraries are greatly managed/manageable by npm. Among other things, we can easily track their evolution and follow security announcements (thanks to David for example), we know they come from upstream and are not tricked to our needs, ...

Not so much for client-side libraries! Furthermore, PRs such as https://github.com/erming/shout/pull/311/files (582 new lines!) and https://github.com/erming/shout/pull/337/files (841 new lines!!) ship outrageous amounts of code in our very hands. I am not familiar with them, but I know there are many package management for these, and we should be investigating a bit on that. Any experienced users there?

贡献者指南

技术栈
javascript
领域
frontendtooling
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
npm basicsclient side package managersJavaScript
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue discusses the lack of client side library management in the project. The goal is to research and propose a client side package manager (e.g., Bower, webpack) to manage libraries in the client/js/libs directory. Examine existing PRs like #311 and #337 for context. Look into the project's build system and how to integrate a package manager to automate updates.