diff --git a/foomo/blog/2022-01-20-exploring-partytown/index.mdx b/foomo/blog/2022-01-20-exploring-partytown/index.mdx index b2198fc..16ad6b7 100644 --- a/foomo/blog/2022-01-20-exploring-partytown/index.mdx +++ b/foomo/blog/2022-01-20-exploring-partytown/index.mdx @@ -1,11 +1,74 @@ --- slug: exploring-partytown -authors: [ themre ] +authors: [ marko ] tags: [ nodejs, service-worker, gtm ] --- -# Exploring partytown +# Issue with performance +When building an ecommerce site or an application where performance is a great deal for the users, you need to keep your application fast and responsive. Frontend developers have already many use-cases when the UI becomes laggy and this increases when 3rd party scripts are being included, such as Google Tag Manager or various Live chats (e.g. Intercom). +This does not only influences the users when using the site but also Lighthouse score gets lower which also influences page rankings. So the most naive and easy way for this is to defer loading of such scripts but when you need to get all the data from the start of the application, such tactic is not an option. So what else can we do? +# Exploring Partytown +Developers at BuilderIO created an library [https://github.com/BuilderIO/partytown](Partytown) that would allow relocating resources from 3rd party scripts off the main thread. +We won't dive into specifics how it works, because they explain it nicely on their GitHub page. + +In our stack we use [https://nextjs.org/](Next.js) React framework and we will go through the basic steps that will allow us to include Partytown for Google Tag Manager. + +## Setup + +Partytown script needs to be located inside our application and live on the same domain. Since we're using monorepo structure, we need to copy this script across all our frontend application. For that we used CopyPlugin webpack plugin in our Next.js config file: + +```javascript +config.plugins.push( + ... + new CopyPlugin({ + patterns: [ + { + // we copy script from node_modules partytown package to `~partytown` folder in our package that serves static files + from: path.join(path.dirname(require.resolve('@builder.io/partytown')), 'lib'), + // paths for SSR and client side rendering differ + to: path.join(`${isServer ? '..' : '.'}/static/assets/`, '~partytown'), + }, + ], + }) + ); +``` + +Partytown's requirement is that it needs to know what script should it load into own web worker. For that we set script type to `text/partytown`. This will prevent script to load on initial load. + +Inside `_document.tsx` we add this: +```javascript + + ... + // include Partytown and set custom path due to multiple frontends + + // tag 3rd party script with partytown type +