Merlin Beutlberger

Hey @Bomberus, I double checked the changes we released with the `v1.13.1` patch. However I couldn't find an indication that it might cause this issue. Just from looking at the...

> Never the less, I removed the node_modules folder and installed everything again. Did this resolve your issue? > So I guess @ui5/project is importing the older server version? Based...

Stale

Thank you for your input Mike! That part of the roadmap was slightly outdated, so I updated it with our latest decisions: > - [x] Drop support for **Node.js Version...

We are currently in the process of publishing a first **Release Candidate** for UI5 Tooling v3. As of the latest discussions, we stick to a minimum Node.js requirement of version...

Thanks for sharing your experience @nhebling! If you don't mind, it would help us understanding your scenario better if you could roughly describe your setup. What kind of third-party npm...

This roadmap is very much outdated. I'll close this with reference to https://github.com/SAP/ui5-tooling/issues/701 We'll check the list here again and take over any topics that are still relevant.

> 1. There are many things that can be done about sap.ui.core.js. For example, a large number of text comments and line breaks can be removed, which can be packaged...

Hey @BenReim, sorry for the delay. We just had another look at this issue and found that there is a mismatch in the component names that prevents this from working...

Hey @mauriciolauffer, thanks for providing your input! From my understanding there is already a wide use for custom tasks implementing deployment functionality. Most prominently through the Fiori Tools `deploy-to-abap` task...