There's a de facto standard format for compiler or linter error messages, which is the same format as `grep -n`: `_FILE_NAME_ : _LINE_NUMBER_ : _MESSAGE_`. Experimentally, nano supports that. I haven't researched if it supports any other format, but in any case it doesn't support lacheck's format.
You can define a wrapper to the lacheck command that rewrites its messages in the standard format, and tell nano to invoke that wrapper instead of invoking lacheck directly.
#!/usr/bin/env bash
set -o pipefail
lacheck "$@" 2>&1 | sed 's/^"\([^"]*\)", line /\1:/'