If developing a traditional web application that is to be accessed via the browser, the recommended approach is to deploy it to a web server and access it via http://
(or https://
) rather than file://
. Web server software is available free of charge for all operating systems.
For Windows, IIS is recommended.
On Mac OS and Linux, Apache is a popular option but any web server will do.
As a side note, a web server is not necessary when the ArcGIS API for JavaScript is used in embedded scenarios, for example Microsoft PowerBI, Windows Store app, or Adobe Creative Cloud.
JavaScript developers have a wide-range of development environment options. Some individuals prefer text editors that have many keyboard shortcuts for traversing through words, sentences, paragraphs, etc. Others are partial to more robust Integrated Development Environments (IDE) that often have many more tools related to code refactoring, syntax checking, code completion, code formatting, and source code management. Whichever editor you use, we recommend validating your code throughout your development process.
The JavaScript team maintains a collection of useful resources for developers using the ArcGIS API for JavaScript. Two popular options for inspecting your source code are JSLint and JSHint. Both are code quality tools that scan your code to identify potential issues such as missing semicolons, trailing commas, implied globals, unreachable code and more. Using a linter can save you debugging time by quickly identifying issues that are easily overlooked.
Many newer IDEs (e.g. Visual Studio Code) support syntax checking with JSHint and code hinting when providing a TypeScript definition file. The JavaScript team maintains a
Microsoft Visual Studio Code, is a free development enviroment for building Web applications.
Instructions for installing extensions, such as JSLint, for Visual Studio Code can be found here. For JSlint, review the documentation for more details.
Download WebStorm and take a tour of the Quickstart Guide.
Setup Coding style:
For more advanced Code Style formatting, visit the Web Help topic on Code Style.