Skip to content

chore(deps): bump casper-js-sdk from 5.0.12 to 5.1.1 in /agent/x402 - #92

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/agent/x402/casper-js-sdk-5.1.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/agent/x402/casper-js-sdk-5.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown

Bumps casper-js-sdk from 5.0.12 to 5.1.1.

Release notes

Sourced from casper-js-sdk's releases.

Casper JS SDK v5.1.1

Fixed

  • Named imports now work from Node.js ESM: import { RpcClient, Transaction } from 'casper-js-sdk' previously threw SyntaxError: Named export not found, forcing ESM consumers through createRequire or a default-import destructure. The node bundle is now emitted as statically analyzable CommonJS (commonjs-static instead of UMD), so Node's loader can see every named export. require() consumers are unaffected — the file is still CommonJS with an identical export surface

Changed

  • dist/lib.node.js is no longer a UMD bundle. It is plain CommonJS, so require(), bundlers and every path through the exports map behave as before — but loading that file through an AMD loader such as RequireJS, or as a <script> tag expecting a browser global, no longer works. Browser and React Native consumers resolve to dist/lib.web.js through the browser and exports conditions, and that bundle is still UMD

Full Changelog: casper-ecosystem/casper-js-sdk@5.1.0...5.1.1

Contributors: @​Comp0te

Casper JS SDK v5.1.0

No runtime or API change — dist/ behaves exactly as in 5.0.13 and engines.node stays ">=18". The rest of the release is an internal toolchain update with no effect on consumers.

Changed

  • Production dependencies bumped within their majors, with no source change: @ethersproject/{bignumber,bytes,constants}, @noble/{curves,hashes,ed25519,secp256k1}, bn.js, humanize-duration, ts-results and typedjson

Removed

  • Unused production dependencies node-fetch, @scure/bip32 and @scure/bip39, shrinking the installed dependency tree
  • reflect-metadata. The SDK never took typedjson's reflection path — every decorator declares its type explicitly — so nothing in dist/ needs it. Consumers who relied on the SDK to pull reflect-metadata into their own tree must now declare it themselves

Full Changelog: casper-ecosystem/casper-js-sdk@5.0.13...5.1.0

Contributors: @​Comp0te

Casper JS SDK v5.0.13

Changed

  • Restricted the published package to dist, resources, README.md, CHANGELOG.md and LICENSE via a files whitelist — the docs site, CI workflows and build configs no longer ship
  • Raised axios to ^1.19.0, the brace-expansion override to ^5.0.9 and form-data to 4.0.6, and fully regenerated package-lock.json. No source change was required

Removed

  • Unused glob production dependency, and with it the abandoned inflight and the rest of its transitive tree

Fixed

  • Security vulnerabilities in production dependencies

... (truncated)

Changelog

Sourced from casper-js-sdk's changelog.

[5.1.1] - 2026-09-02

Fixed

  • Named imports now work from Node.js ESM: import { RpcClient, Transaction } from 'casper-js-sdk' previously threw SyntaxError: Named export not found, forcing ESM consumers through createRequire or a default-import destructure. The node bundle is now emitted as statically analyzable CommonJS (commonjs-static instead of UMD), so Node's loader can see every named export. require() consumers are unaffected — the file is still CommonJS with an identical export surface

Changed

  • dist/lib.node.js is no longer a UMD bundle. It is plain CommonJS, so require(), bundlers and every path through the exports map behave as before — but loading that file through an AMD loader such as RequireJS, or as a <script> tag expecting a browser global, no longer works. Browser and React Native consumers resolve to dist/lib.web.js through the browser and exports conditions, and that bundle is still UMD

[5.1.0] - 2026-08-11

No runtime or API change — dist/ behaves exactly as in 5.0.13 and engines.node stays ">=18". The rest of the release is an internal toolchain update with no effect on consumers.

Changed

  • Production dependencies bumped within their majors, with no source change: @ethersproject/{bignumber,bytes,constants}, @noble/{curves,hashes,ed25519,secp256k1}, bn.js, humanize-duration, ts-results and typedjson

Removed

  • Unused production dependencies node-fetch, @scure/bip32 and @scure/bip39, shrinking the installed dependency tree
  • reflect-metadata. The SDK never took typedjson's reflection path — every decorator declares its type explicitly — so nothing in dist/ needs it. Consumers who relied on the SDK to pull reflect-metadata into their own tree must now declare it themselves

[5.0.13] - 2026-08-06

Changed

  • Restricted the published package to dist, resources, README.md, CHANGELOG.md and LICENSE via a files whitelist — the docs site, CI workflows and build configs no longer ship
  • Raised axios to ^1.19.0, the brace-expansion override to ^5.0.9 and form-data to 4.0.6, and fully regenerated package-lock.json. No source change was required

Removed

  • Unused glob production dependency, and with it the abandoned inflight and the rest of its transitive tree

Fixed

  • Security vulnerabilities in production dependencies
Commits
  • 2e9da26 Merge pull request #615 from casper-ecosystem/CSDK/esm-named-exports
  • 0866d81 Date the 5.1.1 entry and record the UMD bundle it drops
  • bbe7ac1 Emit the node bundle as commonjs-static so named ESM imports work
  • 02b743d Merge pull request #609 from casper-ecosystem/CSDK/changelog-5.1.0-date
  • ed4eb31 Date the 5.1.0 changelog entry to its release day
  • aac5e91 Merge pull request #607 from casper-ecosystem/CSDK/phase-2.5-release-engineering
  • f20a088 Fix the npm publish workflow
  • a6bbb62 Trim the 5.1.0 changelog entry to consumer-facing changes
  • 5c0153c Release 5.1.0 version
  • a0c8038 Apply the Prettier 3 reformat
  • Additional commits viewable in compare view
Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [casper-js-sdk](https://github.com/casper-ecosystem/casper-js-sdk) from 5.0.12 to 5.1.1.
- [Release notes](https://github.com/casper-ecosystem/casper-js-sdk/releases)
- [Changelog](https://github.com/casper-ecosystem/casper-js-sdk/blob/dev/CHANGELOG.md)
- [Commits](casper-ecosystem/casper-js-sdk@5.0.12...5.1.1)

---
updated-dependencies:
- dependency-name: casper-js-sdk
  dependency-version: 5.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies, security. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 7, 2026

Copy link
Copy Markdown

Deploying lastre-app with  Cloudflare Pages  Cloudflare Pages

Latest commit: 52969f1
Status: ✅  Deploy successful!
Preview URL: https://5df4b704.lastre-app.pages.dev
Branch Preview URL: https://dependabot-npm-and-yarn-agen-9azv.lastre-app.pages.dev

View logs

@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
lastro Ready Ready Preview Sep 7, 2026 9:46am UTC

Request Review

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 7, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
lastre 52969f1 Sep 07 2026, 09:47 AM

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying lastro with  Cloudflare Pages  Cloudflare Pages

Latest commit: 52969f1
Status: ✅  Deploy successful!
Preview URL: https://5b54309b.lastro-296.pages.dev
Branch Preview URL: https://dependabot-npm-and-yarn-agen-z8re.lastro-296.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants