

The package.json file used by npm really only requires one version ( main), but as it turns out, we aren’t limited to that. How does npm know which version to serve to a browser/build process? It is likely your own package.json file will contain a lot more than is listed here. The file used in these examples was generated by hand, and will include the minimum configuration required for the discussion/task at hand. Throughout this document, references are made to the package.json file listed above. Properly packaging your SFC for distribution via npm enables your component to be shared in a way which is ready to use everywhere! Packaging Components for npmįor the purposes of this section, assume the following file structure: package.json However, this excludes anyone who wishes to use the component directly in a browser via tag, anyone who uses a runtime-only build, or build processes which don’t understand what to do with.

vue file might be preferred in this scenario (see Packaging Components for npm > SSR Usage for details). Also, the SSR build uses string concatenation as an optimization, so the. vue files directly, and anyone using a Vue build containing the Vue compiler can consume it immediately. vue file directly? Isn’t that the simplest way to share components?” Because a Single File Component (SFC) is already just one file, you might ask: Our sponsors and backers are listed in SPONSORS.md.
UNPKG MODULE HOW TO
Please visit the UNPKG website to learn more about how to use it. Vue already allows components to be written as a single file.

UNPKG MODULE CODE
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.
