Skip to content

Expose _fetchPackageManifest within the fast-npm-meta client package #10

@kricsleo

Description

@kricsleo

Clear and concise description of the problem

It can used to fetch the private packages metadata on the client side, allowing client-side data processing to match that of the server.
(Can be used by the node-modules-inspector)

Suggested solution

Move the _fetchPackageManifest to the fast-npm-meta package and export it.

async function _fetchPackageManifest(name: string, registry: string, userAgent: string): Promise<PackageManifest> {

Alternative

No response

Additional context

I'm willing to submit a PR for this. 🙌🏻

Validations

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions