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

@cevo/angular-gte

v1.2.1

Published

Angular Libraries for communicating with the Gfinity API v2

Downloads

18

Readme

README

This README would normally document whatever steps are necessary to get your application up and running.

What is this repository for?

This library is the primary method of connecting with CEVO CTE API endpoints.

How do I get set up?

Delivering Changes

While working on the library, it's best to be running gulp --env=local to view debug logs and ensure there are no syntax issues.

  • Once work is done, a PR can be opened
  • Once PR is merged into master, pull the new changes onto a local master branch
  • Run "gulp --env=production" or simply "gulp"
  • Run "npm version [patch|minor|major]"
  • Run "npm publish" to push the changes to the npm repository
  • Ensure necessary libraries either "npm update" for patches, or "npm install @cevo/angular-cte --save" for minors and majors
  • Push site reposities that use the new code

Failure to follow these steps will potentially result in a failure on either dev or production, or both, to properly update to the new version. It's important to note that on local repositories you are not building against the NPM repository, but the locally checked out code for this library. You can test a production build by simply running "gulp" to see whether or not the code will work on production as-is, or whether it will fail.