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

trucks-resolver-core

v1.0.1

Published

Abstract import resolver class

Downloads

6

Readme

Resolver

Abstract HTML import resolver

Implementation contract for protocol resolver plugins.

Install

npm i trucks-resolver-core --save


Usage

Resolver plugin implementations should extend this class, see the file and http plugins for example implementations.

API

Resolver

Abstract protocol resolver.

Resolver plugin implementations should create a subclass of this class and invoke registry.register() with a protocol and the derived class.

Resolver

public Resolver(state, href[, parent])

Create a resolver.

The file property is initialized to the canonical path for the href argument.

  • state Object compiler state.
  • href String source URL to resolve.
  • parent Object a parent resolver.
Throws
  • TypeError attempting to parse a bad href argument.

protocol

String protocol

Get the protocol from the href assigned to this resolver, if no protocol is found lookup is performed in a parent hierarchy.

file

String file

Absolute computed path for the URL.

This is initialized to the canonical path for the href argument passed to the constructor but implementations may overwrite this.

resolve

public resolve(cb)

Resolve the contents for the URL.

Implementors should invoke callback with an error and Buffer contents or an object representing compiler options:

(err, contents) => {}.

When the callback is invoked with compiler options it is treated as a nested compile pass using the given options which should have an input files array.

  • cb Function callback function.

getCanonicalPath

public getCanonicalPath()

Get a canonical path for the URL, used to determine if the resource has already been processed.

Typically implementors would convert this to an absolute path or absolute URL to ensure that duplicates can be resolved.

Returns the canonical file path to resolve.

License

MIT


Created by mkdoc on August 2, 2016