Download the PHP package clarkewing/cashier-nightwatch without Composer
On this page you can find all versions of the php package clarkewing/cashier-nightwatch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download clarkewing/cashier-nightwatch
More information about clarkewing/cashier-nightwatch
Files in clarkewing/cashier-nightwatch
Package cashier-nightwatch
Short Description Surface Laravel Cashier (Stripe) API requests on Laravel Nightwatch timelines.
License MIT
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 cashier-nightwatch
Cashier Nightwatch
Surface Stripe API requests — those made by Laravel Cashier and the Stripe PHP SDK — on your Laravel Nightwatch timelines, with the request URL redacted by default.
Stripe's PHP SDK uses its own cURL client, so its API calls bypass Nightwatch's Guzzle instrumentation and never show up on your timelines. This package swaps in a Nightwatch-aware cURL client so they do.
Installation
The service provider is auto-discovered. To customise redaction, publish the config:
What is recorded — and redacted
Nightwatch stores only the method, URL, byte sizes and status code for an outgoing request — never request/response headers or bodies. Consequently:
- Your Stripe secret key (the
Authorizationheader) is never captured. - Request/response bodies (card data, customer PII on writes) are never captured — only their byte size.
- The URL is the only sensitive surface, because Stripe
list/searchcalls put filters such asemailorcustomerin the query string.
By default the package redacts query-string values while keeping the keys:
Configuration
| Key | Default | Description |
|---|---|---|
enabled |
true |
Master switch. No-ops if Nightwatch is not installed. |
redact_query |
keys |
keys (redact values, keep names)drop (remove the query string)keep (leave as-is — may log PII). |
mask_path_ids |
false |
Mask Stripe IDs in the path, e.g. /v1/customers/cus_***. |
Each maps to an env var: CASHIER_NIGHTWATCH_ENABLED, CASHIER_NIGHTWATCH_REDACT_QUERY, CASHIER_NIGHTWATCH_MASK_PATH_IDS.
For full control you can also use Nightwatch's own hook in a service provider (the record's url is mutable):
Compatibility
This integrates at the Stripe SDK level (Stripe\ApiRequestor::setHttpClient) and relies on a few Laravel Nightwatch internals (Core::$clock, Core::$config, outgoingRequest(), paused()). It targets Nightwatch 1.x and may need updating across a Nightwatch major version.
Streaming Stripe responses (requestStream) are not instrumented.
Testing
License
MIT — see LICENSE.
All versions of cashier-nightwatch with dependencies
guzzlehttp/psr7 Version ^2.0
illuminate/support Version ^12.0 || ^13.0
laravel/nightwatch Version ^1.0
psr/http-message Version ^1.1 || ^2.0
stripe/stripe-php Version ^16.0 || ^17.0