feat: add core tools

# editorconfig.org

root = true

[*]

indent_style = space

indent_size = 2

end_of_line = lf

charset = utf-8

trim_trailing_whitespace = true

insert_final_newline = true

[*.md]

trim_trailing_whitespace = false

# Logs

logs

*.log

npm-debug.log*

yarn-debug.log*

yarn-error.log*

# Runtime data

pids

*.pid

*.seed

*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover

lib-cov

# Coverage directory used by tools like istanbul

coverage

# nyc test coverage

.nyc_output

# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)

.grunt

# Bower dependency directory (https://bower.io/)

bower_components

# node-waf configuration

.lock-wscript

# Compiled binary addons (https://nodejs.org/api/addons.html)

build/Release

# Dependency directories

node_modules/

jspm_packages/

# TypeScript v1 declaration files

typings/

# Optional npm cache directory

.npm

# Optional eslint cache

.eslintcache

# Optional REPL history

.node_repl_history

# Output of 'npm pack'

*.tgz

# Yarn Integrity file

.yarn-integrity

# dotenv environment variables file

.env

# parcel-bundler cache (https://parceljs.org/)

.cache

# next.js build output

.next

# nuxt.js build output

.nuxt

# vuepress build output

.vuepress/dist

# Serverless directories

.serverless/

# FuseBox cache

.fusebox/

#DynamoDB Local files

.dynamodb/

########## end of https://github.com/github/gitignore/blob/master/Node.gitignore

# ignore ide files

.idea

.vscode

# ignore lib

lib

# ignore docs

docs

image: node:lts-alpine

cache:

  key: ${CI_COMMIT_REF_SLUG}

  paths:

    - lib

    - node_modules

before_script:

  - npm install

stages:

  - build

  - test

  - deploy

build:

  stage: build

  script:

    - npm run build

audit:

  stage: test

  script:

    - npm audit

pages:

  stage: deploy

  script:

    - npm run documentation

    - mv docs public

  only:

    - /^v[0-9]+\.[0-9]+\.[0-9]+$/

  artifacts:

    paths:

      - public

## Summary

(Summarize the bug encountered concisely)

## Steps to reproduce

(How one can reproduce the issue - this is very important)

## Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)

## What is the current bug behavior?

(What actually happens)

## What is the expected correct behavior?

(What you should see instead)

## Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,

logs, and code as it's very hard to read otherwise.)

## Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

/label ~meeting

## Description

(Describe the feature that you're requesting concisely)

## Explanation

(Explain why the feature is necessary)

## Dependencies, issues to be resolved beforehand

(List issues or dependencies that need to be resolved before this feature can be implemented)

/label ~meeting