Frameworks like any programming paradigm were made to systematically solve problems in a structured format. Though many different frameworks exist and they all use different structures to solve similar problems, it’s the structure that matters. That’s not to say that any structure should be valued, as with any strategy in problem solving it should be scrutinized. A framework should put through a crucible of rigorous testing to make sure it actually solves the problems it sets out to solve.
However I see a recent trend of developers crying out against frameworks as if they seem to be useless technical baggage. The irony is that technical baggage is exactly one of the issues they set out to solve. The structure of a framework does bring extra weight and initial legwork to build applications(although not really since scaffolding tools solve this for the most part). However unless the project is a static web page that needs no customization(which is a non starter in any business setting) then the framework tends to enforce structure that reduces technical debt over time.
Any developer worth his salt knows that Feature Creep is a major problem, Frameworks don’t solve that problem(only proper communication can) but they do help with extendability and scaleability. So even if a project’s current needs to do not merit a framework, if the project has any long term goals the chances that it will eventually are exponentially high the longer the project’s life goes on. Trust me, you don’t want to find out 4 years into a project that the entire project needs to be redone in a framework and sometimes a different language if you levy Typescript.
I don’t want to come off as saying Frameworks solve all of your problems, because they sure as heck do not. But I do think that any serious web project would be silly not to leverage the tools, scaleability and functionality that Frameworks offer in the modern development world.