It is likely that npm is trying to remove it from one place, but you still installed it somewhere else.
This is a problem when, for example, a program npmuses #!/usr/bin/env nodea shebang in the string instead of the exact patch for the binary file nodefor which it was installed (common for Node binary installations), especially when you have many versions of Node installed in many places.
See what is the result:
which node
which npm
cat `which npm` | head -1
cat `which eslint` | head -1
ls -alp `which npm`
ls -alp `which eslint`
cat $PATH
and try to narrow down the problem.