![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@terra-money/houston
Advanced tools
Houston is a development environment, testing framework and smart contract pipeline for Terra, aiming to make life as a Terra developer easier.
Houston will gracefully setup a stable version of rust compiler and wasm target to develop smart contracts on Terra blockchain.
Grab the latest version of NPM:
npm install -g houston
To get more information on Houston, check out the documentation.
Houston has five commands to help smart contract development:
init
: for project initialization
compile
: for compiling contracts
deploy
: for deploying contracts to blockchain
add
: for adding or downloading contract cargo projects
test
: for executing test scripts with Mocha and Chai
To get help on each command, run houston help <command>
.
mkdir myProject
cd myProject
houston init
Once this operation is completed, you'll now have a project structure with the following items:
myProject/
|- contracts
| |- starter
|- wasm
|- schema
|- test
|- houston-config.js
contracts
: contract directory for cosmwasm contract cargos
wasm
: wasm binary directory for compiled contracts
schema
: generated schema for compiled contracts
test
: test script directory for contract interaction
starter
: a starter cosmwasm project
Set current working directory inside of the project directory
houston compile --contracts [contractName]
All contract cargos in the contracts
directory will be compiled as default.
[contractName]
is an optional parameter to specify which cargo to compile with the command.
Once this operation is initiated, you'll see the event in the console as below:
Compiling your contracts...
===========================
After comilation of each contract, you'll get the directories for compiled results as below:
> WASM written to /Users/terraformlabs/myProject/wasm
> Schemas written to /Users/terraformlabs/myProject/schemas/starter_schemas
Compiled WASM binaries will be placed in wasm
directory as <cargo name>
.wasm.
Generated collection of schema json files will be placed as a directory with the name <cargo name>-schema
in schema
directory.
You will have the new project structure with the following items:
myProject/
|- contracts
| |- starter
|- wasm
| |- starter.wasm
|- schema
| |- starter-schema
| |- config.json
| |- ....
|- test
|- houston-config.js
Contributions are welcome to this project for helping Terra developers to build their dapps. To contribute to this project, you can check CONTRIBUTING.md for the detail.
Or you can join the Terra's official discord channel and discuss new ideas or addition.
This software is licensed under the Apache 2.0 license. See LICENSE for full disclosure.
© 2020 Terraform Labs, PTE.
FAQs
Core module for Houston smart contract framework
The npm package @terra-money/houston receives a total of 31 weekly downloads. As such, @terra-money/houston popularity was classified as not popular.
We found that @terra-money/houston demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.