Keep up the good work friend, I have made this script one of the essential elements when creating web pages. This other screenshot shows the structure of my index.html file, I use all the scripts in the head sectionĪnd this one is the CSS styles file that I use with the recommendations of your script and without the property: !ImportantĮven if you want to verify the files yourself you can check the docs folder of my repository, which is published in the github pages So unpkg is also sponsored by Cloudflare which is an awesome CDN and serves 95 of unpkg's traffic from the cache, making unpkg extremely fast. This is the file that executes the reveals, the commented options disable them to verify that they were not the cause of the problem, but it does not matter if they are active or inactive Hello, after a while I come back with another issue, I'm trying to display a page on github pages using your amazing script, it works to a certain extent, the problem is that the "origin" option does not apply the effects it should, possibly I'm doing something wrong but I've tried several times with different options like local scripts, changing styles and events, but it does not work, another minor thing is that by following your recommendations to avoid flickering in the load of the page if the css visibility option is hidden it is added !important like visibility: hidden !important will not work the reveal, it is something uncomfortable sometimes, attached screenshots the my javascript script ScrollReveal Version: release 4.0.4 using cdn.Operating System: Windows 10 pro 圆4 v 1803.The unpkg CDN is powered by Cloudflare, one of the world's largest and fastest cloud network platforms. Instead, please reach out to with any questions or concerns. Please do not contact npm for help with unpkg. unpkg is not affiliated with or supported by npm, Inc. Unpkg is an open source project built and maintained by Michael Jackson. That's it! Now when you npm publish you'll have a version available on unpkg as well. Use a build script to generate your UMD build in the umd directory when you publish.Add the umd directory to your files array in package.json.Add the umd (or dist) directory to your.You can do this easily using the following setup: All you need to do is include your UMD build in your npm package (not your repo, that's different!). 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. You 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |