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

@node-elion/builder

v5.1.1

Published

Super scalable enterprise Node.js server library

Downloads

192

Readme

MIT License View this project on NPM View this project on NPM Known Vulnerabilities Quality Gate Status

@node-elion/builder

This package is part of the Elion project.

This package was created to be able quickly and painlessly build js/ts files while ignoring problems with commonJS/ESM modules. To get started, you just need to install this package and change the project's build configuration

Installation

Install @node-elion/builder with npm

This package is recommended to be installed as a dev dependency

npm i --save-dev @node-elion/builder

Usage

Update package.json to be able to use @node-elion/builder package:

/* package.json */
{
    /*...*/
    "scripts": {
        "start": "ebi start",
        "build": "ebi build"
    }
    /*...*/
}

CLI commands

ebi start

| parameter | alias | type | default | description | |------------------------:|:-----:|:----------:|:--------------:|-----------------------------------------------------------------------------------------------------------------------| | --entry | -e | string | src/index.js | sets entry to your application. This is usually the root file, in which all necessary processes are imported and run. | | --assets-folder | -a | string | src/assets | files (like.tf or .json etc.) that should be stored in raw format | | --plugin | -p | string[] | [] | Builder plugins | | --plugin-config | -l | string[] | [] | Plugin config | | --plugins-config-file | -c | string | | Plugin config file (should be .json format) | | --debug | -d | boolean | false | pass Inspect argument (--inspect) to started process | | --build-folder | -b | string | ./.devbuild | Folder, where built files will be stored (you can use tmp for in order to use the temporary folder of your device) |

ebi build

| parameter | alias | type | default | description | |------------------------:|:-----:|:----------:|:--------------:|-----------------------------------------------------------------------------------------------------------------------| | --entry | -e | string | src/index.js | sets entry to your application. This is usually the root file, in which all necessary processes are imported and run. | | --assets-folder | -a | string | src/assets | files (like.tf or .json etc.) that should be stored in raw format | | --plugin | -p | string[] | [] | Builder plugins | | --plugin-config | -l | string[] | [] | Plugin config | | --plugins-config-file | -c | string | | Plugin config file (should be .json format) | | --build-folder | -b | string | ./build | Folder, where built files will be stored | | --keep-classnames | | boolean | false | Keep classnames in production build |

Examples

Check the examples folder for a better understanding of how the loader works

Contributing

Contributions are always welcome!

See CONTRIBUTING.md for ways to get started.

Acknowledgements

License

MIT