Download the PHP package pushinbr/pam-native-devtools without Composer
On this page you can find all versions of the php package pushinbr/pam-native-devtools. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pushinbr/pam-native-devtools
More information about pushinbr/pam-native-devtools
Files in pushinbr/pam-native-devtools
Package pam-native-devtools
Short Description Deterministic temporal replay, state, network and frame diagnostics for PAM Native.
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pam-native-devtools
Why PAM Native DevTools
Inspect timelines, snapshots, network activity, and performance marks with bounded, redacted evidence suitable for development and CI. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
| Best for | A focused capability you can add to any PAM Native application |
| Native path | Deterministic temporal recorder · Native overlays |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Time-travel debugging for signals and actions
- Network and native-event inspection
- Frame-jank investigation and reproducible bug reports
Quick start
Already have a PAM Native project? Add only this capability:
New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.
See it in action
A deterministic, bounded diagnostic recorder for PAM Native development: application events, serializable state snapshots, performance marks, errors, and complete network transactions. Export one JSON artifact for bug reports or CI regressions without coupling production apps to a visual UI.
Sensitive keys are redacted recursively, object depth and collection size are bounded, strings are truncated, and the oldest records are discarded under pressure. The package complements PAM's native debug overlay and navigation timeline; it does not ship UI into production applications.
What installation does
pam composer require pushinbr/pam-native-devtools installs the package through the project's normal composer.json and composer.lock. Run pam doctor --fix afterward to validate the environment and regenerate native integration when required.
Use pam packages to inspect direct installed Composer dependencies and pam composer remove pushinbr/pam-native-devtools to uninstall the capability.
API guide
| API | Responsibility |
|---|---|
DevTools |
Record events, mutations, snapshots, frames, marks, measures, errors, and network work. |
NetworkTransaction |
Complete or fail a captured request lifecycle. |
Redactor |
Bound and recursively redact diagnostic values. |
TimelineRecording |
Validate and serialize the bounded, versioned replay artifact. |
ReplaySession |
Step, seek, time travel to state, or replay the timeline deterministically. |
RecordKind / NetworkState |
Typed diagnostic record states. |
All coded states, kinds, and variants are sequential integer-backed enums. Use enum cases in application code; do not depend on raw wire numbers.
Production checklist
- Keep DevTools in development and diagnostic builds.
- Add product-specific sensitive keys to redaction rules.
- Attach exported JSON to reproducible bug reports, never public issue bodies without review.
- Run
pam doctor,pam test, and a signed release build on every supported platform. - Exercise denial, cancellation, backgrounding, process restart, and offline behavior before release.
Troubleshooting
- Records disappear: the buffer intentionally drops oldest entries under pressure.
- Values are truncated: increase detail only when the privacy and size trade-off is acceptable.
- A request remains open: always call
complete()orfail(). - Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PAM Native 0.8.x, PHP 8.5, Android API 26+, and iOS 15+ unless a platform-specific section above states a stricter requirement. Platform SDKs, credentials, entitlements, physical hardware, and store configuration remain application responsibilities.
Security vulnerabilities should be reported through the repository security policy or GitHub private vulnerability reporting, not a public issue.
All versions of pam-native-devtools with dependencies
ext-json Version *
pushinbr/pam-native Version ^0.8 || ^0.9 || ^0.10 || ^1.0