🎨 vscode-theme-dark-blood

I released the new version of my dark theme for VSCode, 1 theme with 5 shades of different colors with the name of the blood type (A, B, AB, 0)! Optimized for typescript and javascript. I wrote some regexes to color JSDoc comments correctly too which are now much more readable.

👔 Screenshot

Blood - Default

Blood - Type A

Blood - Type B

Blood - Type AB

Blood - Type 0

🚀 Installation

1. Install extension from vscode marketplace.
2. Open VSCode, go to extensions list and find "Dark Blood Theme"
3. Click to Set Color Theme and confirm theme.

🧩 Extra: if you want exactly what the screenshots look like (icons, hexcode colors preview, etc), install these extensions:

• Set font: Fira Code Medium or JetBrains Mono Medium (13.5px size and 500 weight + ligatures).
• ext install pkief.material-icon-theme
• ext install naumovs.color-highlight
• ext install wiggin77.codedox
• ext install gruntfuggly.todo-tree
• ext install esbenp.prettier-vscode
• ext install dbaeumer.vscode-eslint

Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.

❤️ Thanks! Leave a feedback!

🦒 Beautiful Logger for Node.js

The best alternative to the console.log statement

I love using console.log but it is difficult to record all the log information. I have implemented a small colored variant with tags, colors, messages of various errors and write to file logs in .json / txt format.

Resources: [NPM] [GITHUB]

💡 Features

• [✔️] Easy to use
• [✔️] MIT License
• [✔️] The best alternative to the console.log statement
• [✔️] Write stdout logs to file (supported format: text/log and json)
• [✔️] The JSON logs format is compatible with pinojs
• [✔️] Translations: 🇬🇧 🇮🇹 🇵🇱 (Help me ❤️)

👔 Screenshot

🚀 Installation

1. In your node project run: npm install @ptkdev/logger --save
2. Usage:

   const Logger = require("@ptkdev/logger");
   const logger = new Logger();
   logger.info("message");
   

You can set options to new Logger(options); example:

const Logger = require("@ptkdev/logger");

const options = {
    "language": "en",
    "colors": true,
    "debug": true,
    "info": true,
    "warning": true,
    "error": true,
    "sponsor": true,
    "write": true,
    "type": "log",
    "path": {
        "debug_log": "./debug.log",
        "error_log": "./errors.log",
    }
};

const logger = new Logger(options);
logger.info("message");

Options

Methods

💫 License

• Code and Contributions have MIT License
• Images and logos have CC BY-NC 4.0 License
• Documentations and Translations have CC BY 4.0 License

❤️ Thanks! Leave a feedback!

🦌 Badges generator from dotfiles for any markdown

Tool to help automate your badges of shields.io, badgen.net, fury.io and snyk.io from .all-shieldsrc dotfile for your markdown files. You can use Liquid variables like {{name}} or {{version}} which refer to your package.json.

Inspired by all-contributors-cli

Resources: [all-shields-cli on npm] [all-shields-cli on github]

💡 Features

• [✔️] Easy to use
• [✔️] MIT License
• [✔️] Support: shields.io
• [✔️] Support: fury.io
• [✔️] Support: snyk.io
• [✔️] Support: badgen.net
• [✔️] Full customizations!
• [✔️] Liquid Variables
• [✔️] Tool to help automate your badges on markdown.
• [✔️] Badges generator from dotfiles for any markdown

👔 Screenshot

🚀 Installation

1. In your node project run: npm install @ptkdev/all-shields-cli --save-dev
2. In your package.json add script:

    ...
    "scripts": {
        "all-shields-cli": "all-shields-generate"
    }
    ...
   

3. Create .all-shieldsrc and paste sample:

   {
    "files": [
        "README.md"
    ],
    "shields": [
        {
            "id": "my-badges",
            "badges": [
                {
                    "url": "https://www.npmjs.com/package/@ptkdev/all-shields-cli",
                    "color": "lightgray",
                    "label": "package name",
                    "title": "package name",
                    "message": "all-shields-cli",
                    "style": "flat",
                    "logo": "",
                    "platform": "shields"
                }
            ]
        }
    ]
   }
   

4. Add in your README.md the html comment (my-badges is id from the previous step):

   <!-- all-shields/my-badges:START -->
   <!-- all-shields/my-badges:END -->
   

5. Run npm run all-shields-cli

See folder examples, run with node example.js. Below is available a description of options values.

🔑 Liquid variables

In your .all-shieldsrc dotfile you can use liquid variables like {{name}} or {{version}} which refer to your package.json. Key of package.json is name of liquid variable {{key_from_package.json}}

💫 License

• Code and Contributions have MIT License
• Images and logos have CC BY-NC 4.0 License (Freepik Premium License)
• Documentations and Translations have CC BY 4.0 License

❤️ Thanks! Leave a feedback!

I would like to introduce you to my collection of templates (or also called boilerplate). What are? Are a starting templates from which to develop apps, sites, bots, pwa, etc... I hate start new project with empty git repository.

🚀 Why?

They all use the same folder structure, preconfigured typescript and jest, the same prettier, tspaths, eslint, the same contributors and badges generators in short, they are totally userfriendly and same workflow. Learning to use one is very easy to switch to another.

Summary: what do this boilerplate series have in common? All.

👔 Screenshot

My Svelte Github Templates:

🏗 svelte-webcomponent = to create native html5 webcomponents using svelte

👔 svelte-spa = to create single page apps with svelte

🧬 svelte-electron = to create desktop apps using svelte-spa

📱 svelte-cordova = to create mobile (android and ios) apps using svelte-spa

🧵 svelte-kit-ssr = to create apps or websites with svelte optimized for seo using the server side rendering technique

🧰 node-modules = to create npm libraries

🪓 node-cli = to create terminal commands

🤖 node-telegram-bot = to create telegram bot in node

🤖 node-discord-bot = to create discord bot in node

💾 Setup Project

If you want replace all strings (example: package name, author, urls, etc...) in markdown file, source files and others files of this project you need edit setup.json with correct values and run npm run setup.

💫 License

Code and Contributions have MIT License