JavaScript is disabled for your browser. Some features of this site may not work without it.
| dc.contributor.author | OBJELEAN, Alexandru | |
| dc.date.accessioned | 2019-11-08T07:25:47Z | |
| dc.date.available | 2019-11-08T07:25:47Z | |
| dc.date.issued | 2011 | |
| dc.identifier.citation | OBJELEAN, Alexandru. Build-Time Javascript Code Analysis. In: Microelectronics and Computer Science: proc. of the 7th intern. Conf., September 22-24, 2011. Chişinău, 2011, vol. 1, pp. 218-220. ISBN 978-9975-45-174-1. | en_US |
| dc.identifier.isbn | 978-9975-45-174-1 | |
| dc.identifier.uri | http://repository.utm.md/handle/5014/6384 | |
| dc.description.abstract | Javascript can be tough to maintain. The bigger is your project, the harder it will be to ensure that everything is ok. Luckily, there are tools to help you with that. One of the recently launched tools is JSHint, a online JavaScript checking tool. The tool is very similar to JSLint, but is designed to be more customizable and community-oriented. JSHint can help you to detect errors and potential problems in JavaScript code and to enforce your team's coding conventions. It is very flexible so you can easily adjust it to your particular coding guidelines and the environment you expect your code to execute in. The purpose of this article is to show you how to use jsHint as a build-time solution using wro4j maven plugin. | en_US |
| dc.language.iso | en | en_US |
| dc.publisher | Technical University of Moldova | en_US |
| dc.rights | Attribution-NonCommercial-NoDerivs 3.0 United States | * |
| dc.rights.uri | http://creativecommons.org/licenses/by-nc-nd/3.0/us/ | * |
| dc.subject | Javascript | en_US |
| dc.title | Build-Time Javascript Code Analysis | en_US |
| dc.type | Article | en_US |
Files in this item
The following license files are associated with this item:
This item appears in the following Collection(s)
Except where otherwise noted, this item's license is described as Attribution-NonCommercial-NoDerivs 3.0 United States