@polywrap/uri-resolver-extensions-js

@polywrap/uri-resolver-extensions-js

Polywrap URI resolver extensions to customize resolution in the Polywrap Client.

Installation

npm install --save @polywrap/uri-resolver-extensions-js

Usage

If you build a configuration for the Polywrap client using the PolywrapClientConfigBuilder in the @polywrap/client-config-builder-js package, the ExtendableUriResovler is included by default. In that case you only need to register implementations of the URI Resolver Extension interface.

Otherwise, you must also add the ExtendableUriResolver to your resolver.

  const clientConfig: CoreClientConfig = {
    interfaces: new UriMap<Uri[]>([
      [
        Uri.from("wrap://ens/uri-resolver.core.polywrap.eth"),
        [
          Uri.from("wrap://ens/fs-resolver.polywrap.eth"),
          Uri.from("wrap://ens/ipfs-resolver.polywrap.eth"),
          Uri.from("wrap://ens/ens-resolver.polywrap.eth"),
        ],
      ],
    ]),
    resolver: RecursiveResolver.from(
      [
        StaticResolver.from([
          ...redirects,
          ...wrappers,
          ...packages,
        ]),
        new ExtendableUriResolver(),
      ]
    )
  };

Reference

ExtendableUriResolver

/**
 * A Uri Resolver that delegates resolution to wrappers implementing the
 * URI Resolver Extension Interface.
 * */
export class ExtendableUriResolver extends UriResolverAggregatorBase<
  Error,
  Error
> 

Properties

extInterfaceUri (static)

  /** The supported interface URIs to which resolver-ext implementations should be registered */
  public static defaultExtInterfaceUris: Uri[] = [
    Uri.from("wrap://ens/wraps.eth:uri-resolver-ext@1.1.0"),
    Uri.from("wrap://ens/wraps.eth:uri-resolver-ext@1.0.0"),
  ];

extInterfaceUri

  /** The active interface URIs to which implementations should be registered */
  public readonly extInterfaceUris: Uri[];

constructor

  /**
   * Create an ExtendableUriResolver
   *
   * @param extInterfaceUris - URI Resolver Interface URIs
   * @param resolverName - Name to use in resolution history output
   * */
  constructor(
    extInterfaceUris: Uri[] = ExtendableUriResolver.defaultExtInterfaceUris,
    resolverName = "ExtendableUriResolver"
  ) 

Methods

getUriResolvers

  /**
   * Get a list of URI Resolvers
   *
   * @param uri - the URI to query for resolvers
   * @param client - a CoreClient instance that can be used to make an invocation
   * @param resolutionContext - the current URI resolution context
   *
   * @returns a list of IUriResolver or an error
   * */
  async getUriResolvers(
    uri: Uri,
    client: CoreClient,
    resolutionContext: IUriResolutionContext
  ): Promise<Result<IUriResolver<unknown>[], Error>> 

tryResolverUri

  /**
   * Resolve a URI to a wrap package, a wrapper, or a URI.
   * Attempts resolution with each the URI Resolver Extension wrappers sequentially.
   *
   * @param uri - the URI to resolve
   * @param client - a CoreClient instance that may be used to invoke a wrapper that implements the UriResolver interface
   * @param resolutionContext - the current URI resolution context
   * @returns A Promise with a Result containing either a wrap package, a wrapper, or a URI if successful
   */
  async tryResolveUri(
    uri: Uri,
    client: CoreClient,
    resolutionContext: IUriResolutionContext
  ): Promise<Result<UriPackageOrWrapper, Error>> 

getStepDescription (protected)

  /**
   * A utility function for generating step descriptions to facilitate resolution context updates
   *
   * @returns text describing the URI resolution step
   * */
  protected getStepDescription = (): string 

UriResolverExtensionFileReader

/** An IFileReader that reads files by invoking URI Resolver Extension wrappers */
export class UriResolverExtensionFileReader implements IFileReader 

constructor

  /**
   * Construct a UriResolverExtensionFileReader
   *
   * @param _resolverExtensionUri - URI of the URI Resolver Extension wrapper
   * @param _wrapperUri - URI of the wrap package to read from
   * @param _client - A CoreClient instance
   * */
  constructor(
    private readonly _resolverExtensionUri: Uri,
    private readonly _wrapperUri: Uri,
    private readonly _client: CoreClient
  ) 

