@meza/adr-tools 1.0.10 → 1.0.11

package/vitest.config.e2e.ts

@@ -0,0 +1,13 @@
+import { defineConfig } from 'vitest/config';
+
+export default defineConfig({
+  test: {
+    dir: 'tests',
+    testTimeout: 10000,
+    watch: false,
+    coverage: {
+      reportsDirectory: './reports/coverage/e2e',
+      reporter: ['text', 'json', 'html']
+    }
+  }
+});

package/vitest.config.ts

@@ -2,10 +2,17 @@ import { defineConfig } from 'vitest/config';
 
 export default defineConfig({
   test: {
+    dir: 'src',
     testTimeout: 10000,
     watch: false,
+    poolOptions: {
+      forks: {
+        singleFork: true,
+        isolate: true
+      }
+    },
     coverage: {
-      reportsDirectory: './reports/coverage',
+      reportsDirectory: './reports/coverage/unit',
       reporter: ['text', 'json', 'html']
     }
   }

package/.eslintignore

@@ -1,2 +0,0 @@
-node_modules
-dist

package/.eslintrc.json

@@ -1,23 +0,0 @@
-{
-  "extends": [
-    "tailored-tunes",
-    "plugin:json/recommended",
-    "plugin:security/recommended"
-  ],
-  "root": true,
-  "parser": "@typescript-eslint/parser",
-  "plugins": [
-    "json",
-    "@typescript-eslint"
-  ],
-  "rules": {
-    "no-console": "off",
-    "security/detect-object-injection": 0,
-    "security/detect-non-literal-fs-filename": 0
-  },
-  "env": {
-    "commonjs": false,
-    "es6": true,
-    "node": true
-  }
-}

package/.github/dependabot.yml

@@ -1,14 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
-version: 2
-updates:
-  - package-ecosystem: "npm" # See documentation for possible values
-    directory: "/" # Location of package manifests
-    versioning-strategy: increase-if-necessary
-    commit-message:
-      prefix: "chore: "
-    schedule:
-      interval: "daily"

package/.github/workflows/auto-merge.yml

@@ -1,14 +0,0 @@
-name: auto-merge dependabot
-
-on:
-  pull_request:
-
-jobs:
-  auto-merge:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - uses: ahmadnassri/action-dependabot-auto-merge@v2
-        with:
-          target: minor # includes patch updates!
-          github-token: ${{ secrets.GITHUB_TOKEN }}

package/doc/adr/0001-record-architecture-decisions.md

@@ -1,21 +0,0 @@
-# 1. Record architecture decisions
-
-Date: 2022-06-22
-
-## Status
-
-Accepted
-
-## Context
-
-We need to record the architectural decisions made on this project.
-
-## Decision
-
-We will use Architecture Decision Records, as [described by Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions).
-
-## Consequences
-
-See Michael Nygard's article, linked above.
-For a lightweight ADR toolset, see Nat Pryce's [adr-tools](https://github.com/npryce/adr-tools).
-> For a node version of the same tooling, see Meza's [adr-tools](https://github.com/meza/adr-tools).

package/doc/adr/0002-using-heavy-e2e-tests.md

@@ -1,20 +0,0 @@
-# 2. Using Heavy E2E Tests
-
-Date: 2022-06-22
-
-## Status
-
-Accepted
-
-## Context
-
-The original tool has an [exhaustive test suite](https://github.com/npryce/adr-tools/tree/master/tests) that allows us to make sure that we're backwards compatible.
-
-## Decision
-
-We'll be re-implementing those tests for ourselves too. This means that we will be using the original examples,
-expectations and the ethos of invoking the tool with the given examples.
-
-## Consequences
-
-The E2E test suite will be very slow to run and it can only be executed sequentially.