Would I pass a job interview for my current position?

No, absolutely not. I am a senior front-end engineer with 24 total years experience and about 15 years of full time employment in the corporate space.

I have enough experience that I can build most any kind of application that will execute in the browser. Given my level of experience I can execute pretty quickly. For my current side project I wrote a complete OS-like GUI in the browser, including file system display, in about 15 days. Its mostly WGAC 2.0 AA compliant and performs awesome even when scaling to an absurd number of GUI windows in the display.

Of course, if I approach any problem space that I have no experience with there will be some required learning time. For example I have no experience with graphics processing, so if I were tasked with rewriting Photoshop for the browser I would slow down figuring out how to write the tools specific to that class of application. If I were tasked with writing an accounting application I would have to learn how some basic accounting things work, and so forth.

Experience and competence will not get you hired writing JavaScript. In fact I will argue, as I have observed from interviewing this year, that you can be neither competent or experienced in this language/platform and be hired for an incredibly high salary, even at stable established big companies, if the other conditions are correct. I was having no trouble pitching $170k in a low cost of living area and requesting full time remote.

Hands down the most important consideration for employment writing JavaScript is appreciating the most popular tools. The most popular of them all at this time is React. To prove this visit this month's Who is hiring thread and do a CTRL+F for TypeScript. Around 90-95% of those positions require ReactJS.

https://news.ycombinator.com/item?id=29782099

Hiring aside, why would somebody with my level of experience spend any time with a large framework like that? It will dramatically slow down the performance of my applications, thanks VDOM, and inflate the size of my code by several times. It will also slow down my speed of delivery by an order of magnitude because there are addition technical concerns and more to test for. Then there are all the dependencies and additional build steps and plugins and all the other luggage that I don't want or need and that I certainly don't want to force onto my users. Worse, is that without all the nonsense the front-end is only a tiny part of any major application. Like insignificant trivially tiny compared to the rest of the application code even after accounting for accessibility, security, and cross-browser concerns. All the code swell is tech debt that increases maintenance concerns by orders of magnitude.

At this point I am already immediately disqualified from continuing employment in this field, but there are other more subtle secondary concerns resulting from tooling that add up to widen that gap.

Its interesting, because I went on a bunch of interviews, this past summer/fall. Never, in those discussions, almost never did anything knowledge related about the technologies/platforms come up in discussion, which I found very strange. There would be some knowledge questions about how the language works from a very broad level and how to asynchronously transmit data, but that's it. You would think if you were hiring a Node.js engineer there might be some Node related questions or if you were hiring for a browser related engineer there might be some browser related questions. Weird.