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

@feedlify/target-git

v0.0.2

Published

Keeps up-to-date a @feedlify repository from a git compatible location

Downloads

1

Readme

@feedlifly/target-fs

======================

This module is capable of updating a repository that lies on the local file system

yarn add @feedlify/target-fs

You can use target-fs to update a repository:

import targetFs from '@feedlify/target-fs
const report = await targetFs('/repo-root')

The file structure should be something like:

index.json
feed1/
  feed.json
  index.json
  data/
    0000.json
    0001.json
feed2/
  ...

Basically a repository is a list of feed, each feed is a list of origins. At every level there is an index.json file that contains informations regarding the level itself.

At the root of the repository the index.json lists the available feeds:

{
  "feeds": [
    {
      "ref": "general",
      "name": "general",
      "ctime": "2019-04-06T09:54:08.235Z",
      "mtime": "2019-04-06T12:09:10.946Z",
      "from": "2019-03-02T18:20:20.000Z",
      "to": "2019-04-05T16:07:26.000Z",
      "count": 156,
      "data_files_count": 3
    },
    {
      "ref": "tech",
      "name": "tech",
      "ctime": "2019-04-06T11:41:18.489Z",
      "mtime": "2019-04-06T12:09:10.948Z",
      "from": "2019-03-02T18:20:20.000Z",
      "to": "2019-04-05T16:07:26.000Z",
      "count": 104,
      "data_files_count": 2
    }
  ]
}

Inside each feed folder we find the feed.json which contains the list of the origins to be fetched, as well as the rules to apply.

All the data that is collected during updates is then stored into the /data folder in json files named by date.

Another index.json helps listing all the available data files:

{
  "ctime": "2019-04-06T09:54:08.235Z",
  "mtime": "2019-04-06T12:09:10.946Z",
  "from": "2019-03-02T18:20:20.000Z",
  "to": "2019-04-05T16:07:26.000Z",
  "count": 156,
  "data": [
    {
      "ctime": "2019-04-06T12:09:10.945Z",
      "fname": "20190406020910.json",
      "from": "2019-03-02T18:20:20.000Z",
      "to": "2019-04-05T16:07:26.000Z",
      "count": 52
    },
    {
      "ctime": "2019-04-06T09:54:08.235Z",
      "fname": "20190406115408.json",
      "from": "2019-03-02T18:20:20.000Z",
      "to": "2019-04-05T16:07:26.000Z",
      "count": 52
    },
    {
      "ctime": "2019-04-06T08:42:01.392Z",
      "fname": "20190406104201.json",
      "from": "2019-03-02T18:20:20.000Z",
      "to": "2019-04-05T16:07:26.000Z",
      "count": 52
    }
  ]
}

Using this index file is then possible to build the full dataset for a given feed.