A JavaScript library to observe Page Lifecycle API states: https://github.com/WICG/page-lifecycle
A JavaScript library to observe Page Lifecycle API states: https://github.com/WICG/page-lifecycle
Page Lifecycle hook for react
Network / page-lifecycle / JS-runtime fault injection primitives for Playwright. Extracted from chaosbringer.
Public WebBuilder SDK package for page lifecycle APIs, template APIs, media APIs, and transport helpers.
The page lifecycle provider introduces a concept of page lifecycles to route changes. The useful scenario is to raise an event when navigations happen (easy using react-router already), then raise another event once all the data has been loaded for that r
Lightweight async task scheduling and concurrency control: schedulers, idle/frame/limited queues, throttle, debounce, batch, page lifecycle, random delays. Browsers, Node.js, Deno, Bun.
A little add to tgwf/co2 to calculate co2 of front at all stage of the page lifecycle
Cloudflare Browser Rendering primitive — session/page lifecycle, font loading, normalized errors
ESLint plugin for Angular applications, following https://angular.dev/style-guide
A set of general utilities for the lifecycle of a JS/TS project/library
A swup plugin for animating the previous and next page in parallel
An iteration of the Node.js core streams with a series of improvements
JavaScript package lifecycle hook runner
Headed Playwright browser with React DevTools pre-loaded
Contains a programmatic library for managing the Amplify sandbox lifecycle. The sandbox lifecycle includes starting a file watching process that kicks off deployments on file changes. The backend-deployer is used for executing these deployments. The sandb
HTTP daemon and CLI for agent-driven browser extension testing with Playwright
The Unleash Proxy (Open-Source)
Event and disposable helpers.
XMLHttpRequest mock for testing
[](https://www.npmjs.com/package/@adyen/adyen-web)
Declarative, nested, stateful, isomorphic page visibility for React
Honeycomb OpenTelemetry Wrapper for Browser Applications
Implements did-insert / did-update / will-destroy modifiers for Ember.js
An authentication gem for the pre-production (mainly) phase of the application lifecycle. Provide a simple sign in page with a list of all users in the application. Click on any user logins you to the application under the user.
Bidi2pdf Rails provides a seamless integration between Rails and the Bidi2pdf gem for generating high-quality PDFs using Chrome/Chromium's headless browser. It supports rendering PDFs from controller actions, remote URLs, or HTML strings with configurable options for orientation, margins, page size, and more. The gem handles browser lifecycle management and provides a clean API for PDF generation with proper asset handling.
Docsmith adds snapshot-based versioning to any ActiveRecord model with zero system dependencies. • Full content snapshots (HTML, Markdown, JSON) for instant rollbacks • Format-aware diff engine: word-level diffs for Markdown, tag-atomic diffs for HTML • Document-level and range-anchored comments with threading and version migration • Per-class configuration, debounced auto-save, lifecycle events, and a clean API Perfect for wikis, CMS pages, API specs, legal documents, or any content that needs an audit trail and inline collaboration.
# Quick Start The Owner API uses the JSON format, and must be accessed over a [secure connection](https://en.wikipedia.org/wiki/HTTPS). Let’s assume that the access token provided by your account manager is “TOKEN”. Here’s how to get the list of ids of all your invoices from the first week of August with a shell script: ```bash query="end_date=2018-08-08T00%3A00%3A00%2B00%3A00&start_date=2018-08-01T00%3A00%3A00%2B00%3A00" curl -i "https://api-eu.getaround.com/owner/v1/invoices?${query}" \ -H "Authorization: Bearer TOKEN" \ -H "Accept:application/json" \ -H "Content-Type:application/json" ``` And here’s how to get the invoice with the id 12345: ```bash curl -i "https://api-eu.getaround.com/owner/v1/invoices/12345" \ -H "Authorization: Bearer TOKEN" \ -H "Accept: application/json" \ -H "Content-Type: application/json"" ``` See the [endpoints section](#tag/Invoices) of this guide for details about the response format. Dates in request params should follow the ISO 8601 standard. # Authentication All requests must be authenticated with a [bearer token header](https://tools.ietf.org/html/rfc6750#section-2.1). You token will be sent to you by your account manager. Unauthenticated requests will return a 401 status. # Pagination The page number and the number of items per page can be set with the “page” and “per_page” params. For example, this request will return the second page of invoices, and 50 invoices per page: `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` Both of these params are optional. The default page size is 30 items. The Getaround Owner API follows the [RFC 8288 convention](https://datatracker.ietf.org/doc/html/rfc8288) of using the `Link` header to provide the `next` page URL. Please don't build the pagination URLs yourself. The `next` page will be missing when you are requesting the last available page. Here's an example response header from requesting the second page of invoices `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` ``` Link: <https://api-eu.getaround.com/owner/v1/invoices?page=3&per_page=50>; rel="next" ``` # Throttling policy and Date range limitation We have throttling policy that prevents you to perform more than 100 requests per min from the same IP. Also, there is a limitation on the size of the range of dates given in params in some requests. All requests that need start_date and end_date, do not accept a range bigger than 30 days. # Webhooks Getaround can send webhook events that notify your application when certain events happen on your account. This is especially useful to follow the lifecycle of rentals, tracking for example bookings or cancellations. ### Setup To set up an endpoint, you need to define a route on your server for receiving events, and then <a href="mailto:owner-api@getaround.com">ask Getaround</a> to add this URL to your account. To acknowledge receipt of a event, your endpoint must: - Return a `2xx` HTTP status code. - Be a secure `https` endpoint with a valid SSL certificate. ### Testing Once Getaround has set up the endpoint, and it is properly configured as described above, a test `ping` event can be sent by clicking the button below: <form action="/docs/api/owner/fire_ping_webhook" method="post"><input type="submit" value="Send Ping Event"></form> You should receive the following JSON payload: ```json { "data": { "ping": "pong" }, "type": "ping", "occurred_at": "2019-04-18T08:30:05Z" } ``` ### Retries Webhook deliveries will be attempted for up to three days with an exponential back off. After that point the delivery will be abandoned. ### Verifying Signatures Getaround will also provide you with a secret token, which is used to create a hash signature with each payload. This hash signature is passed along with each request in the headers as `X-Drivy-Signature`. Suppose you have a basic server listening to webhooks that looks like this: ```ruby require 'sinatra' require 'json' post '/payload' do push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end ``` The goal is to compute a hash using your secret token, and ensure that the hash from Getaround matches. Getaround uses an HMAC hexdigest to compute the hash, so you could change your server to look a little like this: ```ruby post '/payload' do request.body.rewind payload_body = request.body.read verify_signature(payload_body) push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end def verify_signature(payload_body) signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body) return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_DRIVY_SIGNATURE']) end ``` Obviously, your language and server implementations may differ from this code. There are a couple of important things to point out, however: No matter which implementation you use, the hash signature starts with `sha1=`, using the key of your secret token and your payload body. Using a plain `==` operator is not advised. A method like secure_compare performs a "constant time" string comparison, which renders it safe from certain timing attacks against regular equality operators. ### Best Practices - **Acknowledge events immediately**. If your webhook script performs complex logic, or makes network calls, it’s possible that the script would time out before Getaround sees its complete execution. Ideally, your webhook handler code (acknowledging receipt of an event by returning a `2xx` status code) is separate of any other logic you do for that event. - **Handle duplicate events**. Webhook endpoints might occasionally receive the same event more than once. We advise you to guard against duplicated event receipts by making your event processing idempotent. One way of doing this is logging the events you’ve processed, and then not processing already-logged events. - **Do not expect events in order**. Getaround does not guarantee delivery of events in the order in which they are generated. Your endpoint should therefore handle this accordingly. We do provide an `occurred_at` timestamp for each event, though, to help reconcile ordering.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.