mirror of
https://github.com/luxfi/bundler.git
synced 2026-10-30 17:01:04 +00:00
zeekay
907787570e
A version written into a manifest is written into every manifest that wants it, which is how eslint came to exist in a hundred and four forms across this estate and how a package came to resolve twice at run time. The catalog moves the number out of the manifest: a manifest names the package, the workspace names the version. Four are held below their latest because the newer release cannot be used, and the reason is recorded rather than the version alone: @noble/hashes 2 renamed every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels 3 points its types condition at the bundle.
SDK to check if the validation code of a UserOperation violates any validation rules
Usage
In order to check the UserOperation you have created, use the code below.
This is especially useful if you are developing a custom Account or Paymaster contract,
overriding the validateUserOp, validatePaymasterUserOp, or expect your contracts' code to
be called from these methods within the ERC-4337 transaction context.
import { UserOperation } from '@account-abstraction/utils'
import { checkRulesViolations } from '@account-abstraction/validation-manager'
const userOperation: UserOperation = createUserOp()
await checkRulesViolations(provider, userOperation, entryPoint)