@Albert Margarit (NS Eng Lead) 1. Test Framework (priorty #1 IMO) - Being able to easily mock any module for example. Sometimes you just can't separate (easily) your business logic from netsuite code which makes it difficult to test without a little mocking magic w/ the existing N/x libraries from the file cabinet source code for 2.0. I don't much care if there's a way to mock an event as we shouldn't be testing whether or not the afterSubmit/beforeSubmit etc... is firing as thats on netsuite but rather the business logic side of things. This is a MUCHHHHHHH larger conversation than just a few sentences. 2. JSDoc and documentation - valid JSDoc so that it can be used for offline documentation such as Dash (mac) / Zeal (pc) (or any other flavor) and auto complete 3. WebStorm (you can also make the plugin available for other IDEs via the plugin.xml properties which I would highly suggest since some people use other IDEs within the jetbrains family like PhpStorm for commerce/suitetalk. This doesn't require any extra work/testing as it should work in any of them) 4. Node - This is a JS development so why not have JS tools. For instance why install maven and all of the Java stuff for CLI when it can be done via NodeJS? 5. Continuous Integration - Pretty self explanatory here but would like to see support for integrating with the major git sites like github/bitbucket/gitlab etc...