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

ngx-tethys

v18.2.1

Published

Fast and reliable Tethys Design components for Angular by Worktile & PingCode FE Team.

Downloads

720

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

why520crazywhy520crazywalkerkay001walkerkay001pubuzhixingpubuzhixingxiaobei_luxiaobei_luhandsomebutterballhandsomebutterballhuanhuanwahuanhuanwaminlovehuaminlovehua

Keywords

Readme

ngx-tethys

Fast and reliable Tethys Design components for Angular by Worktile & PingCode FE Team.

CircleCI Coverage Status npm (scoped) npm release docgeni code style: prettier

English | 中文文档

✨ Features

  • 📦 Out of the box
  • 🚀 Powerful and 60+ rich components
  • 🔰 Perfect support for TypeScript, Provide complete type definition
  • 🎨 Extract enterprise level interactive language and design style
  • 💫 Synchronize with Angular version
  • ❤️ High-Quality, Each component has complete testing coverage and documentation, and high quality is equivalent to using it with confidence

📖 Documentation

Development

Only for library contributors.

Clone and installation

$ git clone [email protected]:atinc/ngx-tethys.git
$ cd ngx-tethys
$ npm install
$ npm run start

Release & Publish

  1. Run npm run release to release new version, this command will does the following:

    • Checkout to master and identifies current version and latest tag.
    • Prompts for a new version to select.
    • Create a release branch as release-v1.0.0
    • Modifies package metadata (package.json, version.ts) to reflect new release and generate changelog
    • Commits those changes to release branch.
    • Pushes to the git remote.

    You can run npm run release -- [patch|minor|major|2.0.0] to skip the version selection prompt and increment the version by that keyword or specify version.

  2. Submit pull request from release branch to master(don't merge it)

  3. GitHub Actions will auto build and publish lib

Release the next version requires executing npm run release-next

Manually release version requires executing npm run release-manual

npm run release -- --dry-run or npm run pub -- --dry-run

running with the flag --dry-run allows you to see what commands would be run, without committing to git or updating files. (意思就是打印一下日志让你看看做了哪些步骤，但是并不会真的执行脚本，你可以放心的执行)

Notes

  1. Don't use barrel index (should directly import specify component in module, don't import index.ts)
  2. Should exports component module in public-api.ts