Your learning plan sounds waaay frontend heavy.

My advice would be to be more balanced, if you are really aiming for full stack, and not just be like: "I do frontend, but want to use my frontend tech for backend purposes.".

If someone tells me they are a fullstack dev, I would expect the following, in order starting from frontend to backend, not because of priority:

(1) The frontend basics: HTML, CSS, JS, TS. All in modern versions, and knowing how to use actual web standards, which doesn't mean just using whatever the latest version of Google Chrome supports. The skill to choose good representations of information on web pages, that work across various browsers and don't limit accessibility. Being able to produce websites, that are not just a whitescreen, when I visit them without having JS enabled.

(2) A frontend web framework. For example Vue.

(3) A backend web framework, that does not run on frontend only tech. There are places, where frontend shenanigans are not accepted in the backend and many more places, where they would be accepted, but their dependency trees are extremely overkill for what is needed. That means a backend web framework and a backend programming language. Many choices there. Mainstream ones: Go, Python, Ruby, Java. Probably forgot to list some. Not so mainstream ones: Other languages on the JVM, Rust, Elixir. Probably forgot to list some. Many exotic ones there. Each has their go-to (micro) web frameworks.

(4) Knowing a backend programming language well, being able to use it fluently, just as fluently as you use JS/TS.

(5) Knowing how to use a database. SQL the language of course, but no need to know everything, if you can work by looking things up that you need to know. Better Postgres, not so great MySQL or MariaDB, worse MS SQL shit. MongoDB is meh, very situational, often not what you would actually want, unless you must have document storage in the database. Firebase is also very situational. Can you set up a Firebase on your own server, or are you relying on Google hosting?

(6) All the other typical backend things like: Containerization, being able to create container images that are useful and flexible. Understanding mounts and such things that come with containerization. Educated management of dependencies with reproducibility in mind. Probably shell scripting skills. An understanding of at least roughly how GNU/Linux distros work, the usual command line tools and system tools like cronjobs, rsync, ssh, and so on. You feel at home on the command line.

"Fullstack Dev" is deeper than most people, who label themselves as such. It has become a buzzword in HR job ads, but they don't know what the word means.

Truly being a fullstack developer means having a very broad set of skills and knowledge. Few "fullstack" engineers are truly fullstack. Most who call themselves that these days are nothing more than frontend devs, who know 1 frontend web framework, and think that their NodeJs or NPM stuff is gonna fly on the backend too. Well, for some companies it might. They put "fullstack" on their CV to increase their ability to be hired, but it doesn't really reflect their skill. They are "fullstack devs" but limited to frontend tech.