It would be cool to be able to reproduce any of the templates that are in Studio from the command line.

near new $TEMPLATE_NAME $PROJECT_NAME --project_dir $DIR

This one actually blocks development, since now we cannot see the result of contract execution when using near shell.

For instance:

near call near.test benchmark_sum_n "{\"n\": 10}" --accountId near.test                                      1 ↵  10030  13:41:58
[WARNING] Didn't find config at /Users/zaver/Projects/nearcore/src/config

Scheduling a call: near.test.benchmark_sum_n({"n": 10}) with attached 1000000000 NEAR
Loaded master account near.max key from /Users/zaver/.near/validator_key.json with public key = JBozFzsVw3j1KSZs1vnbtRtgdbv5m6RsoFDLnxHYB2Cv
Result: {
  logs: [
    {
      hash: '5Lcdu4GJDbgJWGSaAV5hf4yFsiudhWuVBqQaV5FEX7yW',
      lines: [],
      receipts: [],
      result: [Array]
    }
  ],
  status: 'Completed'
}

Displays [Array] instead of actually printing the JSON form. It was not the case before.

Currently in gulp-utils.js, the listFiles function passed to asc.main is listFiles: () => []. Previously this function was only used if you provided a library argument. However, now with the module resolution it's used to determine if a folder is valid. e.g.../z/v/node_modules. Is there a reason for this? Otherwise I'll remove it in the PR.
`

Here are some things I tried when I first used the tool installing globally from npm.

These are based on experiences with other CLI tools that generate apps.
E.g.

• Angular
• Leiningen
• Create React App

generating a project

near new .
# generates a new generic hello world in the current dir

near new my-project ---project_dir=~/directory
# generates project in new dir ~/directory/my-project 

near new $TEMPLATE $PROJECT
# generates a project in current dir from one of the studio templates (https://github.com/nearprotocol/near-shell/issues/14)

getting help

near --help
near -h
# returns help for all commands

near $CMD -h
# returns help for specific command

making an error in the commands

near ne
# tells me what commands I have at my disposal

Right now typical build process would be like:

Compile:
npm -> near -> gulp -> asc (compile)

Deploy:
npm -> near (deploy)

I think it instead should be:

Compile:
npm -> gulp -> near as a lib -> asc

Deploy:
npm -> gulp -> near (deploy)

I think this will make our CLI tools even better cause:

• gulp is a versatile tool which can be used for a lot of other app build tasks, web dev folks know it – no need to hide behind our CLI
• but people should be able to replace gulp easily as still not everyone wants to use it. This is much easier when near doesn't call gulp.

near create_account --help

says that --accountId is used to set the account to create, but acountId is now a required positional argument.

Changing amount silently is not a good practice. Instead, non-integer values should not be allowed.

near create_account nearproject

Error:  { BadRequestError: Transaction PwxM38gabyPbmtsi3RcOzvsDUwF/Lu9o6sjVbDnl4wQ= on unknown contract failed. 
    at sendJson (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/internal/send-json.js:12:15)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:182:7)
  message: 'Transaction PwxM38gabyPbmtsi3RcOzvsDUwF/Lu9o6sjVbDnl4wQ= on unknown contract failed. ' }

This is how most node build tools behave, cause otherwise it's very easy to have confusing version mismatches.

Not enough non-option arguments: got 0, need at least 1
This syntax is supposed to work

Observed:

1. Successfully log in with new master account @@@@@@@@

Expected:
Same flow, except that perhaps step (2) loads the most recently logged in account and step (3) uses whatever flag is explicitly set.

Error should say that this is not supported.
Instead, it references some obscure code in intermediate main.near.ts file.

Currently they are denominates in attoNEAR, which means that staking 10 NEARs is large number with 19 zeros which is hard to keep track.
All the amounts, including provided by user and printed out should display amount in NEAR (and use mantissa like 0.001 Ⓝ if it's smaller than one)

This needs to be in addition to testing the npm run flow for new project, which uses test_environment (that test case needs to stay)

steps to repro:
near blahblah
outputs nothing

instead, should say something about unrecognized command.

This used to work before

We have now 2 testnets - "TestNet" and "Staging". Would be good to be able to specify via NODE_ENV=staging

• send_money
• view_account
• view_state
• stake (this will be more complex, because people will be able to stake in several different ways: as validators and verifiers)
• swap_key
• view latest block
• get block by hash

Note, that some of these functions are or will be special cases of more generic functions. For instance, we discussed with @evgenykuzyakov and @ilblackdragon that we want all our transactions to look like function calls for consistency and forward compatibility. For instance, send_money will be a short cut for near call <my_account> send_money "{"receiver": <other_account>}", or somesuch.

Originally posted by @nearmax in near/docs#36 (comment)

E.g. use case:

• deploy "init"
• call function to initialize storage state
• deploy main contract

To query access key the endpoint is access_key/{public key}

This message shows up even if we are on envs that do not have a keypath configured

Failed to load master account key from /Users/evgueniadegtiareva/.near/validator_key.json: Error: ENOENT: no such file or directory, open '/Users/evgueniadegtiareva/.near/validator_key.json'

near create_account illia.near PUB_KEY <amount>

{
networkId: 'default',
nodeUrl: 'https://rpc.nearprotocol.com',
contractName: 'near-hello-devnet',
walletUrl: 'https://wallet.nearprotocol.com',
initialBalance: 100000000
}
events.js:173
throw er; // Unhandled 'error' event
^

Error: spawn gulp ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:19)
at onErrorNT (internal/child_process.js:431:16)
at processTicksAndRejections (internal/process/task_queues.js:84:17)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)
at onErrorNT (internal/child_process.js:431:16)
at processTicksAndRejections (internal/process/task_queues.js:84:17)

This gives the option to also fork the project. If we make it a dependency for this than we can still just copy the files as we currently do. Ideally it would be nice to have a selection of starting projects similar to NEARStudio.

edit: Updated image to highlight the deprecated warning not the error due to account

What should happen:

near send loaded.potato 1000000000
# All good. You sent a bunch o money

What's happening:

This is important to e.g. fail continuous deployment builds.

Currently old near-shell would either show nothing or show error saying "unexpected JSON output" which is unclear to user that near-shell must be updated.

Currently if one wants to use a different wallet (for example staging), there are not ways to specify it for near login command.

Generated template would generally have unique contract name, I'm thinking of following workflow.

Create app in my-awesome-app folder with my-awesome-app contract name:

npx create-near-app my-awesome-app

npm install done behind the scenes (like with create-react-app), contract account also created immediately.
This should also eventually have option for different stater templates, etc.

Run generated app:

cd my-awesome-app
npm start

Originally posted by @vgrichina in https://github.com/nearprotocol/near-shell/pull/24/files

Note, there is also other stuff that was not in pynear but we will very likely have:

• expiration_date Returns date and time of contract or access key expiration due to rent payments;
• add_access_key
• delete_access_key
• delete_account (Both delete_access_key and delete_account can be called by non-account owner if they are about to run out of balance due to rent)
• async_call (for contract calls the incur a long chain of cross-contract calls)
• async_status

Note, that some of these functions are or will be special cases of more generic functions. For instance, we discussed with @evgenykuzyakov and @ilblackdragon that we want all our transactions to look like function calls for consistency and forward compatibility. For instance, send_money will be a short cut for near call <my_account> send_money "

{"receiver": <other_account>}

", or somesuch.

_Originally posted by @nearmax in near/docs#36 (comment)

Right now it looks like I can only use one account at once which has keys stored in neardev/devkey.json.

This cannot support normal deploy pattern where developer deploys to local node and shared devnet using different accounts.

There should be some straightforward option to either use different accounts/key pairs or to use same key pair on both local node and shared devnet.

I need to run near login in a near project to login. Not doing so will result in a message like:

[WARNING] Didn't find config at /Users/shei/Desktop/code/nearcore/src/config
Log in is not needed on this environment. Please use appropriate master account for shell operations.

If we create a project using near new_project . and then run npm i && near build it would give the following error Error: ENOENT: no such file or directory, open 'out/model.near.ts' and can be resolved by manually creating the out directory.

Can't install near-shell via npm due to:

As a developer I don't want to specify full arguments to near deploy each time I need to deploy to different environment.

What I want to do instead is to have config file with necessary parameters for different env, e.g. like here:
https://github.com/sequelize/express-example/blob/master/config/config.js

As result deploy to production can be as easy as:

NODE_ENV=production npm run deploy

steps to repro:
start local node e.g. via nearcore/scripts/start_local

near login to testnet
near new_project and deploy
near view contractId whoSaidHi fails with

rror: Error: [-32000] Server error: account {localaccount} does not exist while viewing
at JsonRpcProvider.sendJsonRpc (/Users/evgueniadegtiareva/near/near-shell/node_modules/nearlib/lib/providers/json-rpc-provider.js:50:19)
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at async JsonRpcProvider.query (/Users/evgueniadegtiareva/near/near-shell/node_modules/nearlib/lib/providers/json-rpc-provider.js:32:24)
at async Account.fetchState (/Users/evgueniadegtiareva/near/near-shell/node_modules/nearlib/lib/account.js:33:23)
at async Account.state (/Users/evgueniadegtiareva/near/near-shell/node_modules/nearlib/lib/account.js:39:9)
at async Near.account (/Users/evgueniadegtiareva/near/near-shell/node_modules/nearlib/lib/near.js:35:9)
at async Object.exports.callViewFunction (/Users/evgueniadegtiareva/near/near-shell/index.js:110:21)
at async exitOnError (/Users/evgueniadegtiareva/near/near-shell/bin/near:8:5)

At least one dev flow is broken.
run after new_project, npm install, npm run-script test - this should run tests in a sandbox environment (i.e. separate instance of contract deployed and used). local_test_environment is supposed to be used for that, and it's being ignored right now.

Near shell cannot be used for users working with Rust contracts:

• It requires config.js;
• It requires contract helper. near shell is supposed to supersede pynear, by pynear was able to work without locally running contract helper.

To reproduce:

• Start local node, without contract helper, e.g. using ./run_local_dev.sh from near-ops;
• Execute the following commands (you can find the wasm contract here https://www.dropbox.com/s/l8vjk0p6aef52as/test_contract_bg.wasm?dl=0):

near create_account --useDevAccount --account_id "francis"          ✔  10014  10:01:20
[WARNING] Didn't find config at /Users/zaver/Projects/near-shell/src/config

near deploy --useDevAccount --account_id "francis" --wasmFile /Users/zaver/Projects/nearcore/runtime/rust-api/test-contract/pkg/test_contract_bg.wasm
[WARNING] Didn't find config at /Users/zaver/Projects/near-shell/src/config

Starting deployment. Account id: francis, node: http://localhost:3030, helper: undefined, file: /Users/zaver/Projects/nearcore/runtime/rust-api/test-contract/pkg/test_contract_bg.wasm
Error:  Error: [1] Error calling abci_query(account/francis,,0,false)
Message: undefined
account francis does not exist while viewing
    at NearClient.jsonRpcRequest (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/nearclient.js:108:27)
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
    at async NearClient.viewAccount (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/nearclient.js:23:26)
    at async NearClient.getNonce (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/nearclient.js:87:17)
    at async Near.deployContract (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/near.js:128:23)
    at async Object.exports.deploy (/usr/local/lib/node_modules/near-shell/index.js:78:9)
    at async exitOnError (/usr/local/lib/node_modules/near-shell/bin/near:8:5) {
  log: 'account francis does not exist while viewing'

export function broken_function(): u64[] {
    return [1, 2];
}

Trying to compile this results in the following error:

ERROR TS2339: Property 'toString' does not exist on type 'u64'.
    encoder.setString(null, value[i].toString());
    in ../out/main.near.ts(42,33)

Steps to reproduce:

• Start a node Navigate to nearcore folder. Switch to staging branch. Pull it. Start a node with:

rm -rf testdir; ./scripts/start_unittest.py --local

• Get most recent near-shell Navigate to near-shell folder. Switch to staging. Install it:

rm -rf node_modules; npm install

• Create new account Where /Users/zaver/Projects/nearcore should be replaced to your path to nearcore folder.

./bin/near create_account status_message --masterAccount=test.near --homeDir=/Users/zaver/Projects/nearcore/testdir --nodeUrl=http://localhost:3030

• Deploy smart contract (get wasm file here: https://www.dropbox.com/s/gtg1ytn8vboe3gj/status_message.wasm?dl=0)

/bin/near deploy --accountId=status_message --wasmFile=/Users/zaver/Projects/near-runtime-rs/examples/status-message/res/status_message.wasm --homeDir=/Users/zaver/Projects/nearcore/testdir --nodeUrl=http://localhost:3030

• Call a function on it

./bin/near call status_message set_status "{\"message\": \"Hello\"}" --accountId=test.near --wasmFile=/Users/zaver/Projects/near-runtime-rs/examples/status-message/res/status_message.wasm --homeDir=/Users/zaver/Projects/nearcore/testdir --nodeUrl=http://localhost:3030

EXPECTED:

To get a meaningful output.

ACTUAL:

near-shell returns an error:

WARNING] Didn't find config at /Users/zaver/Projects/near-shell/src/config, using default shell config
Scheduling a call: status_message.set_status({"message": "Hello"}) with attached 1000000000 NEAR
Loaded master account test.near key from /Users/zaver/Projects/nearcore/testdir/validator_key.json with public key = 22skMptHjFWNyuEWY22ftn2AbLPSYpmYwGJRGwpNHbTV
Error:  TypeError: Cannot read property 'length' of undefined
    at Object.getTransactionLastResult (/Users/zaver/Projects/near-shell/node_modules/nearlib/lib/providers/provider.js:14:32)
    at Object.exports.scheduleFunctionCall (/Users/zaver/Projects/near-shell/index.js:98:37)
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
    at async exitOnError (/Users/zaver/Projects/near-shell/bin/near:8:5)

• Confirm that the state changed. We want to make sure that the above error is about transaction status not being read correctly, while the contract call was actually correctly executed.

./bin/near view status_message get_status "{\"account_id\": \"test.near\"}" --accountId=test.near --wasmFile=/Users/zaver/Projects/near-runtime-rs/examples/status-message/res/status_message.wasm --homeDir=/Users/zaver/Projects/nearcore/testdir --nodeUrl=http://localhost:3030

OBSERVE:

Result: Hello

Running near login with node version 9.0 gives error:

{ networkId: 'default',
nodeUrl: 'http://34.94.33.164:3030',
contractName: 'near-hello-devnet',
walletUrl: 'https://wallet.nearprotocol.com' }
Error: ReferenceError: URL is not defined
at Object.exports.login (/usr/local/lib/node_modules/near-shell/index.js:122:24)
at Object.handler (/usr/local/lib/node_modules/near-shell/bin/near:90:39)
at Object.runCommand (/usr/local/lib/node_modules/near-shell/node_modules/yargs/lib/command.js:242:26)
at Object.parseArgs [as _parseArgs] (/usr/local/lib/node_modules/near-shell/node_modules/yargs/yargs.js:1078:30)
at Object.get [as argv] (/usr/local/lib/node_modules/near-shell/node_modules/yargs/yargs.js:1012:21)
at Object. (/usr/local/lib/node_modules/near-shell/bin/near:216:3)
at Module._compile (internal/modules/cjs/loader.js:654:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
at Module.load (internal/modules/cjs/loader.js:566:32)
at tryModuleLoad (internal/modules/cjs/loader.js:506:12)