An Exploration of npm Package Co-Usage Examples from Stack Overflow: A Case Study
- 1 January 2022
- journal article
- research article
- Published by Institute of Electronics, Information and Communications Engineers (IEICE) in IEICE Transactions on Information and Systems
- Vol. E105.D (1), 11-18
- https://doi.org/10.1587/transinf.2021mpp0003
Abstract
Third-party package usage has become a common practice in contemporary software development. Developers often face different challenges, including choosing the right libraries, installing errors, discrepancies, setting up the environment, and building failures during software development. The risks of maintaining a third-party package are well known, but it is unclear how information from Stack Overflow (SO) can be useful. This paper performed an empirical study to explore npm package co-usage examples from SO. From over 30,000 SO question posts, we extracted 2,100 posts with package usage information and matched them against the 217,934 npm library package. We find that, popular and highly used libraries are not discussed as often in SO. However, we can see that the accepted answers may prove useful, as we believe that the usage examples and executable commands could be reused for tool support.Keywords
This publication has 26 references indexed in Scilit:
- Semantic versioning and impact of breaking changes in the Maven repositoryJournal of Systems and Software, 2017
- Do developers update their library dependencies?Empirical Software Engineering, 2017
- Historical and impact analysis of API breaking changes: A large-scale studyPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2017
- Search-based software library recommendation using multi-objective optimizationInformation and Software Technology, 2017
- Why do we break APIs? First answers from developersPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2017
- How to break an API: cost negotiation and community values in three software ecosystemsPublished by Association for Computing Machinery (ACM) ,2016
- SimilarTech: automatically recommend analogical libraries across different programming languagesPublished by Association for Computing Machinery (ACM) ,2016
- Augmenting API documentation with insights from stack overflowPublished by Association for Computing Machinery (ACM) ,2016
- How the Apache community upgrades dependencies: an evolutionary studyEmpirical Software Engineering, 2014
- Automated library recommendationPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2013