wasm-check fails on ink! ERC20 example

[peblair]

To reproduce, create a project with the ink! ERC20 sample code and then run the following:

$ cargo install pwasm-utils --features cli
$ cargo contract build
$ wasm-check target/ink/erc20.wasm
All imports should be from env

Looking through the substrate codebase, I believe that it is the wasm-check tool which is incorrect, as the sealN modules (which are what are being used for the imports) should be correct.

[athei]

You are correct in your analyzes. Those CLI tools are somewhat lagging behind in features because all the internal users are using the crate directly. I was meaning to give them some love soon.