DEV Community: Dani Tseiltin

Monitor your Git project success!

Dani Tseiltin — Mon, 08 Feb 2021 20:19:46 +0000

Hi fells!
Lately, I've been working hard on a lot of personal projects to boost my appearances in GitHub and the software development world (and mostly, reach success in my projects over GitHub), so I was drastically developing projects day and night to get stuff done.

Issues

My main issues we're, that because I have a lot of projects I work on (while most of them are also NPM packages) it was hard for me to follow on all of them regarding downloads/stars/forks and such.
My solution was to develop the Android app I called 'Git Stats' that solved my issue.

Key features

Ability to find GitHub projects
Ability to open GitHub projects information (stars, forks, npm statistics)
Ability to save projects in bookmarks for easier & quicker access.

See your project stats!

Dani Tseiltin — Sat, 06 Feb 2021 12:55:56 +0000

Main issue

Because I have a lot of projects I work on (while most of them are also NPM packages) it was hard for me to follow on all of them regarding downloads/stars/forks and such.

How I solved it

I developed an Android app called Git Stats, this gave me the ability to make it easier and quicker to access my projects information!

Key features

Ability to find GitHub projects
Ability to open GitHub projects information (stars, forks, npm statistics)
Ability to save projects in bookmarks for easier & quicker access.

I'd be happy to hear your thoughts on the app! please be there to share if you like it! feel free to give it some ⭐ if you think I did a good job! I hope I helped you as well~

Do you use Redis?

Dani Tseiltin — Sat, 09 Jan 2021 02:12:46 +0000

Do you use Redis? Or even better = Redis Modules?
I've built a nice project in typescript as a living and easy SDK for Redis Modules!!
Please join and say your piece :) https://github.com/danitseitlin/redis-modules-sdk

[#ActionsHackathon] Automatic NPM deployments

Dani Tseiltin — Sun, 16 Aug 2020 00:07:00 +0000

As part of my #ActionsHackathon submission, I'll be sharing a workflow that will be automatically deploying versions of your NPM package using a project I developed called npm-package-deploy.

In a few words:
This project was originally developed because I had a project where I wanted to automate the NPM version releases on each commit to master in order to make it a bit easier and quicker.

Prerequisites (Before usage):

Install the npm-package-deployer package.
Add a lint script to your package.json ("lint": "eslint .")
Add a deploy script to your package.json ("deploy": "npm-deploy [name of your package]")
Add a script for your tests (which I called unit-tests in my example)
Define a secret called NPM_AUTH_TOKEN which holds the value of your NPM authentication token.
Define secrets for BOT_NAME and BOT_EMAIL that will hold any fake values. (Used to define GIT name and GIT email for the deployment)

My Workflow (Named -> Deployment BOT)

#This is an automatic deployer flow

name: Deployment Bot
on:
  push:
    branches: [ master ]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Configurating GIT
      run: git config --global user.name $BOT_NAME && git config --global user.email $BOT_EMAIL
      env:
        BOT_NAME: ${{secrets.BOT_NAME}}
        BOT_EMAIL: ${{secrets.BOT_EMAIL}}
    - name: Creating .npmrc file
      run: echo "registry=https://registry.npmjs.org/" >> ~/.npmrc && echo "//registry.npmjs.org/:_authToken=$NPM_AUTH_TOKEN" >> ~/.npmrc
      env:
        NPM_AUTH_TOKEN: ${{secrets.NPM_AUTH}}
    - name: Installing NPM packages
      run: npm install
    - name: Running tests
      run: npm run unit-tests
    - name: Verifying linting
      run: npm run lint
    - name: Deploying version
      run: npm run build && npm run deploy

Submission Category:

Maintainer Must-Haves

Yaml File or Link to Code:

Yaml File

Additional Resources / Info

Link to the using repository
Link to a GitHub Action Execution

How to better manage your CLI arguments

Dani Tseiltin — Sat, 15 Aug 2020 09:08:51 +0000

Today, in the natural way in nodejs, our CLI arguments are passed into something called process.argv as a string array.
The problem with that, is that it's not really 'extremely easy to use' in your code.
You'd have to do something like the following code (each time):

const arg = process.argv.find((argument: string) => argument.indexOf('--arg=') !== -1);
const value = arg.split('=')[1];

The code above looks for an item in the array that will contain part of your argument, for this example your argument is --arg.
Not only that, afterwards you need to only take the value in order to use it.
Maybe the code is not complex, but for me it was quite annoying to always handle in my personal/work projects.

A Better solution:

In order to solve my issue, I brought to life a NPM package called cli-argument-parser, this package gives you to ability to address a JS object that will contain only the relevant arguments and their values.

How does it work?

After running npm install cli-argument-parser to install it,
You can try the following code snippet:

import { cliArguments } from 'cli-argument-parser';
const arg1 = cliArguments.arg1;
const arg2 = cliArguments.arg2;

The package, works based on arguments prefixes (-- as default) and separators (= as default).
According to the code snippet above, if I pass the arguments --arg1=value1 arg2=value2, the variable arg1 will hold the correct value, but variable arg2 will hold the value of undefined, because it was filtered out based on the default prefix of --,
If we passed --arg2=value2, the arg2 variable will hold the correct value of value2.

Command line configuration:

Even though I honestly favor using arguments this way --arg=value, people are different so I made sure we can configure unique styles of argument filtering.

Using a configuration file

A way to achieve this is to create a file called cli.config.json in the root directory of your project. You will need to set both prefix and separator like the following:

{
    prefix: '-',
    separator: '~'
}

This configuration means, that you can now pass argument of -arg~value and it will know to filter the correct arguments and build it in the cliArguments JS object.

Using CLI arguments

If additional files are a mess in your opinion, it is also possible to pass the CLI configuration via CLI arguments.
--cli-prefix to configurate the CLI prefix, ie: --cli-prefix=--
--cli-separator to configurate the CLI separator, ie: --cli-separator==

Using the code

Instead of using the existing cliArguments, you are able to also create a custom one, using the following code snippet:

import { filterArguments } from 'cli-argument-parser';
const arguments = filterArguments('--', '=');

The arguments variable will hold a JS object with arguments (just like cliArguments) filtered by defined prefix and separator.

In a few words:

Maybe the problem is not the biggest, but definitely makes it a bit easier to read CLI arguments using this package.
Feel free to share your thoughts and take a peek here and don't be shy to ⭐ it ;)

NPM Deploy Bot: Automate your deploy process

Dani Tseiltin — Mon, 10 Aug 2020 19:52:53 +0000

Hi, I've made a NPM package that helps you release versions of your NPM package.

Why?

I had a project where I wanted to automate the NPM version releases on each commit to master in order to automate the process and make it a bit easier.

How do you use it?

You just run npm-deploy <package name> and it releases the next version based on the latest version released to NPM.
You can also create a package.json script to deploy your version to make it easier to use:

"scripts": {
  "deploy": "npm-deploy <package name>"
}

GitHub Actions integration

You can integrate this package with a GitHub action workflow:

Setup your git configuration
Create an .npmrc file with the NPM auth token
Add deploy script in your package.json like in the example above
Run npm run deploy A full example can be seen here

If you liked it, you can find this package here, feel free to point out your opinion and give it a good star ;)