Improve n8n build time

um can i share my screen very quickly is it showing up okay i'm gonna take that as a yes um so what did we come up with um oliver and i had this idea of trying to improve the build speed time for the entire project because as you know it kind of like usually like set an identity build and go make yourself some coffee and then come back and it's still building and it kind of like takes a bit of a while um and so we try to go about this and basically try to go through every component and try to make it faster our main goal of all this like the big idea was build speed um but there are sort of like percent the different packages country with different percentages uh of the build time to the totals um so what we did was focusing on the two biggest like um guilty parts of this which were basically the node space package which that you know it's gigantic like you can do a visualization of this and it's very big and then the editor ui which for some reason like this combination of view on webpack and so on and compiling sas uh also takes a while so if you want numbers um i did this and so we discovered with this that learner is a liar because if you build with learner you check the total time and then you pick out the different like times that it takes for the different packages to build the numbers don't add up which is interesting yes like literally they're completely wrong we run it many times with different systems so there are two totals but the actual total for an m1 machine is this one so 146 seconds um and from this i don't know what else to mention here uh we decided to go basically to focus on node space and edit your ui we had es build which i don't know if you guys know it but it's kind of like a go line compiler for typed into javascript so it's much faster than using javascript to compile javascript like way faster um and then we thought about for example there's this turbo repo um like more modern alternative to learner where you can for example with learner you do like you have many packages you run every command for every package one after the other as you know in the pipeline but with turbo reboot which was recently acquired by versailles what you can do is basically collapse all the waterfalls um by using um sort of by allowing it to analyze sort of the dependencies that are there and to use many threads so that as you can see here for example we can lend test lint tests instead of um going one by one um and so what we did was first in the es belt case as you know um as i was saying it was let me just give you the number but it took no space 40 seconds right with es build let me just move you guys out of the way with es build you run it and it takes 580 milliseconds again 466 milliseconds uh 124 milliseconds so if you do some calculation you could say that we're like 40 000 milliseconds minus what 400 milliseconds divided by 40 000 we're seeing a bit of a reduction of 99 in the build time for node space which is a good start i think um then what we can do is just keep going with all the other sort of parts of the project because i mean this is just this is half of it right um and i was thinking maybe it would make sense for oliver to explain what he's been doing with the editor ui he's been making a lot of progress but you have to remember this is kind of like a an experiment so let me stop sharing so that oliver can take over yep uh s7 previous described the main goal was to speed up the process and to reduce the time for developer and when developers build uh the projects so basically i was working on the editor with packages basically and i think we are near nineteen percent uh done with speeding up the process the main goal is even described the main goal was reducing the time and i was using this sl build library instead of view cli because in well when i tested also on the standalone project it reduced the building time for nearly 90 percent and it will be

uh really cool stuff for developers basically the main problem that i faced here was the compiling the sas variables and uh as i researched a little bit i will give you overview how was done previous so basically oh there was just a second so basically uh the view cli the end of the pack there are some options to prepend data or to import variables that we are using through every few components in the editorial packages basically it is our application and with the asset wheel it's a built package that will reduce the time for compiling every files there's a little problem with it so i am trying uh together with you and uh in the last couple or one or two hours we were trying to figure out what is the problem and uh how we will solve this patient and we come out with some solution that we will continue to implement it so basically it shows only error or you can see only we uh the compiler could not uh see the could not compile the variables that comes from the team so basically that is but i'm pretty sure that uh in the next hour we will find proper solution for it and we we will use it for the future purpose so everyone that is working on the application as developer will be happy that will save a lot of time during typing always simply around defaults or builds