When comparing JSNLog vs CatchJS, the Slant community recommends CatchJS for most people. In the question“What are the best JavaScript client-side error logging services?” CatchJS is ranked 14th while JSNLog is ranked 17th. The most important reason people chose CatchJS is:
Can send emails when new errors happen.
Specs
Ranked in these QuestionsQuestion Ranking
Pros

Pro Integrates with your existing server-side logging package
Not a hosted option, so you'll store client-side logs along with your server-side logs.

Pro Stack traces
JSNLog passes exception log messages with its stack trace.
Pro Notifications when things break
Can send emails when new errors happen.
Pro Shows code snippets
Shows code snippets of the error and applies source maps automatically.
Pro Doesn't slow down page loads
Has a very small filesize, so it doesn't slow down page loads.
Pro Screenshots really help debugging
It takes a screenshot of the screen, so you can see what the user was looking at when the error happened.
Cons

Con No hosted option
You'll have to store client-side logs along with your server-side logs.

Con No reporting capabilities
Your server logging solution should provide that, and JSNlog integrates with Elmah, Log4Net, NLog, Serilog, Common.Logging.
