Visual Studio Code together with the UI5 Tooling. But IMO it should be seamlessly possible to either develop a UI5 application in SAP Web IDE and locally in e.g. Keep in mind, the SAP Web IDE still provides a lot of value and benefits with its wizards, tools and integration into various SAP platforms.
Every UI5 developer should make this experience to feel how good local UI5 development can be already today. Now, let’s start with some hands-on and let’s make our hands dirty. All those features can be combined and used for UI5 development to come to a modern development experience! A real-life example: Local UI5 development with the UI5 Tooling transpile ES6 to ES5 code by using Babel or to provide custom middlewares to get a livereload of the browser in case of changes in the project sources as well as a simple HTTP proxy to tunnel backend services. So, the repository step by step grow to integrate custom tasks to e.g. The extensibility concept of the UI5 Tooling allows to integrate those tools easily. The UI5 Ecosystem Showcase repository contains several ideas to improve the UI5 development experience by leveraging open-source tools. This was the kick-start for the UI5 Ecosystem Showcase repository – a repository to demonstrate how easy the UI5 Tooling can be enhanced with own custom tasks and middlewares. But I offered Volker to help him to write a proxy and to get started with the extensibility of the UI5 Tooling demonstrating the task and middleware extensibility. I asked Volker what kind of proxy he needs: a simple proxy, an AppRouter, a HTML5 runtime router, …? All proxies are somehow specific to their platform, coming with different configurations and IMO the UI5 Tooling team will never satisfy all demands. Last year, at the UI5con at SAP, Volker Buzek approached me and asked for a proxy as part of the UI5 Tooling. But without using mockdata, such a proxy is needed. Compared to the HTML5 runtime, the UI5 Tooling just provides access to the UI5 resources and doesn’t provide a proxy to access backend services. But when grabbing projects from SAP Web IDE and running them locally, the development server is mandatory. As the SAP Web IDE comes with an integrated preview based on the HTML5 runtime, the development server of the UI5 Tooling is not required here. Today, all UI5 projects created with the SAP Web IDE include the proper configuration to use the UI5 Tooling for the build process. BackgroundĪpproximately one year ago, the SAP Web IDE switched to use the UI5 Tooling to build UI5 projects. This blog explains the individual steps to you to make the same experience.
Unable to start livereload serve how to#
Besides explaining the UI5 Tooling in general, I showed how to grab a UI5 application from SAP Web IDE and how to configure it to run it locally with the UI5 Tooling. On April 1 st I talked about the “ UI5 Tooling – a modern CLI-based development experience” in a SAP Community call.
0 kommentar(er)
