Because of a underlying 3rd party calendar component update the builds of TiNG started breaking because they changed some api
We did releases of Bootstrap components (24.3.4 and 24.12.1) and NGGrid (24.3.7 and 24.12.2) to fix this,
You need to update to at least 1 of them in your 24 LTS or 12 release to fix this problem
Thanks for the fast fix!
So I understand correctly, the internal build via npm that runs from time to time / when triggerd in the project explorer via “copy Titanium NGClient sources” + selecting “copy & build” loads and builds external components, located in the workspace, which broke in this case?
Would there be a way for us to disable this if there are problems with updating and the user is stuck on a build that doesn’t get updates?
our components depend on 3rd party components in this case https://github.com/Eonasdan/tempus-dominus/releases
and our components don’t fix to hard version because if we do that then everything is hard coupled to each other if multiply components/packages where using that 3rd party component (which is the case with this one, there are dependencies in core, legacy components, bootstrap calendar but also nggrid is using this for its date celleditor)
so we have things like <6.9 or ^16 and that so on, so we allow a range of things, this is also good for security fixies, so of a 3rd party component releases a minor/micro release for a security or other fix a rebuild of TiNG will get that.
Problem is we had something like ^6.9.5 as the npm version, for npm that doesnt mean that all 6.9.x version are possible but all 6.x and we got a 6.10 version because of that and in that one they made a mistake which is now already fixed in 6.10.1 and made some api property mandatory which shouldn’t really be.
because it was marked as mandatory in an options object and we don’t provide that with that property the build broke.
This is tricky to fix if you just use the Servoy Package Manager packages… (so kind of the binary packages), this could be fixed if you use it from source (by quickly just adjusting the version to fix it to a certain version)
Problem is also if it did go wrong, the “npm update” command already did happen and you have the new version of that 3rd party package. so your workspace is already in a wrong state at that time.
Happily this doesn’t happen a lot, the few times it did break before like that was purely because of Uppy, they are constantly breaking even between there own packages, so that one is really fixed now.