Methods

readFile

  /**
   * Read a file
   *
   * @param filePath - the file's path from the wrap package root
   *
   * @returns a Result containing a buffer if successful, or an error
   * */
  async readFile(filePath: string): Promise<Result<Uint8Array, Error>> 

UriResolverWrapper

/**
 * An IUriResolver that delegates resolution to a wrapper that implements
 * the URI Resolver Extension Interface
 * */
export class UriResolverWrapper implements IUriResolver<unknown> 

constructor

  /**
   * construct a UriResolverWrapper
   *
   * @param implementationUri - URI that resolves to a URI Resolver Extension implementation
   * */
  constructor(public readonly implementationUri: Uri) 

Methods

tryResolverUri

  /**
   * Attempt to resolve a URI by invoking a URI Resolver Extension wrapper, then
   * parse the result to a wrap package, a wrapper, or a URI
   *
   * @param uri - the URI to resolve
   * @param client - a CoreClient instance that may be used to invoke a wrapper that implements the UriResolver interface
   * @param resolutionContext - the current URI resolution context
   * @returns A Promise with a Result containing either a wrap package, a wrapper, or a URI if successful
   */
  async tryResolveUri(
    uri: Uri,
    client: CoreClient,
    resolutionContext: IUriResolutionContext
  ): Promise<Result<UriPackageOrWrapper, unknown>> 

Development

This package is open-source. It lives within the Polywrap JavaScript Client repository. Contributions from the community are welcomed!

Build

nvm use && yarn install && yarn build

Test

yarn test

Changelog

Polywrap Origin (0.11.0)

Features

@polywrap/core-js:

• PR-6 Improved URI Inference
  • Non-wrap URI schemes can now be used (ex: https://domain.com/path). The non-wrap scheme will be used as the authority, and all other contents will be shifted into the path.
  • Examples:
    • https://domain.com/path into wrap://https/domain.com/path
    • ipfs://QmHASH into wrap://ipfs/QmHASH

@polywrap/client-config-builder-js:

• PR-45 Modular Config Bundles
  • The DefaultBundle has been broken apart into two separate bundles: sys and web3.
  • addBundle(...) has been added to the ClientConfigBuilder interface.
  • addDefaults() now calls addBundle("sys") and addBundle("web3") internally.

@polywrap/sys-config-bundle-js:

• PR-45 Bundled System-Level Plugins & Resolvers
  • The sys bundle includes: logger, datetime, concurrent, http, httpResolver
  • This package is compiled to run in both node.js and browsers.
  • In node.js, the bundle also includes: fileSystem, fileSystemResolver.

@polywrap/web3-config-bundle-js:

• PR-45 Bundled Web3 Plugins & Resolvers
  • The web3 bundle includes: ethereumProviderV1, ethereumProviderV2, ipfsHttpClient, ipfsResolver, ensTextRecordResolver, ensResolver, ensIpfsContenthashResolver.

@polywrap/config-bundle-types-js:

• PR-45 Base Typings For Config Bundle Packages
  • Valid config bundle packages are expected to export a bundle value, which is of type Bundle.

Breaking Changes

@polywrap/client-config-builder-js:

• PR-47 Renaming For Improved Accuracy
  • Renamed ClientConfigBuilder to PolywrapClientConfigBuilder
  • Renamed IClientConfigBuilder to ClientConfigBuilder
  • Renamed addWrapper(s) to setWrapper(s)
  • Renamed addPackage(s) to setPackage(s)
  • Renamed addRedirect(s) to setRedirect(s)

@polywrap/core-js:

• PR-32 Rename getEnvFromUriHistory to getEnvFromResolutionPath

Bugs

@polywrap/client-js

• PR-32 Improved Browser Compatability
  • Building the JS client into browser-based applications no longer requires custom polyfills to remove Node.JS dependencies.

@polywrap/client-cofig-builder-js

• PR-37 Add @polywrap/plugin-js as a Dependency
  • This resolves some package resolution warnings that are emitted from npm when installing the client-config-builder.

@polywrap/wasm-js:

• PR-30 Properly Serialize Empty Wrap Environment
  • The wrap environment was being improperly encoded as an empty object, which had a size > 0 bytes, causing deserialization to fail. This has been fixed and it is now an empty byte array with size of 0.