
Security News
New CVE Forecasting Tool Predicts 47,000 Disclosures in 2025
CVEForecast.org uses machine learning to project a record-breaking surge in vulnerability disclosures in 2025.
await-interaction-response
Advanced tools
Improve [INP (Interaction to Next Paint)](https://web.dev/articles/inp) by allowing the browser to paint before blocking the main thread. You can test how it works in the [live demo](https://await-interaction-response.vercel.app/).
Improve INP (Interaction to Next Paint) by allowing the browser to paint before blocking the main thread. You can test how it works in the live demo.
You can learn more about INP and this package in our blog: Demystifying INP: New tools and actionable insights.
Install the package:
pnpm add await-interaction-response
npm install await-interaction-response
yarn add await-interaction-response
Next, add awat interactionResponse()
to interactions that have a bad INP:
import interactionResponse from 'await-interaction-response';
<input
type="text"
value={value}
onChange={async (e) => {
setValue(e.target.value);
await interactionResponse();
expensiveMainThreadWork();
}}
/>;
Generally, add await interactionResponse()
in places where you're having INP issues and when your UI library solutions (like React's startTransition
) aren't enough for your use case.
So a first step is to monitor for INP issues in development with tools like the Vercel Toolbar or the chrome web-vitals extension and in production with services like Vercel Speed Insights that do RUM.
Your INP score is affected when the browser does not have time to update the UI after an user interaction. A common cause is executing JavaScript in the main thread for longer periods of time. To prevent this, you'll want to delay executing JavaScript code unrelated to the UI change until the main thread is free to handle it.
Therefore, await-interaction-response
simply forces you to wait and gives the browser time to commit the UI change. This helps improve INP in situations where JavaScript is the culprit.
interactionResponse
is a function with 8 lines of code that waits until the next animation frame to start a 0
time out, which delays resolving its promise to the end of the queue in the event loop. Once called the promise resolves and execution continues to the rest of your JS code.
FAQs
Improve [INP (Interaction to Next Paint)](https://web.dev/articles/inp) by allowing the browser to paint before blocking the main thread. You can test how it works in the [live demo](https://await-interaction-response.vercel.app/).
The npm package await-interaction-response receives a total of 5,458 weekly downloads. As such, await-interaction-response popularity was classified as popular.
We found that await-interaction-response demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CVEForecast.org uses machine learning to project a record-breaking surge in vulnerability disclosures in 2025.
Security News
Browserslist-rs now uses static data to reduce binary size by over 1MB, improving memory use and performance for Rust-based frontend tools.
Research
Security News
Eight new malicious Firefox extensions impersonate games, steal OAuth tokens, hijack sessions, and exploit browser permissions to spy on users.