01 / ASSET CHOICE
Choose the asset your page actually uses
A library may publish JavaScript, CSS, fonts, language packs, or multiple browser builds. Start with the feature you need, then add only the matching assets. A stylesheet cannot initialize JavaScript behavior; a script does not automatically supply a separate theme or icon font.
LibStract lists companion CSS and JavaScript builds as separate entries. Search by library name or file extension, check the exact version on the card, and include both files only when the library’s own instructions call for them.
02 / SCRIPT ORDER
Load dependencies before the code that uses them
Classic scripts execute in document order when loaded without async. Put a dependency first and your initialization code afterward, or use a deliberate module/build setup. Avoid loading multiple versions that claim the same global name on one page.
The link above shows the URL on the current LibStract host. Use Copy URL in the catalog to copy the exact address.
03 / STYLES & FONTS
Keep stylesheet dependencies reachable
If a stylesheet uses companion fonts or other files, keep the required files together as provided by the library. When you use LibStract's published stylesheet URL, LibStract serves its companion assets too; you do not need to upload them yourself.
If an asset does not load correctly, check your browser's Network and Console panels for the specific error.
04 / MODULES
Use module builds as modules
ES modules require a module import and a server that returns JavaScript with a JavaScript MIME type. Fuse.js in this catalog is an ES module, not a classic script; it will not create a global just by adding a normal script src.
The link above shows the URL on the current LibStract host. Use Copy URL in the catalog to copy the exact address.
05 / PRODUCTION
A short production checklist
- Pin and record the exact library version you tested.
- Review the package licence and attribution obligations.
- Use the exact asset URL provided by LibStract; its published companion files are served at the paths expected by the stylesheet or library.
- For assets loaded from LibStract, use the public HTTPS URL provided by the catalog. For files you download and host yourself, make sure your own server uses the correct MIME types and cache settings.
- Test the asset URLs from your website, mobile layout, browser console, and network panel.
- If your website loads an asset from another origin, check the browser's cross-origin and security requirements.