{"_id":"@amoeba_/compliance","name":"@amoeba_/compliance","dist-tags":{"latest":"0.1.0"},"versions":{"0.1.0":{"name":"@amoeba_/compliance","version":"0.1.0","description":"Generated Soroban client for the Amoeba compliance contract","license":"MIT","type":"module","repository":{"type":"git","url":"git+https://github.com/wurli-sh/amoeba.git","directory":"bindings/generated/compliance"},"publishConfig":{"access":"public"},"exports":"./dist/index.js","types":"./dist/index.d.ts","dependencies":{"@stellar/stellar-sdk":"^14.5.0","buffer":"6.0.3"},"devDependencies":{"typescript":"^5.6.2"},"scripts":{"build":"tsc"},"_id":"@amoeba_/compliance@0.1.0","bugs":{"url":"https://github.com/wurli-sh/amoeba/issues"},"homepage":"https://github.com/wurli-sh/amoeba#readme","_integrity":"sha512-gThpqsQmSP6AJgMvwP+kQsZ0tqb9uqPxfe15rEmctcHtD+V/3KaH2m/rIN4rWq0J0Dd7d9lmKmBsKg2rEUne3g==","_resolved":"/tmp/3a94f2a4d8ab4fb1ba705280444f5001/amoeba_-compliance-0.1.0.tgz","_from":"file:amoeba_-compliance-0.1.0.tgz","_nodeVersion":"25.9.0","_npmVersion":"11.12.1","dist":{"integrity":"sha512-gThpqsQmSP6AJgMvwP+kQsZ0tqb9uqPxfe15rEmctcHtD+V/3KaH2m/rIN4rWq0J0Dd7d9lmKmBsKg2rEUne3g==","shasum":"a2901f48358b5b6cad4112b5e0745bd46b268276","tarball":"https://registry.npmjs.org/@amoeba_/compliance/-/compliance-0.1.0.tgz","fileCount":5,"unpackedSize":31749,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQCnSymMJBTNfPu1xePqo/rscGlr5hR/7cHNnCB89JGWgQIhAIbrCwIyNmhZpBeLc6yYBNOaO1p5sTwjbAOBRE0YfljY"}]},"_npmUser":{"name":"patlu-sh","email":"elaaprasad@gmail.com"},"directories":{},"maintainers":[{"name":"patlu-sh","email":"elaaprasad@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/compliance_0.1.0_1781778262712_0.6521025294920422"},"_hasShrinkwrap":false}},"time":{"created":"2026-06-18T10:24:22.541Z","0.1.0":"2026-06-18T10:24:22.858Z","modified":"2026-06-18T10:24:23.074Z"},"maintainers":[{"name":"patlu-sh","email":"elaaprasad@gmail.com"}],"description":"Generated Soroban client for the Amoeba compliance contract","homepage":"https://github.com/wurli-sh/amoeba#readme","repository":{"type":"git","url":"git+https://github.com/wurli-sh/amoeba.git","directory":"bindings/generated/compliance"},"bugs":{"url":"https://github.com/wurli-sh/amoeba/issues"},"license":"MIT","readme":"# compliance JS\n\nJS library for interacting with [Soroban](https://soroban.stellar.org/) smart contract `compliance` via Soroban RPC.\n\nThis library was automatically generated by Soroban CLI using a command similar to:\n\n```bash\nsoroban contract bindings ts \\\n  --rpc-url INSERT_RPC_URL_HERE \\\n  --network-passphrase \"INSERT_NETWORK_PASSPHRASE_HERE\" \\\n  --contract-id INSERT_CONTRACT_ID_HERE \\\n  --output-dir ./path/to/compliance\n```\n\nThe network passphrase and contract ID are exported from [index.ts](./src/index.ts) in the `networks` constant. If you are the one who generated this library and you know that this contract is also deployed to other networks, feel free to update `networks` with other valid options. This will help your contract consumers use this library more easily.\n\n# To publish or not to publish\n\nThis library is suitable for publishing to NPM. You can publish it to NPM using the `npm publish` command.\n\nBut you don't need to publish this library to NPM to use it. You can add it to your project's `package.json` using a file path:\n\n```json\n\"dependencies\": {\n  \"compliance\": \"./path/to/this/folder\"\n}\n```\n\nHowever, we've actually encountered [frustration](https://github.com/stellar/soroban-example-dapp/pull/117#discussion_r1232873560) using local libraries with NPM in this way. Though it seems a bit messy, we suggest generating the library directly to your `node_modules` folder automatically after each install by using a `postinstall` script. We've had the least trouble with this approach. NPM will automatically remove what it sees as erroneous directories during the `install` step, and then regenerate them when it gets to your `postinstall` step, which will keep the library up-to-date with your contract.\n\n```json\n\"scripts\": {\n  \"postinstall\": \"soroban contract bindings ts --rpc-url INSERT_RPC_URL_HERE --network-passphrase \\\"INSERT_NETWORK_PASSPHRASE_HERE\\\" --id INSERT_CONTRACT_ID_HERE --name compliance\"\n}\n```\n\nObviously you need to adjust the above command based on the actual command you used to generate the library.\n\n# Use it\n\nNow that you have your library up-to-date and added to your project, you can import it in a file and see inline documentation for all of its exported methods:\n\n```js\nimport { Contract, networks } from \"compliance\"\n\nconst contract = new Contract({\n  ...networks.futurenet, // for example; check which networks this library exports\n  rpcUrl: '...', // use your own, or find one for testing at https://soroban.stellar.org/docs/reference/rpc#public-rpc-providers\n})\n\ncontract.|\n```\n\nAs long as your editor is configured to show JavaScript/TypeScript documentation, you can pause your typing at that `|` to get a list of all exports and inline-documentation for each. It exports a separate [async](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function) function for each method in the smart contract, with documentation for each generated from the comments the contract's author included in the original source code.\n","readmeFilename":"README.md","_rev":"1-81b95d8f6d616a3b6f2cc890613d6484"}