{"_id":"@ableezz/numberspay_uwallet","name":"@ableezz/numberspay_uwallet","dist-tags":{"latest":"0.0.3"},"versions":{"0.0.3":{"version":"0.0.3","name":"@ableezz/numberspay_uwallet","type":"module","exports":"./dist/index.js","typings":"dist/index.d.ts","scripts":{"build":"tsc"},"dependencies":{"@stellar/stellar-sdk":"^13.x","buffer":"6.0.3"},"devDependencies":{"typescript":"^5.6.2"},"_id":"@ableezz/numberspay_uwallet@0.0.3","gitHead":"c944baef5f7d509f97f5f1153389451f4558f24c","description":"JS library for interacting with [Soroban](https://soroban.stellar.org/) smart contract `numberspay_uwallet` via Soroban RPC.","_nodeVersion":"22.11.0","_npmVersion":"11.0.0","dist":{"integrity":"sha512-eVb7bIFwCPP++b39ZycfEERaIGEtyp/BB5edxlDgwyrkHbCxY5TJu67HBc3vrpy3Uk9B4ZTBUOl5qD7zcB4K4A==","shasum":"f5e449e3f71e17e2b1ab2e1d5555de62607d15d7","tarball":"https://registry.npmjs.org/@ableezz/numberspay_uwallet/-/numberspay_uwallet-0.0.3.tgz","fileCount":6,"unpackedSize":48850,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIQCwCjX+EIcTM/BjNKXD+hFvjw0x9oIMLbDJPoYoxOnAkQIge9zyPr0841lYbGaMdKygWOFom2A7aGcVXrtSdbKNuu0="}]},"_npmUser":{"name":"ableezdev","email":"djayableez@gmail.com"},"directories":{},"maintainers":[{"name":"ableezdev","email":"djayableez@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/numberspay_uwallet_0.0.3_1752375108536_0.2368911214199323"},"_hasShrinkwrap":false}},"time":{"created":"2025-07-13T02:51:48.149Z","0.0.3":"2025-07-13T02:51:48.718Z","modified":"2025-07-13T02:51:49.042Z"},"maintainers":[{"name":"ableezdev","email":"djayableez@gmail.com"}],"description":"JS library for interacting with [Soroban](https://soroban.stellar.org/) smart contract `numberspay_uwallet` via Soroban RPC.","readme":"# numberspay_uwallet JS\r\n\r\nJS library for interacting with [Soroban](https://soroban.stellar.org/) smart contract `numberspay_uwallet` via Soroban RPC.\r\n\r\nThis library was automatically generated by Soroban CLI using a command similar to:\r\n\r\n```bash\r\nsoroban contract bindings ts \\\r\n  --rpc-url https://soroban-testnet.stellar.org \\\r\n  --network-passphrase \"Test SDF Network ; September 2015\" \\\r\n  --contract-id CD3Z5C3PAF4IUYTKYYI2CB6VGQARX4B244EL7KWIRK5CHR6ODG55WDGA \\\r\n  --output-dir ./path/to/numberspay_uwallet\r\n```\r\n\r\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.\r\n\r\n# To publish or not to publish\r\n\r\nThis library is suitable for publishing to NPM. You can publish it to NPM using the `npm publish` command.\r\n\r\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:\r\n\r\n```json\r\n\"dependencies\": {\r\n  \"numberspay_uwallet\": \"./path/to/this/folder\"\r\n}\r\n```\r\n\r\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.\r\n\r\n```json\r\n\"scripts\": {\r\n  \"postinstall\": \"soroban contract bindings ts --rpc-url https://soroban-testnet.stellar.org --network-passphrase \\\"Test SDF Network ; September 2015\\\" --id CD3Z5C3PAF4IUYTKYYI2CB6VGQARX4B244EL7KWIRK5CHR6ODG55WDGA --name numberspay_uwallet\"\r\n}\r\n```\r\n\r\nObviously you need to adjust the above command based on the actual command you used to generate the library.\r\n\r\n# Use it\r\n\r\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:\r\n\r\n```js\r\nimport { Contract, networks } from \"numberspay_uwallet\"\r\n\r\nconst contract = new Contract({\r\n  ...networks.futurenet, // for example; check which networks this library exports\r\n  rpcUrl: '...', // use your own, or find one for testing at https://soroban.stellar.org/docs/reference/rpc#public-rpc-providers\r\n})\r\n\r\ncontract.|\r\n```\r\n\r\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.\r\n","readmeFilename":"README.md","_rev":"1-bbc0a615db46a747cb3d022edcc5f747"}