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

haxelib-webpack-helper

v1.0.0

Published

Resolve aliases to node modules placed in haxelib directory.

Downloads

4

Readme

Helper for webpack to load npm modules from haxelib directories.

Install

npm install haxelib-webpack-helper --save-dev

Using

Just add line for each haxe library (which contain npm module or *.js) into your webpack.config.js. Helper automatically install haxe libraries if not installed.

You have two alternatives for this: automatic (using some assumes) or manual (suitable for generic case).

Automatic

This way assume what @:jsRequire metas in haxe libraries have next format:

@:jsRequire("haxelib/<haxe_library_name>/<path_to_js_file>")

Then, use resolveHaxelibAliases() to preprocess aliases in your webpack.config.js:

const resolveHaxelibAliases = require('haxelib-webpack-helper').resolveHaxelibAliases;

module.exports = {
    resolve: {
        alias: resolveHaxelibAliases({
            "haxelib/jslibs/js/FontSupport": "",
            "haxelib/jslibs/js/Other": "2.3.1"
        })
    }
}

Function resolveHaxelibAliases() resolve all aliases started from haxelib/ into disk paths. Other aliases will be untouched.

Manual

In this case you can use getHaxelibPath() to get path to specified haxe library. Example of the webpack.config.js:

const getHaxelibPath = require('haxelib-webpack-helper').getHaxelibPath;

module.exports = {
    resolve: {
        alias: {
            //"module_name_specified_in_jsRequire_meta": getHaxelibPath("my_haxe_library_name") + "relative_path_to_npm_or_js_file"
            "jslibs/FontSupport": getHaxelibPath("jslibs") + "js/FontSupport",
            "jslibs/Other": getHaxelibPath("jslibs:2.3.1") + "js/Other"
        })
    }
}