Bump vitest from 2.1.9 to 4.0.4 (#361)

* Bump vitest from 2.1.9 to 4.0.4

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.1.9 to 4.0.4.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.4/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 4.0.4
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Fix

* Simplify

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Gregor Noczinski <gregor@noczinski.eu>

Author: dependabot[bot]

.editorconfig

@@ -0,0 +1,23 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+trim_trailing_whitespace = true
+
+[*.{js,jsx,ts,tsx}]
+indent_style = space
+indent_size = 2
+
+[*.json]
+indent_style = space
+indent_size = 2
+
+[*.{yaml,yml}]
+indent_style = space
+indent_size = 2
+
+[*.{css,scss,sass,less}]
+indent_style = space
+indent_size = 2

.gitattributes

@@ -0,0 +1,9 @@
+*.yaml text eol=lf
+*.yml  text eol=lf
+*.json text eol=lf
+*.js   text eol=lf
+*.jsx  text eol=lf
+*.ts   text eol=lf
+*.tsx  text eol=lf
+*.html text eol=lf
+*.css  text eol=lf

README.md

@@ -12,18 +12,18 @@ Code kata in JavaScript where you have to write a library of books and magazines
 
 ## Frame conditions
 
-1. You have exact **2.5 hours** of time - **no minute longer**.  
-   If you reach this time limit stop your work immediately.  
-   It is one part of the kata to respect this time limit.  
-   There are no restrictions on how to use the provided time.  
+1. You have exact **2.5 hours** of time - **no minute longer**.
+   If you reach this time limit stop your work immediately.
+   It is one part of the kata to respect this time limit.
+   There are no restrictions on how to use the provided time.
    If you want to code the entire time, take a break or a cigaret - it’s up to you.
 
 2. There is no complete or incomplete, most likely it'll be impossible to close all the tasks in the first run (that's the point of kata as a type of practice). Keep in mind following priorities though:
    1. **Code quality and structure**.
    2. Functionality.
    3. UI/UX.
 
-3. This is a real world situation. You are allowed to consult the Internet, use every library you want, call a friend...  
+3. This is a real world situation. You are allowed to consult the Internet, use every library you want, call a friend...
    **BUT you're NOT allowed to:**
    - do pair programming
    - have a look at your previous implementation of this kata if you've done it before