Great discussion you were having here about the CLI and WebStorm use cases 👏 Answering to @darrenhillconsulting @stalbert @alien4u @creece and other people in the conversation: • There are no intention at the moment to create a hard dependency between WebStorm and the CLI mainly because of the nature of the type of users that each tool is target to, but regardless of that, we do are aligning the experiences and standardizing processes, so is probable that in a near future you will find some behaviors that are available nowadays in the CLI for Node.js, implemented as part of the WebStorm Plugin (For example: Project Structure or the authentication system) • Our main focus is to provide and richful experience to improve the developer efficiency while customizing their projects, and this goes beyond the IDE or the CLI, to achieve this what we really want to do first is to align and standardize processes, so regardless of your "editor", you can benefit from the upcoming additions. There are many things going on, and I am always available to hear your needs so if you want to share your use cases or ideal setups, please reach me to build the right things. For example, you can start a threat here and answer: 1- What are the best practices that you have nowadays? 2- What is missing from our side that will make your life easier? 3- What do you think about the experience for the SuiteCloud CLI for Node.js Please, do not share information that could be sensitive (names, company, contract or anything personal), I would love to have interviews with all of you, but now we need to fill a process before moving into a formal meeting (NDA and some Legal paperwork that can be done with whoever is interested)