feat(docs): add docs, release blog, more nits

packages/neo-one-cli-common-node/src/configuration.ts

@@ -17,8 +17,12 @@ const configurationDefaults = {
     path: nodePath.join('neo-one', 'migration.js'),
   },
   contracts: {
-    path: nodePath.join('neo-one', 'contracts'),
     outDir: nodePath.join('neo-one', 'compiled'),
+    path: nodePath.join('neo-one', 'contracts'),
+    json: true,
+    avm: false,
+    debug: false,
+    opcodes: false,
   },
   codegen: {
     path: nodePath.join('src', 'neo-one'),
@@ -91,11 +95,15 @@ const configurationSchema = {
     },
     contracts: {
       type: 'object',
-      allRequired: true,
+      allRequired: false,
       additionalProperties: false,
       properties: {
-        path: { type: 'string' },
         outDir: { type: 'string' },
+        path: { type: 'string' },
+        json: { type: 'boolean' },
+        avm: { type: 'boolean' },
+        debug: { type: 'boolean' },
+        opcodes: { type: 'boolean' },
       },
     },
     codegen: {
@@ -157,8 +165,8 @@ const relativizePaths = (config: Configuration) => ({
   },
   contracts: {
     ...config.contracts,
-    path: nodePath.relative(process.cwd(), config.contracts.path),
     outDir: nodePath.relative(process.cwd(), config.contracts.outDir),
+    path: nodePath.relative(process.cwd(), config.contracts.path),
   },
   codegen: {
     ...config.codegen,
@@ -181,10 +189,18 @@ const createDefaultConfiguration = (configIn: Configuration, importDefaultNetwor
 
 ${exportConfig} {
   contracts: {
-    // NEO•ONE will look for smart contracts in this directory.
-    path: '${config.contracts.path}',
     // The NEO•ONE compile command will output the compile results in this directory.
     outDir: '${config.contracts.outDir}',
+    // NEO•ONE will look for smart contracts in this directory.
+    path: '${config.contracts.path}',
+    // Set this to true if you want the compile command to output JSON.
+    // json: ${config.contracts.json},
+    // Set this to true if you want the compile command to output AVM.
+    // avm: ${config.contracts.avm},
+    // Set this to true if you want the compile command to output additional debug information.
+    // debug: ${config.contracts.debug},
+    // Set this to true if you want the compile command to output the AVM in a human-readable format for debugging (requires debug: true).
+    // opcodes: ${config.contracts.opcodes},
   },
   artifacts: {
     // NEO•ONE will store build and deployment artifacts that should be checked in to vcs in this directory.
@@ -297,8 +313,8 @@ const validateConfig = async (rootDir: string, configIn: any): Promise<Configura
     },
     contracts: {
       ...config.contracts,
-      path: nodePath.resolve(rootDir, config.contracts.path),
       outDir: nodePath.resolve(rootDir, config.contracts.outDir),
+      path: nodePath.resolve(rootDir, config.contracts.path),
     },
     codegen: {
       ...config.codegen,

packages/neo-one-cli-common/src/configuration.ts

@@ -4,8 +4,12 @@ export type CodegenFramework = 'none' | 'react' | 'angular' | 'vue';
 export type CodegenLanguage = 'typescript' | 'javascript';
 
 export interface ContractsConfiguration {
-  readonly path: string;
   readonly outDir: string;
+  readonly path: string;
+  readonly json?: boolean;
+  readonly avm?: boolean;
+  readonly debug?: boolean;
+  readonly opcodes?: boolean;
 }
 
 export interface CodegenConfiguration {

packages/neo-one-cli/src/cmd/compile.ts

@@ -2,7 +2,6 @@ import { Yarguments } from '@neo-one/utils-node';
 import yargs from 'yargs';
 import { start } from '../common';
 import { createTasks } from '../compile';
-
 export const command = 'compile';
 export const describe = 'Compiles a project and outputs code to a local directory.';
 export const builder = (yargsBuilder: typeof yargs) =>
@@ -13,28 +12,32 @@ export const builder = (yargsBuilder: typeof yargs) =>
     .describe('path', 'Contract directory')
     .boolean('json')
     .describe('json', 'Output the contract with the JSON format')
-    .default('json', true)
     .boolean('avm')
     .describe('avm', 'Output the contract with the AVM format')
-    .default('avm', false)
     .boolean('debug')
     .describe('debug', 'Output additional debug information')
-    .default('debug', false)
     .boolean('opcodes')
-    .describe('opcodes', 'Output the AVM in a human readable format for debugging, requires --debug')
-    .default('opcodes', false);
+    .describe('opcodes', 'Output the AVM in a human readable format for debugging, requires --debug');
 
 export const handler = (argv: Yarguments<ReturnType<typeof builder>>) => {
   start(async (_cmd, config) => {
-    await createTasks(
-      argv.path ? argv.path : config.contracts.path,
-      argv.outDir ? argv.outDir : config.contracts.outDir,
-      {
-        json: argv.json ? argv.json : !argv.avm,
-        avm: argv.avm,
-        debug: argv.debug,
-        opcodes: argv.debug ? argv.opcodes : false,
-      },
-    ).run();
+    const configOptions = config.contracts;
+    const path = argv.path ? argv.path : configOptions.path;
+    const outDir = argv.outDir ? argv.outDir : configOptions.outDir;
+    const options = {
+      json: argv.json ? argv.json : configOptions.json,
+      avm: argv.avm ? argv.avm : configOptions.avm,
+      debug: argv.debug ? argv.debug : configOptions.debug,
+      opcodes: argv.opcodes ? argv.opcodes : configOptions.opcodes,
+    };
+    if (options.opcodes && !options.debug) {
+      throw new Error('`opcodes` flag may only be specified alongside the `debug` flag');
+    }
+    await createTasks(path, outDir, {
+      json: options.json ? options.json : !options.avm,
+      avm: options.avm ? options.avm : false,
+      debug: options.debug ? options.debug : false,
+      opcodes: options.opcodes ? options.opcodes : false,
+    }).run();
   });
 };

packages/neo-one-cli/src/cmd/console.ts

@@ -6,11 +6,11 @@ import { startConsole } from '../console';
 const defaultNetworks: readonly string[] = ['local'];
 
 export const command = 'console';
-export const describe = 'Starts a repl with project contracts and client APIs available.';
+export const describe = 'Starts a REPL with project contracts and client APIs available.';
 export const builder = (yargsBuilder: typeof yargs) =>
   yargsBuilder
     .array('networks')
-    .describe('networks', 'Networks to initialize before starting the repl.')
+    .describe('networks', 'Networks to initialize before starting the REPL.')
     .default('networks', defaultNetworks);
 export const handler = (argv: Yarguments<ReturnType<typeof builder>>) => {
   start(async (_cmd, config) => startConsole(config, argv.networks));

packages/neo-one-cli/src/cmd/stop/neotracker.ts

@@ -3,7 +3,7 @@ import { start } from '../../common';
 import { findKillProcess } from '../../utils';
 
 export const command = 'neotracker';
-export const describe = 'Stops the local neotracker instance.';
+export const describe = 'Stops the local NEO Tracker instance.';
 export const builder = (yargsBuilder: typeof yargs) => yargsBuilder;
 export const handler = () => {
   start(async (_cmd, config) => {

packages/neo-one-website/blog/2020-07-23-neo-one-27-announcement.md

@@ -0,0 +1,67 @@
+---
+slug: 2020/07/23/neo-one-27-announcement
+title: NEO•ONE 2.7 Announcement
+author: The NEO•ONE Team
+twitter: https://twitter.com/neo_one_suite
+---
+
+## NEO•ONE 2.7
+
+We are excited to announce our latest release of NEO•ONE. For this release we have been focused on cleaning up bugs, adding new compiler features, expanding documentation, and preparing for future versions of NEO•ONE as we draw closer to the Neo3 release.
+
+To get started with NEO•ONE you can install our CLI with
+`yarn install @neo-one/cli`
+
+## Compile
+
+Starting with NEO•ONE 2.7 you will be able to output your compiled smart contract to various format types as well as generate debug information as per the spec listed [here](https://github.com/ngdseattle/design-notes/blob/master/NDX-DN11%20-%20NEO%20Debug%20Info%20Specification.md). We hope this will give our users more freedom in the end-to-end tooling they choose to use for developing their smart contracts. To get started with testing these new features you can use:
+
+`yarn install @neo-one/cli`
+`yarn neo-one init`
+`yarn neo-one compile --json --avm --debug --opcodes`
+
+For more information on how to enable AVM / debug generation use
+
+`yarn neo-one compile --help`
+
+or see the [pull request](https://github.com/neo-one-suite/neo-one/pull/2071).
+
+### Further Work
+
+While we have added the ability to output our compiled smart contracts as `.debug` and `.avm` files there is still work to be done to integrate these features with other tooling, like the Neo Blockchain Toolkit. See the PR linked above or visit the new issue page [here](https://github.com/neo-one-suite/neo-one/issues/2113) for more information. Also be sure to check out our [documentation](/docs/how-to-contribute#How-Can-I-Contribute) on building from source if you would like to help contribute to the project!
+
+## Typescript Updates
+
+In continuing with our efforts to keep NEO•ONE up to date with Typescript we have [updated](https://github.com/neo-one-suite/neo-one/pull/2063) the project to use TypeScript version 3.9.5. While there aren’t as many new features available in the compiler as our [last](https://github.com/neo-one-suite/neo-one/pull/1984) update we want to keep our feature set as familiar to new developers as we can, especially as we gear up for Neo3.
+
+## Documentation
+
+We’ve added several new sections of documentation to the website:
+
+- [Deployment documentation](/docs/deployment)
+- [The NEO•ONE CLI](/docs/cli)
+- [Network configuration](/docs/configuration-options)
+- [Project contribution](/docs/how-to-contribute#How-Can-I-Contribute)
+- [Compiler contribution](/docs/smart-contract-compiler)
+
+Stumped on something and can’t find documentation for it? Feel free to submit a new [issue](https://github.com/neo-one-suite/neo-one/issues) to request it!
+
+## Bug Fixes / Feature Changes
+
+In NEO•ONE 2.7 several bugs have been fixed and features have been updated. You can see all the changes listed below.
+
+- [#2056 Generated createClient does not wait For account setup](https://github.com/neo-one-suite/neo-one/pull/2056)
+- [#2051 Update default network options](https://github.com/neo-one-suite/neo-one/pull/2051)
+- [#2093 Fix switch-statement execution](https://github.com/neo-one-suite/neo-one/pull/2093)
+- [#2095 Fix number mismatches in SetStorage, ArrayStorage and MapStorage](https://github.com/neo-one-suite/neo-one/pull/2095)
+- [#2086 Export `defaultnetwork` helper from CLI](https://github.com/neo-one-suite/neo-one/pull/2086)
+- [#2080 Fix missing type declarations in shipped packages](https://github.com/neo-one-suite/neo-one/pull/2091)
+- [#2096 Fix ‘receive’ invocations when relaying transactions to a live network](https://github.com/neo-one-suite/neo-one/pull/2096)
+- [#2112 Fix error when using typescript migration file for deployment](https://github.com/neo-one-suite/neo-one/pull/2112)
+- [#2034 Update npm release process for smoother releases](https://github.com/neo-one-suite/neo-one/pull/2034)
+
+## Future
+
+NEO•ONE 2.7 will be the last milestone release for NEO•ONE 2.x, while small bug fixes and integration fixes (like https://github.com/neo-one-suite/neo-one/pull/2034) will continue to be released on the 2.x version our work will primarily focus on updating NEO•ONE to be compatible with the Neo3 protocol. Look out for the upcoming releases that will include Neo3 Preview, TestNet and MainNet compatibility.
+
+Questions or concerns? Feel free to reach out to us on [GitHub](https://github.com/neo-one-suite/neo-one) or [Twitter](https://twitter.com/neo_one_suite)

packages/neo-one-website/docs/0-installation/2-cli.md

@@ -0,0 +1,103 @@
+---
+slug: CLI
+title: CLI
+---
+
+The NEO•ONE CLI is your entry point for all of NEO•ONE's functionality.
+
+Run `yarn neo-one --help` to see the CLI commands available and their descriptions.
+Run `yarn neo-one <command> --help` to see what arguments are available for that command.
+Run `yarn neo-one --version` to get the version of NEO•ONE that you are running.
+
+---
+
+[[toc]]
+
+---
+
+## neo-one init
+
+Initializes a new project in the current directory. This will create a default `.neo-one.config.ts` configuration file,
+a sample `Hello World` smart contract in `neo-one/contracts/HelloWorld.ts`, and a unit test in
+`src/__tests__/HelloWorld.ts`.
+
+| Argument  | Type      | Default | Description                                                                                              |
+| --------- | --------- | ------- | -------------------------------------------------------------------------------------------------------- |
+| `--react` | `boolean` | `false` | Setting this to true will generate an example. React component that uses the `HelloWorld` smart contract |
+
+---
+
+## neo-one build
+
+Builds the project and deploys it to the local development network based on the configuration found in the
+NEO•ONE config file.
+
+| Argument  | Type      | Default | Description                                       |
+| --------- | --------- | ------- | ------------------------------------------------- |
+| `--reset` | `boolean` | `false` | Setting this to true will reset the local project |
+
+---
+
+## neo-one new
+
+Create new resources. `neo-one new private-key` is the only available option for now, which will generate a
+new private key.
+
+---
+
+## neo-one start
+
+Start NEO•ONE services. This command takes one argument after the command (`neo-one start <arg>`) which
+can be either `network` or `neotracker`. `neo-one start network` will start the local development network.
+`neo-one start neotracker` will start the local NEO Tracker instance.
+
+---
+
+## neo-one stop
+
+Stop NEO•ONE services. This command takes one argument after the command (`neo-one stop <arg>`) which
+can be either `network` or `neotracker`. `neo-one stop network` will stop the local development network.
+`neo-one stop neotracker` will stop the local NEO Tracker instance.
+
+---
+
+## neo-one deploy
+
+Deploys the project using the migration file.
+
+| Argument    | Type     | Default  | Description                     |
+| ----------- | -------- | -------- | ------------------------------- |
+| `--network` | `string` | `"test"` | Network to run the migration on |
+
+---
+
+## neo-one info
+
+Prints the project configuration.
+
+---
+
+## neo-one compile
+
+Compiles a project's smart contracts and outputs the code to a local directory. You can set the arguments for this command
+either in the NEO•ONE config file (`.neo-one.config.ts`) or as a CLI argument. A CLI argument will override what is found in the
+config file. If an argument is not defined as a CLI argument and is not defined in the config file then the below defaults will be used.
+
+| Argument    | Type      | Default             | Description                                                                  |
+| ----------- | --------- | ------------------- | ---------------------------------------------------------------------------- |
+| `--outDir`  | `string`  | `neo-one/compiled`  | Directory to output the compiled code                                        |
+| `--path`    | `string`  | `neo-one/contracts` | Path to the smart contract directory                                         |
+| `--json`    | `boolean` | `true`              | Output the contract with the JSON format                                     |
+| `--avm`     | `boolean` | `false`             | Output the contract with the AVM format                                      |
+| `--debug`   | `boolean` | `false`             | Output additional debug information                                          |
+| `--opcodes` | `boolean` | `false`             | Output the AVM in a human-readable format for debugging (requires `--debug`) |
+
+---
+
+## neo-one console
+
+Starts a REPL with project contracts and NEO•ONE Client APIs.
+
+| Argument     | Type    | Default     | Description                                     |
+| ------------ | ------- | ----------- | ----------------------------------------------- |
+| `--networks` | `array` | `["local"]` | Networks to initialize before starting the REPL |

packages/neo-one-website/docs/4-contributing/2-smart-contract-compiler.md

@@ -3,7 +3,9 @@ slug: smart-contract-compiler
 title: Smart Contract Compiler
 ---
 
-## How Can I Add New Features or Fix Bugs in the Smart Contract Compiler
+## How Can I Add New Features or Fix Bugs in the Smart Contract Compiler?
+
+### Basics of the Smart Contract Compiler
 
 The NEO•ONE Smart Contract Compiler is by far the _largest_ NEO•ONE package. The compiler takes in (almost) regular
 TypeScript code and compiles it to [NeoVM](https://docs.neo.org/docs/en-us/basic/technology/neovm.html) bytecode, which can
@@ -14,13 +16,17 @@ The bytecode outputted by the compiler corresponds to human-readable opcodes tha
 NeoVM will perform. These actions are the manipulation of data by the NeoVM that will ultimately translate to changes to the
 state of the Neo blockchain.
 
+### Where to Look in the Code
+
 Now that you have a _very_ basic understanding of how the NEO•ONE compiler works, you can start digging into the `neo-one-smart-contract-compiler`
-package. Most likely you'll be looking in `packages/neo-one-smart-contract-compiler/compiler/<subfolder>` (where `<subfolder>` is one of `constants`, `declaration`, `expression`, `helper`, `scope`, `statement`)
-for the specific syntax that is broken or where you want to add a feature. For example, if you want to change how we compile the `===` token, you would
-look for `EqualsEqualsEqualsHelper.ts` in `packages/neo-one-smart-contract-compiler/compiler/helper/relational/EqualsEqualsEqualsHelper.ts`. In there you'll see
+package. Most likely you'll be looking in `neo-one-smart-contract-compiler/compiler/<subfolder>` (where `<subfolder>` is one of `constants`, `declaration`, `expression`, `helper`, `scope`, `statement`)
+for the specific syntax that is broken or where you want to add a feature. For example, if you want to change how we compile the `==` token, you would
+look for `EqualsEqualsEqualsHelper.ts` in `neo-one-smart-contract-compiler/compiler/helper/relational/EqualsEqualsHelper.ts`. In there you'll see
 how this helper will "emit" different opcodes, syscalls, and other helpers to manipulate the Evaluation Stack. The comment line above each emit shows a
 representation of the Evaluation Stack _after_ that bytecode is evaluated.
 
+### Write Unit Tests for What You're Working On
+
 Once you have an understanding of what helpers or syntax compilers you need to change in order to make your compiler change, the best way to begin is to write
 a unit test that you will run to test your change. You'll see that nearly every helper and syntax compiler has a corresponding set of unit tests in `neo-one-smart-contract-compiler/src/__tests__`.
 For example, the `IfStatementCompiler.ts` has a set of unit tests in `IfStatementCompiler.test.ts`. In there you'll see that we typically use the built in `assertEqual` method to
@@ -45,9 +51,11 @@ describe('MyNewCompiler', () => {
 });
 ```
 
+### Start Hacking
+
 Once you've created a unit test that either recreates the bug you're trying to fix, or tests for the expected behavior of your new feature, you can start to make changes
 to the compiler's source code and run your unit test. If you want to add logging (ie. `console.log`) to the source code to get more information you can, just make sure
-to change the console settings in `packages/neo-one-build-tests/environments/test/jestSetup.js`. From there you should make sure to only run one unit test at a time
+to change the console settings in `neo-one-build-tests/environments/test/jestSetup.js`. From there you should make sure to only run one unit test at a time
 so that you're only getting logs from the compilation of that one unit test. This will make it easier to learn what the compiler is doing when compiling a specific string.
 To run a specific unit test, rather than all unit tests, run `rush test -t <path/to/testfile>`.