 Hello, okay, so the thing that I'm going to talk about Yeah, so yeah, that was intentional. I know what I'm doing So the so we have so how many of you use third so everybody is a JavaScript developer, so I'm I'll start with that So how many of you use third-party JavaScript libraries on your website Pretty much everyone right yeah, and how many of you have a problem at times that oh this library is creating some problem in the production and I want I want to switch it off, but How many of you have that problem? There's no way to switch it off right you it's there It's out there in the production and unless you do a production release. It's not it's there You cannot solve for it. So in my team we have come came up with a solution for that and what I call it as a plugin framework for your Website, it's it's a JavaScript framework again It's not using any backbone or angular so So it what you do essentially is the first load of your application You take out all the configurations from the from the server that you want to run any particular Plug-in or any third-party library called Let's say Google analytics or you are running a site catalyst or you're running any other analytics on your website So what you do is you load the configuration in the first load which can be cached on CDN can come from anywhere and Then you based on that all your website code is You have all your third-party plugins are safe coded inside that and when you are running in the website And you see that okay some analytics is breaking your page in the production. You can just switch the The the configuration that is coming loading in the initially you can just switch it off And what will result in that your plug-in will be is off from your website You can fix it in the next release till then your customers are not seeing that issue So you don't have to do an immediate patch release You don't have to do anything all you need to do is load that in the initial con and the configuration pretty much I have taken it from grant file.js I was inspired by a grand file.js and I have written that configuration in that way So you can write it whatever way you want to but the idea was that you have a simple config Which can tell that you want to switch it on or anything on or off and it loads in the first go and You're done. So you now don't have to do any patch releases for this So this is how we did any there's no query, right? I am writing a plug-in npm for that So I'm I want to the intention is to put it on for an npm with the plug-in name of I have not decided the name. My name is Pratik Mandela. You can follow