Workflowįor npm package authors, unpkg relieves the burden of publishing your code to a CDN in addition to the npm registry. This will also load more quickly because we won't have to resolve the latest version and redirect them. If you want users to be able to use the latest version when you cut a new release, the best policy is to put the version number in the URL directly in your installation instructions. Redirects are cached for 10 minutes at the CDN, 1 minute in browsers. This is the latest version when no version is specified, or the maxSatisfying version when a semver version is given. URLs that do not specify a package version number redirect to one that does. This works because npm does not allow package authors to overwrite a package that has already been published with a different one at the same version number.īrowsers are instructed (via the Cache-Control header) to cache assets indefinitely (1 year). The CDN caches files based on their permanent URL, which includes the npm package version. This feature is very experimental Cache Behavior any/file?meta) ?module Expands all “bare” import specifiers in JavaScript modules to unpkg URLs. Query Parameters ?meta Return metadata about any file in a package as JSON (e.g. use a “bare” URL), unpkg will serve the file specified by the unpkg field in package.json, or fall back to main.Īppend a / at the end of a URL to view a listing of all the files in a package. may also use a semver range or a tag instead of a fixed version number, or omit the version/tag entirely to use the latest tag.
0 kommentar(er)
