chore: implement git hooks

Using Husky the following hooks:

- commit-msg: conventional commit lint
- pre-commit: lint-staged
- pre-push: run test

Author: jorgecasar

.commitlintrc

@@ -0,0 +1,5 @@
+{
+  "extends": [
+    "@commitlint/config-conventional"
+  ]
+}

.editorconfig

@@ -0,0 +1,13 @@
+# Stop the editor from looking for .editorconfig files in the parent directories
+root = true
+
+[*]
+# Non-configurable Prettier behaviors
+charset = utf-8
+insert_final_newline = true
+# Caveat: Prettier won’t trim trailing whitespace inside template strings, but your editor might.
+trim_trailing_whitespace = true
+
+# YAML Files
+[*.{yml,yaml}]
+indent_style = space

.eslintrc.cjs

@@ -0,0 +1,49 @@
+module.exports = {
+	extends: [
+		'eslint:recommended',
+		'plugin:prettier/recommended',
+		'plugin:import/recommended',
+		'plugin:markdown/recommended',
+		'plugin:@typescript-eslint/recommended',
+	],
+	plugins: ['@typescript-eslint', 'prettier', 'import', 'html', 'markdown'],
+	env: {
+		browser: true,
+		node: true,
+		es2022: true,
+	},
+	parser: '@typescript-eslint/parser',
+	parserOptions: {
+		ecmaVersion: 'latest',
+		sourceType: 'module',
+	},
+	ignorePatterns: ['output', 'outputTest', '**/*d.ts'],
+	rules: {
+		'@typescript-eslint/ban-ts-comment': ['error', { 'ts-ignore': 'allow-with-description' }],
+		indent: ['error', 'tab', { SwitchCase: 1 }],
+	},
+	overrides: [
+		{
+			files: ['**/*.cjs'],
+			env: {
+				commonjs: true,
+			},
+			parserOptions: {
+				sourceType: 'script',
+			},
+		},
+		{
+			// Enable the Markdown processor for all .md files.
+			files: ['**/*.md'],
+			processor: 'markdown/markdown',
+		},
+		{
+			// Target ```js code blocks in .md files.
+			files: ['**/*.md/*.js'],
+			rules: {
+				'no-console': 'off',
+				'import/no-unresolved': 'off',
+			},
+		},
+	],
+};

.eslintrc.json

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx --no -- commitlint --edit ${1}

.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx --no -- lint-staged

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npm test

.husky/pre-push

@@ -6,3 +6,4 @@ input
 coverage
 templates
 dist
+*.d.ts

.prettierignore

@@ -0,0 +1,75 @@
+# Code of conduct
+
+## Our pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and our
+community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our standards
+
+Examples of behavior that contribute to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that do not
+comply with this Code of Conduct, or to ban temporarily or permanently any
+contributor due to other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of conduct applies both within project spaces and in public spaces
+when an individual represents the project or its community. Examples of
+representing a project or community include using an official project email
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+You can report incidents related to abusive, harassing, or otherwise
+unacceptable behavior by contacting the project team
+at [info@coru.net](mailto:info@coru.net). All complaints will be reviewed and
+investigated and will result in a response that is deemed necessary and
+appropriate to the circumstances. The project team is obligated to maintain
+confidentiality concerning the reporter of an incident. Further details of
+specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of conduct has been adapted from the [Contributor Covenant][homepage],
+version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+.
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/