![]() And that`s what finally inspired me to this idea to make it possible to just include an npm package with close to zero configuration in my UI5 application by just using the npm package as a runtime dependency via sap.ui.define or import statements. The project shims are nice but especially combined with TypeScript I don’t get the code completion support for these npm packages. Vivek Chandregowda explained this is a nice blog roughly a year back: “ Project Shims – Using NPM modules with UI5”. There is already a solution for UI5 applications using the UI5 Tooling to use project shims. There you will get some more background information and can start to make your fingers dirty with TypeScript development for UI5.īut there was always one aspect missing for me so far: I want to directly consume node packages directly in my UI5 application similar like it is possible for other UI frameworks. You can check it out by yourself by following the blog post “ Getting Started with TypeScript for UI5 Application Development”. Additionally, modern IDEs will provide you a lot of support out of the box, e.g., code completion, type checks and more. You can now use ES modules and ES classes to write your UI5 applications. Together with the frontend package manager, all OpenUI5 and SAPUI5 UI libraries have been published to the public npm registry for general availability.įinally, the TypeScript enablement of OpenUI5 and SAPUI5 enables us having a modern development experience for UI5 development. The UI5 version defines in which version the UI libraries are included. But for frontend packages you need to ensure to have only one version per dependency available and even more the dependencies need to be in sync with each other as we want to depend on a specific UI5 version which consists of several UI libraries available as individual npm packages. The node package manager doesn’t do negotiation of dependencies which can lead to inconsistencies. This version introduced a custom package manager which can handle the UI5 frontend packages properly. The ecosystem is the foundation and provided the examples how custom extensions can be developed and shared.Īnother big milestone was UI5 Tooling V2. This was the starting signal of the UI5 Tooling ecosystem. Being now open and extensible allows everyone to create custom tasks and custom middlewares for their special needs and it also avoids the UI5 Tooling team to be the bottleneck to implement new features. Let’s first take a look back into the evolution of the UI5 Tooling and its important milestones over the last couple of month and years to get to a modern, open and extensible development experience:Ī very important milestone of the UI5 Tooling evolution was extensibility. With the UI5 Tooling it is easily possible to create, develop, test and build UI5 projects with a Node.js based tooling. The UI5 Tooling and its ecosystem together are the key pillars of a modern development experience for UI5 applications and libraries.
0 Comments
Leave a Reply. |