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

@webhandle/page-locator

v1.0.1

Published

Downloads

8

Readme

@webhandle/page-locator

Finds "pages" within a directory by examining a url. A page is a template and an optional metadata file which corresponds to a url. The template may be selected in one of three ways.

  1. The URL is exactly the name of the template. This would be a url like /products/my-cool-product.html or /products/my-cool-product.tri. This method finds the template and metadata but does NOT look for alternatives (more on that later).

  2. The URL refers to a directory. This would be something like /products. In this case the directory will be searched for the first file matching one of the index bases names this.indexNames and having a valid extension this.templateExtensions. The resulting template is likely to have a relative path like products/index.html. Metadata and alternatives will be found.

  3. The URL refers to a "page" but not a specific file (the typical case). This would be a URL like /products/my-cool-product. Here the PageLocator trys to find a matching file in the parent directory (/products in this example). This file will be any file with the base name (like my-cool-product) and an extension from this.templateExtensions. Metadata and alternatives will be found.

Alternatives are alternate version of the page for different purposes or environments. Common uses might be for a/b testing or for having the same "page" available in different languages. Which alternative is actually used is up to the calling component.

Install

npm install @webhandle/page-locator

Usage

import FileSink from 'file-sink'
import PageLocator from '@webhandle/page-locator'

let sink = new FileSink('/path/to/page/data')
let locator = new PageLocator({
	sink
})


let info = await locator.locate('/')
// or
info = await locator.locate('/two.html')
// or
info = await locator.locate('/three/four')

info is a structure that looks like:

{
	template: 'index.tri',
	alternatives: {
		en: {
			template: 'index_en.tri',
			metadata: 'index_en.json',
			metadataExists: false
		}
	},
	metadata: 'index.json',
	metadataExists: true
}	

Options

import FileSink from 'file-sink'
import PageLocator from '@webhandle/page-locator'

let sink = new FileSink('/path/to/page/data')
let locator = new PageLocator({
	sink: sink  					// A FileSink object
	, indexNames: ['index']			// basenames of directory index files
	, templateExtensions: ['tri', 'html']	// extensions for template files
})