Standard

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

32nd IEEE/ACM International Conference on Automated Software Engineering. IEEE Computer Society, 2017. p. 578-589.

Research output: Scientific - peer-reviewConference contribution

Harvard

Fjóla Tómasdóttir, K, Finavaro Aniche, M & van Deursen, A 2017, Why and How JavaScript Developers Use Linters. in 32nd IEEE/ACM International Conference on Automated Software Engineering. IEEE Computer Society, pp. 578-589.

APA

Fjóla Tómasdóttir, K., Finavaro Aniche, M., & van Deursen, A. (2017). Why and How JavaScript Developers Use Linters. In 32nd IEEE/ACM International Conference on Automated Software Engineering. (pp. 578-589). IEEE Computer Society.

Vancouver

Fjóla Tómasdóttir K, Finavaro Aniche M, van Deursen A. Why and How JavaScript Developers Use Linters. In 32nd IEEE/ACM International Conference on Automated Software Engineering. IEEE Computer Society. 2017. p. 578-589.

Author

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

32nd IEEE/ACM International Conference on Automated Software Engineering. IEEE Computer Society, 2017. p. 578-589.

Research output: Scientific - peer-reviewConference contribution

BibTeX

@inbook{afb408b43b634e499ce77040e3a624b4,
title = "Why and How JavaScript Developers Use Linters",
keywords = "linters, software maintenance, ASATs, static analysis tools",
author = "{Fjóla Tómasdóttir}, Kristín and {Finavaro Aniche}, Mauricio and {van Deursen}, Arie",
year = "2017",
pages = "578--589",
booktitle = "32nd IEEE/ACM International Conference on Automated Software Engineering",
publisher = "IEEE Computer Society",
address = "United States",

}

RIS

TY - CHAP

T1 - Why and How JavaScript Developers Use Linters

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

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

M3 - Conference contribution

SP - 578

EP - 589

BT - 32nd IEEE/ACM International Conference on Automated Software Engineering

PB - IEEE Computer Society

ER -

ID: 26024520