npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@adobe/helix-rum-js

v2.10.0

Published

Helix RUM JS

Downloads

205,074

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mhaackmhaackamol-anandamol-ananddotendotenstopp-adobestopp-adobedylandepassdylandepassdjaeggidjaeggiadobehallsadobehallsfullcolorcoderfullcolorcodermarbecmarbectripodtripodgarthdbgarthdblazdlazdadobe-adminadobe-adminpatrickfultonpatrickfultontrielofftrieloffshazronshazronkrisnyekrisnyedcpfsdkdcpfsdknatebaldwinnatebaldwindevongovettdevongovettaspro83aspro83symanovisymanovidpfisterdpfisterstefan-guggisbergstefan-guggisbergkorrakorraroferofekptdobekptdobe

Keywords

Readme

AEM RUM JS

AEM RUM Event Generator for JavaScript

Status

codecov GitHub Actions GitHub license GitHub issues semantic-release

Instrument your website with RUM

If your website is not built using AEM Edge Delivery Services it is recommended to setup RUM in standalone mode.

To do it, simply add the following script to your pages.

<script defer type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@^2/dist/rum-standalone.js"></script>

If you want to instruct a 404 response, include the same script but set the status data attribute to 404.

<script defer type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@^2/dist/rum-standalone.js" data-status="404"></script>

If you understand the details of a high performance page, it might be advisable to load the script after the LCP event

Check the following link for advanced configuration options.

Also, you can instrument your website with RUM using Google Tag Manager

Content Security Policy

If your website implements a Content Security Policy it is important to ensure that the origin https://rum.hlx.page is allowed both as a script source and as a destination for navigator.sendBeacon API.

Testing the setup

  1. Access a page of your website where you have included the RUM script.

  2. Adding to the url the request parameter rum=on and reload the page

  3. Open browser console and check that ping messages are being written.

    ping-messages-in-console

  4. Open the network tab of your browser and validate that ping requests using POST method to domain rum.hlx.page are being sent and that the response status is 201

    rum-requests-in-network-tab

Edge Delivery Service Projects

Note that websites implemented with Adobe Edge Delivery Services, based on the boilerplate are already instrumented with RUM.

For more details about RUM in Edge Delivery Projects, upgrading from previous versions of RUM, or customization options, you can check the page RUM in Edge Delivery Services projects

Development

Build

$ npm install

Build standalone

$ npm run build-standalone

Test

$ npm test

Lint

$ npm run lint