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

@bcgov/gatsby-source-matomo

v0.0.5

Published

Plugin that generates a set of nodes based off Matomo analytics

Downloads

9

Readme

Gatsby Source Matomo

Load page data as source nodes

Features

  • Page URL information including visits, hits, bounce rate etc.

Quirks

Although the Matomo API claims to be 'restful', it is far from that. For the initial implementation of this plugin, only page information is retrieved by via default method Action.getPageUrls api reference

This can be overridden to your liking with the apiOptions option

To Use

  • Install npm install --save @bcgov/gatsby-source-matomo
  • Add to your gatsby config
{
  resolve: 'gatsby-source-matomo',
  options: {
    matomoApiToken: '...',
    matomoUrl: '...',
    siteId: '...'
    apiOptions:  {...}, // overrides for the matomo api
  }
}

Options

  • matomoApiToken: this is the access token
  • matomoUrl: the path to your Matomo instance (https://my-matomo-site.com)
  • siteId: the site id you want to get information from
  • apiOptions: an object to override the query to the matomo api.
//...
resolve: 'gatsby-source-matomo',
options: {
  apiOptions: {
    period: '..',
    date: '..',
    method: 'foo'
    // etc
  }
}

Road Map

The initial implementation default to getting page urls, this plus the overridability with the apiOptions field makes this plugin fairly flexible. I am happy to take PR's on extending the capability of this plugin

  • add support to recurse through page urls. Matomo only provides page urls one section at a time. At this time we only support 1 level nested page paths.

  • https://mysite.com/path1/path2/path3 > will not get path3 stats

Disclaimer when overriding with ApiOptions

There is no implementation detail to change the Node Type during an override so be careful with that!