npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lasso-plugin-optimizer

v0.0.0

Published

An optimizer for Lasso JS output bundles

Downloads

5

Readme

lasso-optimizer-plugin

A build / compile time optimizer transform for Lasso JS. Gives Lasso JS some extra arms.

What is this?

  • Lasso JS produces output bundles similar to the NODEJS common-js style syntax on the browser.
  • This is one of the transform stage plugins for Lasso JS, that is applied on the final aggregated output of Lasso JS.
  • It performs code transformations

Why is this needed?

  • This plugin helps in further optimizing Lasso JS output bundles under certain conditions, while resolving modules & circular dependencies.
  • Currrently, Lasso JS inlines the filepaths of modules like
$_mod.def("/marko$4.17.3/components/runtime", function (require, exports, module, __filename, __dirname) {
    // code here
});
$_mod_gh_fe.remap("/marko$4.17.3/components", "/marko$4.17.3/components-browser.marko");
$_mod_gh_fe.installed("globalheaderfrontend$25.1.0", "marko", "4.17.3");
$_mod_gh_fe.remap("/marko$4.17.3/src/runtime/components/index", "/marko$4.17.3/src/runtime/components/index-browser");
  • While they provide a mirror representation of your projects file system, this tends to be of an overhead & bloat for projects.
  • Further, these are resolved on the browser by Lasso Modules Client Side Run Time that performs a Node JS style module resolution.
  • Inlined filepaths & the client side runtime take upto ~30KB in your ungzipped output bundle & upto 5KB in your gzipped response.
  • As JS parse times are impacted by bundle size bloats, this helps optimize the bundle for it.

What does this do?

  • This plugin applies an output transform on the code
  • It attempts to resolve all filepaths and module dependencies at build time
  • It transform modules into simple function expressions
$_mod.def("/marko$4.17.3/components/runtime", function (require, exports, module, __filename, __dirname) {
    // code here
});
$_mod.run("/marko$4.17.3/components/runtime");
$_mod_gh_fe.remap("/marko$4.17.3/components", "/marko$4.17.3/components-browser.marko");
$_mod_gh_fe.installed("globalheaderfrontend$25.1.0", "marko", "4.17.3");
$_mod_gh_fe.main("/process$4.17.3", "src/runtime/components/index-browser");

to

var __marko_4_17_3__components__runtime = function (require, exports, module) {
    // code here
});
require(__marko_4_17_3__components__runtime);
  • The .remap, .installed, .main, .run, .builtin, resolve, require, def are all resolved at build / asset bundling phase.
  • On the browser, the bundle doesn't have to resolve these anymore.
  • By doing this, it gets rid of the Lasso Modules Client Side Run Time & uses a miniature version of it.

Usage

This has to be applied as transform in the Lasso config.

{
    "plugins": [
        "lasso-less",
        "lasso-autoprefixer",
        "lasso-marko",
        "lasso-minify-transpile-inline",
        "rollup-plugin-lasso",
        {
            "plugin": "lasso-inline-slots",
            "config": {
                "inlineSlots": [
                    "inline"
                ]
            }
        }
    ],
    "require": {
        "lastSlot": "inline",
        "transforms": [
            "lasso-babel-env",
            "lasso-optimizer-plugin"
        ]
    },
    "minify": true,
    "minifyInlineOnly": false,
    "bundlingEnabled": true,
    "resolveCssUrls": true,
    "noConflict": "gh-fe",
    "cacheProfile": "production"
}