Move IDE for VSCode

Built by developer for developers, this extension will simplify your Move development and will make your first experience with Move less painful.

• Jump to setup
• The Move Book
• Move Whitepaper
• Marketplace

What's inside:

• Move and Mvir syntax highlighting (always up to date) + spec support
• Code Completion for imported modules and built-ins
• Move Language Server and syntax error check!
• Move Executor - you can run your code in VSCode! Type Move: Run Script
• {{sender}} pattern support for address in your modules and scripts
• Built-in compiler Move (and Mvir) for Libra and Dfinance blockchains

Already want to try? To the marketplace!

Syntax highlighting

Extension features best syntax highlighting you can get for Move or Mvir. Each language has its own grammar file so you won't be mistaken and syntaxes won't overlap.

I've personally put much effort into making this syntax helpful (aka some keywords - like acquires won't be highlighted when misplaced).

Samples

Move - brand new language now shines bright in your VSCode (the best with Atom Light theme)

IDE Setup

Recomended directory structure

I highly recommend you using following directory structure:

modules/       - here you'll put your modules (module.move)
scripts/       - same here! scripts! (script.move)
out/           - compiler output directory (module.mv or module.mv.json)

.mvconfig.json - this file will help you keep setup within working directory (overrides vscode config)

Config file: .mvconfig.json

Not to mess up configurations and keep it simple I suggest you using config file inside your working directory. Sample here (put inside your working dir):

Configuration for Libra:

{
    "network": "libra",
    "sender": "0x....",
    "compilerDir": "out"
}

Configuration file for dfinance:

{
    "network": "dfinance",
    "sender": "wallet1...",
    "compilerDir": "out"
}

Comments:

• network: libra or dfinance (libra is default);
• sender: account from which you're going to deploy/run scripts;
• compilerDir: compiler output directory;

Additional configuration options:

• stdlibPath - custom path to stdlib folder - either relative to workspace or absolute or null;
• modulesPath - custom path to modules folder (instead of default modules) - relative or absolute or null;

Contribution

Feel free to ask any questions or report bugs by opening new issue.