zemd / aul

⛩ Elegant SQL-friendly ORM for Node.js

Hey 👋

NAME
    zemd - Dmytro Zelenetskyi

SYNOPSIS
    zemd [OPTIONS]

DESCRIPTION
    A father, husband, software expert and technology enthusiast with a project 
    history of over ten years and seasoned in various technologies. I am eager 
    to learn new things and take on new challenges.

OPTIONS
    --hey,--hej
        Open the chat with the the sender using the send_message() system call. 
        Send and receive data. There are a number of ways to do this, but the 
        simplest is to use the linkedin() and email() system calls.

    --essential
      Display the list of essential projects.
        @zemd/tsconfig           - default tsconfig files
        @zemd/eslint-flat-config - ESlint flat config with useful set of rules
        .dotfiles                - my dotfiles
        vscode dark theme        - VS Code dark theme

    --css
      Display packages and projects related to CSS.
        @zemd/css-reset           - simple and minimal CSS reset for modern web development.
        @zemd/open-props          - supercharged CSS variables for modern web
        @zemd/tailwind-with-props - a Tailwind preset that maps theme config options to CSS custom properties
        typeface-cisco-sans-tt    - self-host the Cisco Sans TT fonts in a neatly bundled NPM package
        typeface-open-sauce-fonts - self-host the Open Sauce fonts in a neatly bundled NPM package.
  
    --react
      Display the list of react projects. 
        @zemd/react-slottable - slot foundation for your react components

    --javascript
      Display javascript or/and typescript projects
        @zemd/http-client     - lightweight and functional http client builder
        @zemd/figma-rest-api  - a rest api client for Figma
        @zemd/flickr-rest-api - a rest api client for Flickr
        webdav-watch          - a simple cli tool for synchronizing folder with remote webdav server
  
    --frontend
      Display various javascript or/and typescript libraries aimed specifically to frontend
        @zemd/drag-and-drop - simple drag and drop framework

    --backend
      Display projects aimed to work on backend
        @zemd/nestjs-pino-logger - a pino logger integration with nestjs framework
  
    --yarn
      Display the list of yarn2 plugins and yarn2 related tools. 
        yarn-plugin-wait         - plugin that can wait
        yarn-plugin-script-tools - replacing npm scripts with yml instruction file
        yarn-plugin-check        - plugin that can check(port or exit status of the custom command)
        yarn-plugin-banner-tools - plugin that displays ascii banner

    --contributions
      Display the list of open source projects that I participated in.
        hazelcast-client (2017)- implemented `ReplicatedMap` and `Semaphore` data structures
  
SUPPORTED EXTENSIONS
    *.sh, *.js, *.ts, *.tsx,
    *.mjs, *.cjs, *.go, *.rs

DEPRECATED EXTENSIONS
    *.java, *.php, *.rb

COMPANY
    Ikea IT AB

PREVIOUS COMPANIES
    Gopuff, Edgio, Waverley Software,
    Cprime, DataArt

ENVIRONMENT VARIABLES
    LANG
        en_US.utf-8
        uk_UA.utf-8
    HOST
        Malmö, Sweden

KNOWN BUGS
    Requires to use Linkedin messages before establishing communication via email.

SEE ALSO
    blog(4), linkedin(4),
    onlyfans(6), codewars(4)

aul's Issues

An in-range update of koa-compose is breaking the build 🚨

Version 4.1.0 of koa-compose was just published.

Branch	Build failing 🚨
Dependency	koa-compose
Current Version	4.0.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

koa-compose is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci CircleCI is running your tests Details
• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 4 commits.

• 06e82e6 Release 4.1.0
• 13768ff improve: reduce stack trace by removing useless function call (#95)
• e754ca3 test: switch from mocha to jest (#90)
• 326d9ce test: next() should always return а Promise (#89)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.