If we follow that philosophy, then we would have to add to the docker image all the npm packages the community is using? So we end up with hundreds of dependencies (and the dependencies of those dependencies) that n8n it’s not using, but we think some community members might ever use in the function node?
I’m afraid I have to disagree with that. But, yes, I do not have the numbers to back up my statement. We know that adding “custom” dependencies is a pain. As I mentioned earlier, we have talked about improving this as we have talked about improving many other things. Sadly, we are a really small team and have to be very careful in what we spend our resources on if we want to create a successful company.
Maybe this is something that is prioritized in the next quarter. Who knows?