What is this?
Partytown is a lazy-loaded library that relocates resource-intensive third-party scripts off the main thread and into a web worker, so your own code gets the main thread.
Partytown is a lazy-loaded library that relocates resource-intensive third-party scripts off the main thread and into a web worker, so your own code gets the main thread.Is it a framework or a library?It is a library you drop into a webpage, not a framework; it hooks third-party ` ` tags and proxies their DOM access into a web worker.
It is a library you drop into a webpage, not a framework; it hooks third-party ` ` tags and proxies their DOM access into a web worker.How do I add it to a project?You add Partytown to your site following the Getting Started guide, and there are ready-made integrations for popular frameworks and page builders.
You add Partytown to your site following the Getting Started guide, and there are ready-made integrations for popular frameworks and page builders.What do I need to run or build it?It requires Node >=18 to build/develop; for a web page you just include Partytown's worker script, no backend dependencies are listed.
It requires Node >=18 to build/develop; for a web page you just include Partytown's worker script, no backend dependencies are listed.Does it work for every third-party script out of the box?No — the project is explicitly still in beta and not guaranteed to work in every scenario, with documented trade-offs to review before relying on it.
No — the project is explicitly still in beta and not guaranteed to work in every scenario, with documented trade-offs to review before relying on it.Where does this run — in the browser?It runs entirely in the browser, using a web worker as the execution environment for the offloaded scripts.
It runs entirely in the browser, using a web worker as the execution environment for the offloaded scripts.What kinds of scripts is this meant for?Typically analytics, ads, and other third-party embeds that are heavy but not part of your core app logic — moving them to a worker keeps the main thread free for your own code.
Typically analytics, ads, and other third-party embeds that are heavy but not part of your core app logic — moving them to a worker keeps the main thread free for your own code.Why does moving scripts to a web worker help performance?Scripts running on the main thread compete with your app's rendering and interactivity; Partytown proxies DOM access so these scripts execute in a web worker instead, improving metrics like Lighthouse and Core Web Vitals.
Scripts running on the main thread compete with your app's rendering and interactivity; Partytown proxies DOM access so these scripts execute in a web worker instead, improving metrics like Lighthouse and Core Web Vitals.Are there ready-made integrations for popular frameworks?Yes, Partytown ships an Integrations section covering common setups so you don't have to wire the worker proxying by hand.
Yes, Partytown ships an Integrations section covering common setups so you don't have to wire the worker proxying by hand.What are similar projects?rrweb, Fuse, velocity, better-scroll, virtual-dom, highlight.js, ua-parser-js, uPlot
rrweb, Fuse, velocity, better-scroll, virtual-dom, highlight.js, ua-parser-js, uPlotWhich topics is it in?core-web-vitals, web-worker, dom, analytics, browser, performance, productivity, frontend, library, typescript, javascript, web
core-web-vitals, web-worker, dom, analytics, browser, performance, productivity, frontend, library, typescript, javascript, web