These days I don't think you can get away with not knowing JavaScript, unless your thing is pretending to be a luddite, in which case you shouldn't actually be using computers if you're actually a luddite.
I've written some greasemonkey scripts for automating work-related tasks, and done some very basic editing for helping others with visual stuff. I've fixed some folks node code, but that was just reading docs and applying the few lines of change.
There are a lot of positions that never really touch js. My most recent project was working a lot with Chef, which is just ruby all the time.
It's hard to outweigh the advantage of using the same language in both the client and the server, and right now, JavaScript is the only universally practical choice on the client side, so it rules both sides now, in spite of all of node's and npm's problems. WebAssembly will loosen JavaScript's monopoly as it gradually matures, but right now all other languages but JavaScript are second-class citizens on the client side, and it will be that way for a while.