Totally agree with Dan that the order you learn things doesn't really matter, it depends on how you prefer learning (sometimes referred to as "top to bottom" vs "bottom to top")
What's important, crucial even, is that you don't lock you into a single framework and explore whether some things could be done "by the platform" rather than through the framework (or using HTML and/or CSS vs just JS: there was a time, before flexbox and grid, where complex positioning required JS computations, this is no longer true in most cases; don't fall into that trap, because CSS will be much more performant, efficient, and a portable knowledge: works with any framework!)
As soon as you're quite comfortable with JS or a specific JS framework, explore (if/when you have time) whether it wouldn't be better if done by other means.
Totally agree with Dan that the order you learn things doesn't really matter, it depends on how you prefer learning (sometimes referred to as "top to bottom" vs "bottom to top")
What's important, crucial even, is that you don't lock you into a single framework and explore whether some things could be done "by the platform" rather than through the framework (or using HTML and/or CSS vs just JS: there was a time, before flexbox and grid, where complex positioning required JS computations, this is no longer true in most cases; don't fall into that trap, because CSS will be much more performant, efficient, and a portable knowledge: works with any framework!)
As soon as you're quite comfortable with JS or a specific JS framework, explore (if/when you have time) whether it wouldn't be better if done by other means.
Totally agree with your points.