erming/shout

Managing client-side libraries

Open

#479 opened on Sep 26, 2015

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (3,640 stars) (293 forks)batch import
enhancementhelp wanted

Description

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?

Contributor guide

Tech stack
javascript
Domain
frontendtooling
Issue type
feature
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.
1-3 hours
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
npm basicsclient side package managersJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.