Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

lockandload

Package Overview
Dependencies
Maintainers
1
Versions
44
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

lockandload

Minimalist AMD-compliant Javascript and CSS loader

  • 1.1.18
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8
decreased by-20%
Maintainers
1
Weekly downloads
 
Created
Source

lockandload AMD-loader

Lockandload is a minimalist AMD-loader-compatible boilerplate to kickstart your website. It includes special support for single-page-apps.

Gzipped, the essential script content amounts to roughly 1KB of code. Without compression it blows up to just under 2KB. Further minifying this code does not result in any significant gains, it would just hinder readability.

Features

  • Less filling: 1KB of gzipped script content.
  • Handminified to retain readable and maintainable code.
  • It's so small, it can and should be inlined on your HTML page (which is also one of the reasons to handminify it only).
  • Because it is inlined, it is faster than all other loaders.
  • Fully asynchronous script loader: AMD-loader compatible.
  • Supports anonymous define() calls.
  • Supports local require() calls (with one and two arguments).
  • Supports implicit and explicit ['require'] dependencies.
  • Does not support implicit nor explicit exports/module dependencies.
  • Circular dependencies will silently hang in unresolved state (or put differently: do not do that).
  • No extra diagnostic code to minimise code weight and optimise loading speed.
  • Fully event driven, no polling timers.
  • Standard supported dependencies: require and domready.
  • Both high and low priority asynchronous loading of Javascript and CSS files.
  • Leverages native browser speed for high priority loading (by getting out of the way).
  • Legacy support for $(...) jquery riddled synchronous code.
  • Legacy support for loading synchronous Javascript.
  • Single-page-app support using $$(...) page refresh callbacks.
  • Supports IE10 and up and all other webbrowsers.
  • No config file, means: no syntax to learn, no config file parser code.
  • No module system: all needed functionality is included already because it was/is so small, that writing a module system would take more code than the source of all the added functionality.

Requirements

It runs inside any webbrowser environment (starting at IE10 and up).

Usage

Using npm

Running npm install lockandload in the webroot of your site, should create the following file and directory structure:

  • node_modules
    • lockandload
      • lockandload_master.inc: Placed right after the charset definition on the page.
      • lockandload_headready.inc: The start of the headready script that lives at the end of the <head>.
      • lockandload_trailer.inc: The end of the headready script that lives at the end of the <head>.
      • index.php: PHP boilerplate.
      • main.js: Example SPA (Single Page Application).

Using PHP

Copy the boilerplate node_modules/lockandload/index.php file to your webroot; then customise the copied file to taste.

Using other serverside scripting languages

Look at the PHP boilerplate node_modules/lockandload/index.php, and translate this to your own scripting language.

Without serverside scripting

Copy the node_modules/lockandload/index.html boilerplate file to your webroot; then customise the copied file to taste. The index.html contains two <script> sections. The first section should not be preceded by any other <script> tags and should be left verbatim.

The second section should be placed at or close to the end of the <head>, and should not precede any direct <link type="stylesheet"> tags. Inside this second section there is a clearly marked section that is your configuration area.

The basic structure of a page should be:

  • html
    • head
      • Charset declaration.
      • Inline lockandload master script.
      • High priority async external scripts.
      • Viewport declaration.
      • High priority CSS scripts.
      • <title>.
      • All other tags that should go in the <head>.
      • Inline lockandload 'headready' script.
        • CSS scripts fullfilling a custom applied-style dependency.
        • Low priority CSS scripts.
        • Medium priority async Javascript scripts.
        • Low priority async Javascript scripts.
        • Low priority synchronous Javascript scripts.
    • body
      • All other inline scripts (if you must).

The index.html file is a production-stripped version of annotated.html. Look at annotated.html to understand the code and read additional inline documentation. These index.* and lockandload_*.inc files are not present in the git source repository, they can only be found in the npm repository (or after running npm run prepublish).

API

Globally

  • define(id?, dependencies?, factory)
    The standard AMD global entrypoint. To figure out module ids of all the modules that you are trying to load, uncomment some debugging code in the primary load script and inspect your console-pane in the browser.

    Running define(1, dependencies, factory) is a custom extension and is the same as the traditional global require(dependencies, factory). It is used in the existing scripts to avoid defining the global require().

Locally

In the secondary lockandload 'headready' script; all url arguments are used verbatim in <link href="url"> or <script src="url"> tags:

  • css(url, id?)
    Loads low priority ordered css files asynchronously; after the stylesheet has been applied, it fulfills the optional id dependency.
  • js(url, "async"?)
    Loads Javascript file, if the second optional argument "async" is provided, the load will be asynchronous.

Dealing with jQuery

In order to support legacy code that uses inline $(function(){...}) scattered throughout pages, this loader allows you to use that construct even before the jQuery library has been loaded, and thus enables you to load jQuery in an asynchronous and non-blocking fashion.

The standard headready script contains a dependency on domready and jquery which finally runs domready(1) which will run all the registered delayed functions the first time.

SPA (Single Page App) support

To ease SPA development, the loader defines a $$(function(jquery_document){...}) function which registers functions for execution on every SPA-controlled page refresh. The registered functions receive a convenience argument $(document) when executed.

To run the registered functions, one needs to make a call to the entrypoint of the AMD-dependency on domready without arguments. All domready() calls before domready(1) has been run will silently be ignored.

E.g. in your application, you could use code like this:

!function(){
  // Preamble
  define("main", ["domready"], function (domready) {
    // Your main application
    function refreshpage() {
      // The function that gets called on virtual page refreshes
      domready();	// This will call all registered $$(...) functions
    }
  });
}();

References

Other loaders:

Keywords

FAQs

Package last updated on 30 Aug 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc