Standard

Why and How JavaScript Developers Use Linters. / Tómasdóttir, Kristín Fjóla; Finavaro Aniche, Mauricio; van Deursen, Arie.

Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17. ed. / Grigore Rosu; Massimiliano Di Penta; Tien N. Nguyen. IEEE Computer Society, 2017. p. 578-589.

Research output: Scientific - peer-reviewConference contribution

Harvard

Tómasdóttir, KF, Finavaro Aniche, M & van Deursen, A 2017, Why and How JavaScript Developers Use Linters. in G Rosu, M Di Penta & TN Nguyen (eds), Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17. IEEE Computer Society, pp. 578-589, ASE 2017, Urbana-Champaign, IL, United States, 30/10/17. DOI: 10.1109/ASE.2017.8115668

APA

Tómasdóttir, K. F., Finavaro Aniche, M., & van Deursen, A. (2017). Why and How JavaScript Developers Use Linters. In G. Rosu, M. Di Penta, & T. N. Nguyen (Eds.), Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17 (pp. 578-589). IEEE Computer Society. DOI: 10.1109/ASE.2017.8115668

Vancouver

Tómasdóttir KF, Finavaro Aniche M, van Deursen A. Why and How JavaScript Developers Use Linters. In Rosu G, Di Penta M, Nguyen TN, editors, Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17. IEEE Computer Society. 2017. p. 578-589. Available from, DOI: 10.1109/ASE.2017.8115668

Author

Tómasdóttir, Kristín Fjóla ; Finavaro Aniche, Mauricio ; van Deursen, Arie. / Why and How JavaScript Developers Use Linters. Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17. editor / Grigore Rosu ; Massimiliano Di Penta ; Tien N. Nguyen. IEEE Computer Society, 2017. pp. 578-589

BibTeX

@inbook{afb408b43b634e499ce77040e3a624b4,
title = "Why and How JavaScript Developers Use Linters",
abstract = "Automatic static analysis tools help developers to automatically spot code issues in their software. They can be of extreme value in languages with dynamic characteristics, such as JavaScript, where developers can easily introduce mistakes which can go unnoticed for a long time, e.g., a simple syntactic or spelling mistake. Although research has already shown how developers perceive such tools for strongly-typed languages such as Java, little is known about their perceptions when it comes to dynamic languages. In this paper, we investigate what motivates and how developers make use of such tools in JavaScript projects. To that goal, we apply a qualitative research method to conduct and analyze a series of 15 interviews with developers responsible for the linter configuration in reputable OSS JavaScript projects that apply the most commonly used linter, ESLint. The results describe the benefits that developers obtain when using ESLint, the different ways one can configure the tool and prioritize its rules, and the existing challenges in applying linters in the real world. These results have direct implications for developers, tool makers, and researchers, such as tool improvements, and a research agenda that aims to increase our knowledge about the usefulness of such analyzers.",
keywords = "linters, software maintenance, ASATs, static analysis tools",
author = "Tómasdóttir, {Kristín Fjóla} and {Finavaro Aniche}, Mauricio and {van Deursen}, Arie",
year = "2017",
doi = "10.1109/ASE.2017.8115668",
pages = "578--589",
editor = "Grigore Rosu and {Di Penta}, {Massimiliano } and Nguyen, {Tien N.}",
booktitle = "Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17",
publisher = "IEEE Computer Society",
address = "United States",

}

RIS

TY - CHAP

T1 - Why and How JavaScript Developers Use Linters

AU - Tómasdóttir,Kristín Fjóla

AU - Finavaro Aniche,Mauricio

AU - van Deursen,Arie

PY - 2017

Y1 - 2017

N2 - Automatic static analysis tools help developers to automatically spot code issues in their software. They can be of extreme value in languages with dynamic characteristics, such as JavaScript, where developers can easily introduce mistakes which can go unnoticed for a long time, e.g., a simple syntactic or spelling mistake. Although research has already shown how developers perceive such tools for strongly-typed languages such as Java, little is known about their perceptions when it comes to dynamic languages. In this paper, we investigate what motivates and how developers make use of such tools in JavaScript projects. To that goal, we apply a qualitative research method to conduct and analyze a series of 15 interviews with developers responsible for the linter configuration in reputable OSS JavaScript projects that apply the most commonly used linter, ESLint. The results describe the benefits that developers obtain when using ESLint, the different ways one can configure the tool and prioritize its rules, and the existing challenges in applying linters in the real world. These results have direct implications for developers, tool makers, and researchers, such as tool improvements, and a research agenda that aims to increase our knowledge about the usefulness of such analyzers.

AB - Automatic static analysis tools help developers to automatically spot code issues in their software. They can be of extreme value in languages with dynamic characteristics, such as JavaScript, where developers can easily introduce mistakes which can go unnoticed for a long time, e.g., a simple syntactic or spelling mistake. Although research has already shown how developers perceive such tools for strongly-typed languages such as Java, little is known about their perceptions when it comes to dynamic languages. In this paper, we investigate what motivates and how developers make use of such tools in JavaScript projects. To that goal, we apply a qualitative research method to conduct and analyze a series of 15 interviews with developers responsible for the linter configuration in reputable OSS JavaScript projects that apply the most commonly used linter, ESLint. The results describe the benefits that developers obtain when using ESLint, the different ways one can configure the tool and prioritize its rules, and the existing challenges in applying linters in the real world. These results have direct implications for developers, tool makers, and researchers, such as tool improvements, and a research agenda that aims to increase our knowledge about the usefulness of such analyzers.

KW - linters

KW - software maintenance

KW - ASATs

KW - static analysis tools

UR - http://resolver.tudelft.nl/uuid:afb408b4-3b63-4e49-9ce7-7040e3a624b4

U2 - 10.1109/ASE.2017.8115668

DO - 10.1109/ASE.2017.8115668

M3 - Conference contribution

SP - 578

EP - 589

BT - Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering. ASE'17

PB - IEEE Computer Society

ER -

ID: 26024520