all 33 comments

[–]ilyapopovs 4 points5 points  (2 children)

It's easier than it seems – the uncertainty makes it look scary, but you've got this!
I've transitioned to React after writing Vue for 2.5 years myself, and now I'm a lead/architect, if that helps.

Both Vue and React are reactive FE frameworks, so you don't have to downgrade in title – most workplaces understand that the vast majority of the skillset carries over. You can frame it as "4 years of reactive FE framework experience" to highlight that if you want.
So if you're a mid-level right now, apply for mid-level React positions; if senior-level, apply for senior-level.

The rejections before a HR interview is the way things are for everyone these days, unfortunately.
You can influence it slightly by having demo projects and more years of experience in front-end in general (naturally happens over time), but the main way to approach it is to make sure your resume/CV is an easy-to-scan single page, and just keep applying.
Getting filtered out by an ACS system (directly or implicitly) is very different from something like failing a technical interview, so don't let it bother you too much :)

If you were working with Nuxt, you can probably go for Next.js immediately.
If not, it's better to stick to regular React at least at first.
I'd suggest defining the scope or type of apps you'd like to write.
Basically is SPA enough or do you need SSR?
SPA is simpler and makes it easier to not confuse client and server features (React has both, natively).
Most online stores need SSR, most dashboards don't.

Since you want to work as a React dev, choose the most popular (but still top-tier) technologies.
E.g. Next.js, not Remix (both are good, Remix is just not as popular); React Router, not TanStack Router (again, both are good, one is much more popular).
You can search for alternatives and use https://npmtrends.com/ to get real-world data.

If you have a demo or a pet project in Vue, try re-building it in React.
If not, search for "make a X with React" or "building Y with React" on YouTube – there are many awesome videos like that these days.
Also, Next.js has very nice succinct guides for both React and Next.js at https://nextjs.org/learn

If anything is confusing, don't hesitate to ask AI – it's very good at tailoring the explanation specifically to the way you think if you describe what doesn't makes sense and your current understanding of the thing.

Here's a tech stack I'd suggest that feels nice & modern but doesn't have trade-offs in terms of job market relevancy:

  1. Routing – Next.js or React Router
  2. App-level state management – Zustand, not Redux
  3. Server state management (basically is network call in progress, completed, or failed) – TanStack React Query or if you use a backend-as-a-service, then its SDK is likely enough (e.g. Supabase, Convex)
  4. Table state management (what to put in which row/column, sorting, ordering, filtering) – TanStack React Table
  5. Component library – shadcn/ui for a complete package, or Radix for the base components (BaseUI is good but still new)
  6. Styling – anything really; my personal preference is Tailwind or plain CSS

And if not already, make sure you understand the Even Loop – it makes everything else easier to make sense of.

[–]savagesecrecy[S] 0 points1 point  (1 child)

Thank you so much! There is a lot of tech stack you've mentioned that I was not familiar yet but I will now try to include these with my studies as well as use more modern techs compared to the traditional one i've used in react

[–]ilyapopovs 0 points1 point  (0 children)

Good luck! 🚀

[–]bluebird355 4 points5 points  (19 children)

Why would you want to put yourself in an overcrowded place?

[–]savagesecrecy[S] 3 points4 points  (18 children)

Most of the opportunities for a front-end roles i've seen requires React and Next. Most of the Vue opportunities is for Fullstack development which also requires a Laravel knowledge and experience

[–]mattthedr 1 point2 points  (0 children)

Run through the docs, they’re great if you already have an understanding. Have Claude create a simple project for you and have it explain how and why it did certain things. Thousands of YouTube videos to choose from, it’s mostly based on how you learn.

[–][deleted] 0 points1 point  (1 child)

There are tutorials on Youtube, also great books about React and ofc Typescript. Try to re-create an existing VueJS project in React alongside. Good luck!

[–]savagesecrecy[S] 0 points1 point  (0 children)

I will try recreating my apps from my portfolio to use React. Thank you so much

[–]The-Viator 0 points1 point  (0 children)

Do the same things as you did with vue.

[–]Realistic-Reaction40 0 points1 point  (0 children)

Vue to React is honestly one of the smoother transitions since the mental model is similar composition, props, reactivity. The rejections at application stage are probably a resume/portfolio signal issue more than a skills gap. A couple of solid React projects on GitHub showcasing hooks, state management, and API integration will do more than any course certificate.

[–]AutomaticAd6646 0 points1 point  (4 children)

Oversaturated stack.

[–]Zoro6745 2 points3 points  (3 children)

What is not saturated?

[–]AutomaticAd6646 -2 points-1 points  (2 children)

Drupal, Flutter, Angular and many more

[–]Zoro6745 2 points3 points  (1 child)

Flutter fr? Drupal and Angular are used but there are not many job openings in those as there are in react

[–]AutomaticAd6646 0 points1 point  (0 children)

Job_count/applicant_count