Public Release Tasks

[harlan-zw]

These are several items that should be completed for the public release of the module. Any contributions are more than welcome.

Tasks for the public announcement: https://github.com/nuxt/scripts/issues/47

Nuxt

• [x] Add stub for useScript to Nuxt core (https://github.com/nuxt/nuxt/pull/26854 & https://github.com/nuxt/nuxt/pull/27010#issue-comment-box)

Benchamarks

• [x] See what the overhead of using registry script is - 2.09kb gzipped for fathom analytics
• [x] Test web vitals & PSI with / without useScript - not meaningful by itself, too much variability

Documentation

Content

(some content exists on all these pages it just needs polishing)

Getting started

• [x] Introduction
• [x] Installation
• [x] Tutorial: js-confetti
• [x] Reproductions - add a stackblitz demo repo

Guides

• [x] Script Loading
• [x] Script Triggers
• [x] Bundling
• [x] Consent
• [x] Page Events
• [x] Global Scripts

API

• [x] useScript
• [x] createConsentScriptTrigger
• [x] useElementScriptTrigger
• [x] useAnalyticsPageEvent
• [x] Nuxt Config
• [x] Nuxt App Hooks
• [x] Nuxt Hooks

Registry

(see below)

Read Me

• [x] Better background details, more concise and informative.

Home Page

• [x] Benchmarks

Nuxt Scripts

Tests

• [x] Consuming module

  • [x] Playground installing module externally working
  • [x] Generate
  • [x] Build
  • [x] StackBlitz working

• [x] e2e Trigger tests

  • [x] onNuxtReady
  • [x] manual
  • [x] visibility
  • [x] mouseover

Registry Scripts

The initial implementation for all of these scripts is complete. No new scripts should be added at this stage.

The below require proper documentation and sanity checks on implementation. There is some tree-shaking improvements to be made, see Cloudflare Web Analytics example as it's complete.

We also need to properly document which scripts can be bundled.

Analytics

• [x] cloudflare-web-analytics
• [x] fathom-analytics
• [x] google-analytics
• [x] matomo-analytics
• [x] plausible-analytics

Content

• [x] google-maps
• [x] vimeo-player
• [x] youtube-player

Marketing

• [x] intercom
• [x] hotjar

Payments

• [x] lemon-squeezy
• [x] stripe

Tracking

• [x] meta-pixel
• [x] google-tag-manager
• [x] segment
• [x] x-pixel

Util

• [x] npm
• [x] :question: Drop the confetti script and replace it with just a usage example of npm

[oritwoen]

From my own observation, it makes sense to add e2e tests for Registry Scripts to the list.

Especially when it comes to analytics, they like to "go crazy". I tried to run Google Analytics and use events but it didn't work at all, hence my suggestion to add tests to the registry as well.

Maybe I was doing something wrong in general (I was using the documentation). Anyway, this is a suggestion and if I still have a problem with it after updating the packages, I will make an issue and reproduce it.

[harlan-zw]

Thank you for the feedback @oritwoen. Unfortunately to do an e2e test with the registry scripts is not fully possible for all scripts, we can support it for registry scripts that expose an API to check the data we send it.

I've setup a Google Analytics Reproduction and it seems to be working correctly.

If you can provide the code you had an issue with or a reproduction it would help.

Also please make a new issue, I'm going to close this one :pray: