Sounds like a lot more of 2018 to me.
IMHO 2019 is the year of Web Components, as Microsoft Edge will be the last evergreen browser to adopt the Custom Elements v1 spec. Web Components largely make UI libraries based on component patterns obsolete, with the exception of how libraries like React make components stateful of course.
Why should a team in 2019 considering how to build UI components use React when a huge chunk of the API for developing a component is baked into the browser with Custom Elements v1? I recently built a micro library that makes Web Components stateful and the entire library bundles down to under 2.3Kb minified.
Because I can do SSR with React. Single codebase for both backend and frontend.
My use of React is because of two things:
How do Web Components support these patterns ?
But to answer your questions, Custom Elements still have lifecycle hooks and well fetch API is available in evergreen browsers.
How do you import your library into your web component? By leveraging webpack?
"one recruiter I recently spoke to React only accounts for 7% of job requests flowing through their agency."
Tech stacks can cluster around particular hubs in different cities and countries. I'm in a MERN stack hub here, but in other places you might look at the local market and realise it's all LAMP or the front-end is vanilla JS and jQuery. Had a company present at my bootcamp who used Backbone with no plans to migrate away.
Trends change from place to place.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.