@sol, thanks for reporting, but what are you experiencing? stack ls dependencies does accept, and is affected by, --snapshot/--resolver.

For example, I have:

> stack new test-ls-deps
> cd test-ls-deps
> stack ls dependencies
base 4.19.2.0
ghc-bignum 1.3
ghc-prim 0.11.0
rts 1.0.2
test-ls-deps 0.1.0.0

> stack --snapshot ghc-9.10.1 ls dependencies
base 4.20.0.0
ghc-bignum 1.3
ghc-internal 9.1001.0
ghc-prim 0.11.0
rts 1.0.2
test-ls-deps 0.1.0.0

> stack --resolver ghc-9.6.6 ls dependencies
base 4.18.2.1
ghc-bignum 1.3
ghc-prim 0.10.0
rts 1.0.2
test-ls-deps 0.1.0.0

This is what I tried:

$ stack ls dependencies --resolver lts
Invalid option `--resolver'

Usage: stack ls dependencies [COMMAND | [--[no-]license] [--separator SEP]
                               [--filter ITEM] [--[no-]external]
                               [--[no-]include-base] [--depth DEPTH]
                               [--prune PACKAGES] [TARGET]
                               [--flag PACKAGE:[-]FLAG] [--test] [--bench]
                               [--global-hints]]

  View the packages versions used for a project. Use a command if the first
  target specified has the name of a command. Targets other than project
  packages are ignored.

So I guess "global" stack options have to come before the "env" command here.

What adds to the confusion is that for the "dot" command this restriction does not apply, e.g.

stack dot --resolver nightly

seem to work just fine.

Feel free to close as won't fix.

For convenience, most of the top-level commands have a 'hidden' (and undocumented) parser that parses the 'global' options 'a second time around'. That includes dot and, actually, ls. So you can command:

stack --snapshot nightly ls depencencies text
stack ls --snapshot nightly dependencies text

however, that UI 'trick' does not extend as far as the subcommands or the sub-subcommands. So you can't command:

stack ls dependencies --snapshot nightly text
stack ls dependencies text --snapshot nightly