PUBLIC ASSET GUIDE
How to Use LibStract
You just need to copy the URL of the asset you need and use it on your website. LibStract hosts the asset for you, so no separate hosting is required on your side.
1. Find and copy a public URL
Open the library catalog and search by library name, version, type or short filename. Copy URL gives the asset's hosted address; Download saves that individual file. Copy URL is the easiest option when you want to load the asset directly from LibStract.
2. Add a hosted stylesheet
Use the public stylesheet URL shown below. It is resolved from the current LibStract host. Copy URL in the catalog provides the same URL for use in your page. Font Awesome 7's companion webfonts are served with its published stylesheet.
3. Add a hosted JavaScript library
Load a classic browser script before the code that uses it. Use the URL copied directly from the LibStract catalog and follow the library documentation for initialization.
The URL above uses LibStract's current host. Use Copy URL in the catalog to copy the exact address.
Do not load jQuery 3 and jQuery 4 on the same page unless you deliberately manage their shared global names.
4. Include both CSS and JavaScript when needed
Some libraries publish companion CSS and JavaScript. Their files have separate catalog entries. Add both public URLs when the library requires both resources.
These URLs use LibStract's current host. Use Copy URL in the catalog to copy each exact address.
5. Import an ES module
Fuse.js is supplied as an ES module. Use a module script and import the public URL provided by LibStract's Copy URL button. If your browser reports a MIME-type or CORS error, check the browser console for details.
The URL above uses LibStract's current host. Use Copy URL in the catalog to copy the exact address.
Production checks for a hosted asset
Use the public HTTPS URL provided by the LibStract catalog. Check that the asset loads successfully and that any required companion files, fonts, modules, or cross-origin requests work correctly from your website. For important production projects, test the asset before release and consider keeping a local copy when the library's licence allows it. Read the library's licence before redistribution.