You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a video tutorial so I had to create a new WSL environment and install blast therein.
@nbaum (mentioning you since you reacted to the initial issue), I noticed that the below steps result in an error/unexpected behaviour that could reduce dev-experience:
after running npm i cudos-blast global
running blast --help results in this error BlastError: package.json not found.Make sure the current working directory is your Blast project's path
afterwards I ran blast init in a directory, creating a new cudos/cosmwasm blast project. Running blast --help in this directory works
To further isolate:
-- creating an empty package.json and a blast.config.js as in the root directory (as explained in the workaround in the original issue)
Summarily: Unless you firstly run blast init , there needs to be a blast.config.js, and then a package.json file in a directory before one can run a blast command in that directory.
I am unable to run the blast command after successfully installing with
npm install cudos-blast -g
.Running any blast command like
blast --version
orblast --help
results in:BlastError: Config file was not found! Make sure that blast.config.js exists at ~[user]/blast.config.js
The text was updated successfully, but these errors were encountered: