KO
|
EN
gitlite โ search
Search
#typescript
#ai-agents
#deepseek-harness
#dsh-plugin
#open-source
#ai
#claude-code
#cli
#windows
#codex
#developer-tools
#dsh
oasis.js
โ 32
Open GitHub โ
๐ธA web client for the Oasis platform
Download README (.md)
Explore Similar Repositories
chess-engine-nn
:
Chess engine that uses neural network to decide on moves
socket.io-docs
:
:cn: socket.io ไธญๆๆๆกฃใhttps://socket.gitbook.io/docs/ ็ฟป่ฏๅฎๆฏ :heavy_check_mark: ็ญๅพ ๆ ก้ช :heavy_multiplication_x: (ๆณจ๏ผ่ฏฅๆๆกฃๅฏ่ฝ่ฟไบไน ่ฟ)
repo
:
No description available.
mpris-integration
:
Adds mpris integration for certain sites using a Firefox Webextension.
noinstagram
:
"follow" instagram users/tags without an IG account
// repository documentation
Was this content helpful?
โ 0
(0 ratings)
Select Rating:
โ
โ
โ
โ
โ
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
oasis.js
?
Download (.md)
[](https://circleci.com/gh/oasislabs/oasis.js) [](https://gitter.im/Oasis-official/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [](https://oasis-labs-oasis-client.readthedocs-hosted.com/en/latest/) See the [documentation](https://oasis-labs-oasis-client.readthedocs-hosted.com/en/latest/). ## Packages ### The Client For most use cases, it's recommended to use the main `@oasislabs/client` package for all your Oasis client needs, for which there is extensive documentation. | Package | Version | Description | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | | [`@oasislabs/client`](/packages/client) | [](https://www.npmjs.com/package/@oasislabs/client) | Client SDK for interacting with services on Oasis | ### Internal Packages However, if you only need a subset of the client's features, you can take what you need directly from the underlying packages. Together these packages compose the client. Standalone documentation is not provided so it's recommended to use these only if you know what you're doing. | Package | Version | Description | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | | [`@oasislabs/gateway`](/packages/gateway) | [](https://www.npmjs.com/package/@oasislabs/gateway) | Oasis Gateway implementation used as the client backend | | [`@oasislabs/service`](/packages/service) | [](https://www.npmjs.com/package/@oasislabs/service) | Connects to and deploys IDL defined services | | [`@oasislabs/confidential`](/packages/confidential) | [](https://www.npmjs.com/package/@oasislabs/confidential) | Primitives for confidentiality | | [`@oasislabs/common`](/packages/common) | [](https://www.npmjs.com/package/@oasislabs/common) | Common utilities for Oasis packages | | [`@oasislabs/test`](/packages/test) | [](https://www.npmjs.com/package/@oasislabs/test) | Tools used in Oasis tests | | [`@oasislabs/web3`](/packages/web3) | [](https://www.npmjs.com/package/@oasislabs/web3) | Web3 JSON RPC version of an Oasis Gateway | ## Contributing ### Installing To get started first install the required build tools: ``` npm install -g lerna npm install -g yarn ``` Then bootstrap the workspace: ``` yarn ``` ### Building To build the workspace: ``` yarn build ``` In each package, the built javascript and typescript definitions will be in `dist/`. For direct browser testing of a client, simply include the rollup artifact directly in your script tag, e.g., `<script src=/dist/index.umd.js></script>`. For example [here](https://github.com/oasislabs/oasis.js/blob/master/packages/client/test/browser/service/index.html#L3). ### Testing To run all tests: ``` yarn test ``` ### Linting To lint: ``` yarn lint ``` To apply lint fixes: ``` yarn lint:fix ``` ### Publishing new npm package versions This is a multi-package repo; packages are managed by `lerna`. First, bump the version number in all `package.json`: ```sh git checkout -b mybranch lerna version # bumps package numbers and creates a commit ``` Get the PR approved and merge it. Then pull the newly-updated master and push packages from it to npm: ```sh git checkout master && git pull lerna publish from-package ```
