Moving from Bower to npm
Check out the official OpenUI5 demo apps for examples that already make use of the new npm packages. Also various community projects surrounding the UI5Lab are currently working on or have already transitioned from Bower to npm. For example @StErMi‘s openui5-qrcode.
Therefore we have decided to discontinue Bower releases for UI5 1.60 and beyond.
All lower releases will still receive patches for as long as they are in maintenance (see OpenUI5 Versions Maintenance Status).
Migrating to npm
The npm packages differ from the Bower packages in terms of directory structure and content. This is mainly motivated by being able to provide a better integration with both, npm and the UI5 Build and Development Tooling.
The Bower packages had been aligned with the OpenUI5 download package. While the npm packages are in the same structure as the OpenUI5 sources on GitHub. This means that you can easily link your dependencies locally, which drastically improves the development experience when working across multiple projects.
Another important change is that there are no pre-built files like
library.css or an optimized version of the
That’s because with the UI5 Build and Development Tooling there are now several options for building and optimizing UI5 sources along with your application. In many cases, the pre-built files might not even be required.
test-directories (representing their
"test-resources") are also not included. They are not required for most UI5 projects and would increase package size by up to 80%.
- Documentation: Working with the UI5 Build and Development Tooling
- How-to: OpenUI5 sample app using the UI5 Build and Development Tooling
- FAQ: UI5 Build and Development Tooling