Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/darkwebdev/lasso-modernizr below:

darkwebdev/lasso-modernizr: Modernizr plugin for Lasso.js

Lasso.js plugin for custom builds of Modernizr

npm install lasso-modernizr --save

The lasso-modernizr plugin will then need to be registered (and configured) as shown below:

require('lasso').configure({
    ...
    plugins: [
        'lasso-modernizr',
        ...
    ]
});

Include the generated file name into the dependencies of the page where you intend to use Modernizr.

browser.json

{
    "dependencies": [
        { "type": "modernizr" },
    ]
}

You can inline Modernizr into HTML. That's recommended when you want to reduce the amount of rerenders in cases when you use:

• setClasses - set classes on HTML element for conditional CSS behaviour
• html5printshiv - fix HTML5 elements for IE8 and below

{
    "dependencies": [
        { "type": "modernizr", "inline": true },
    ]
}

You should pass Modernizr configuration options through the config object directly to Modernizr. For example:

require('lasso').configure({
    ...
    plugins: [
        {
            plugin: 'lasso-modernizr',
            config: {
                crawl: false,
                tests: [
                    'csstransitions',
                    'flexbox'
                ]
            }
        }
    ]
});

Now just use it like Modernizr.flexbox === true

Default options:

    ...
    config: {
        cache: true,
        devFile: false,
        dest: false,
        options: [],
        uglify: false,
        tests: [],
        excludeTests: [],
        crawl: true,
        useBuffers: false,
        files: {
            src: [
                '*[^(g|G)runt(file)?].{js,css,scss}',
                '**[^node_modules]/**/*.{js,css,scss}',
                '!lib/**/*'
            ]
        },
        customTests: []
    }

Crawl and files options mean that these files will be automtically parsed for Modernizr usage.

For custom tests use addTest option:

    ...
    config: {
        ...
        options: [
            'addTest'
        ] ,
        customTests: [
            './util/modernizr-tests.js'
        ]
    }

modernizr-tests.js

/* global define */
define(['Modernizr'], function(Modernizr) {
    'use strict';

    Modernizr.addTest('ios', function(){
        return Boolean(navigator.userAgent.match(/(iPad|iPhone|iPod)/g))
    });
});

Now you can use it like Modernizr.ios === true

Another way to run custom tests is to add require-run: ./path/to/modernizr-tests to browser.json

Other Modernizr options description can be found here.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4