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

@eui/tools

v6.21.7

Published

eUI common tools and scripts

Downloads

28,820

Readme

@eui/tools

Packages

Build package

eui-scripts build-package <package-name>

# Build a package but **first** its dependencies
eui-scripts build-package <package-name> --deps

# Build a package and send report to Slack
eui-scripts build-package <package-name> --slackReport

# Customize Slack end-point and channel
eui-scripts build-package <package-name> --slackEndPoint /my-new-end-point --slackChannel #my-channel

Build the dependencies of package

If you have several packages, if you want to test 1 package you need to have its dependencies built. This is what this command is for (so run it before testing the package).

eui-scripts build-deps <package-name>

Test package

eui-scripts test-package <package-name>

# or with watch
eui-scripts test-package <package-name> --watch

Publish package

eui-scripts publish <package-name>

# to a specific registry
eui-scripts publish <package-name> --registry=http://my-new-registry.com

# to an alias declared in .euirc.json
eui-scripts publish <package-name> --<registry-alias>

# with Slack Repport
eui-scripts publish <package-name> --slackReport

# Custom Slack end-point & channel
eui-scripts publish <package-name> --slackEndPoint /my-new-end-point --slackChannel #my-channel

Clean package

eui-scripts clean-package <package-name>

Build all packages

eui-scripts build-all

Clean all packages

eui-scripts clean-all

Publish all packages

eui-scripts publish-all

# to a specific registry
eui-scripts publish-all --registry=http://my-new-registry

# to an alias declared in .euirc.json
eui-scripts publish-all --<registry-alias>

App Container

Generate translation

Load the translations located in the packages "/assets/i18n/" folder and generate 1 compiled file with all of the translations.

# You need to provide **scopes**
eui-scripts generate-translations --scopes=opsys,opsys-ui,cc

# Or you can pass packages directly
eui-scripts generate-translations --packages=@opsys-ui/something,@cc/something-else

# Languages (default: ["en", "fr"])
# You can specify the languages
eui-scripts generate-translations --scopes=opsys --langs=en,fr,es,de

# The "root" folder where 'node_modules" is relative to, is by default the process.cwd()
# You can override it passing a --target argument
eui-scripts generate-translations --scopes=opsys --target=src/main/angular

# The destination where the generate files will be saved is "src/assets/i18n-compiled"
# relative to the root folder. You can change it providing a --folder argument
# Be careful that this folder will be removed on each generation so make sure it does not contain
# any other files.
eui-scripts generate-translations --scopes=opsys --folder=src/assets/here-better

Extract Versions of dependencies

Read the packages versions in the node_modules folder for the specified scopes.

# IMPORTANT:
# This script will replace this line:
# "export const VERSIONS = {}"
# in a "src/config/index.ts" file relative to the root.
# You then need to have this file in your project with the specified line of code.

eui-scripts extract-deps-versions --scopes=opsys,opsys-ui,eui

# The "root" folder where the "index.ts" file is relative to, is by default the process.cwd()
# You can override it passing a --target argument
eui-scripts extract-deps-versions --scopes=opsys,eui --target=src/main/angular