Nightly versions may be unstable or not compatible across tooling.
This will essentially compile the packages without performing the final step of code generation, which is faster than running forc build.
Usage: forc check [OPTIONS] [BUILD_TARGET]
Arguments: [BUILD_TARGET] Build target to use for code generation
[default: fuel] [possible values: fuel, evm]
Options:
-p
, --path
<PATH>
Path to the project, if not specified, current working directory will be used
--offline
Offline mode, prevents Forc from using the network when managing dependencies. Meaning it will only try to use previously downloaded dependencies
--locked
Requires that the Forc.lock file is up-to-date. If the lock file is missing, or it needs to be updated, Forc will exit with an error
-t
, --terse
Terse mode. Limited warning and error output
--disable-tests
Disable checking unit tests
--ipfs-node
<IPFS_NODE>
The IPFS Node to use for fetching IPFS sources.
Possible values: FUEL, PUBLIC, LOCAL, <GATEWAY_URL>
--experimental
<EXPERIMENTAL>
Comma separated list of all experimental features that will be enabled
[possible values: new_encoding, references, error_type, const_generics]
--no-experimental
<NO_EXPERIMENTAL>
Comma separated list of all experimental features that will be disabled
[possible values: new_encoding, references, error_type, const_generics]
-v
, --verbose...
Use verbose output
-s
, --silent
Silence all output
-L
, --log-level
<LOG_LEVEL>
Set the log level
-h
, --help
Print help (see a summary with '-h')
-V
, --version
Print version
EXAMPLES:
forc check
forc check --path
forc check --locked