release: v2.0.0 — publish as @deepl/cli, migrate the cache to node:sqlite

.github/ISSUE_TEMPLATE/bug_report.md

@@ -15,7 +15,7 @@ A clear, concise description of the bug.
 - **DeepL CLI version**: (run `deepl --version`)
 - **Node.js version**: (run `node --version`)
 - **Operating system**: (e.g., macOS 14.5, Ubuntu 22.04, Windows 11)
-- **Install method**: (source, npm link, other)
+- **Install method**: (npm global, npx, Homebrew, source checkout, npm link, other)
 
 ## Reproduction Steps
 

.github/workflows/ci.yml

@@ -16,7 +16,10 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [24]
+        # 24.15.0 is the `engines.node` floor — the release where node:sqlite
+        # stopped emitting an ExperimentalWarning. Bare `24` resolves to the
+        # latest 24.x, so without the pin the declared floor is never exercised.
+        node-version: ['24.15.0', '24']
 
     steps:
       - uses: actions/checkout@v7
@@ -27,8 +30,61 @@ jobs:
           cache: npm
 
       - run: npm ci
+      # Ahead of lint: reformatting can move an eslint-disable directive off the
+      # line it suppresses, so drift should be reported as formatting rather
+      # than as the lint failures it goes on to cause.
+      - run: npm run format:check
       - run: npm run lint
       - run: npm run type-check
       - run: npm run check-deps
       - run: npm run build
-      - run: npm test
+      - run: npm run test:coverage
+
+  # The suites run from the working tree, so nothing above proves the published
+  # artifact works. `bin` and the package entry have separate module graphs — a
+  # broken entry point ships while the CLI still passes every test.
+  package:
+    name: Packaged artifact
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-node@v7
+        with:
+          node-version: '24'
+          cache: npm
+
+      - run: npm ci
+      - run: npm run build
+
+      - name: Pack
+        id: pack
+        run: echo "tarball=$(npm pack --silent)" >> "$GITHUB_OUTPUT"
+
+      - name: Install globally and run the CLI
+        env:
+          TARBALL: ${{ steps.pack.outputs.tarball }}
+        run: |
+          npm install -g "./$TARBALL"
+          deepl --version
+
+      # From a throwaway consumer package, because Node does not resolve
+      # bare specifiers out of the global prefix.
+      - name: Import the package entry as a dependency
+        env:
+          TARBALL: ${{ steps.pack.outputs.tarball }}
+        run: |
+          tarball_path="$PWD/$TARBALL"
+          consumer="$(mktemp -d)"
+          cd "$consumer"
+          npm init -y >/dev/null
+          npm install "$tarball_path"
+          node --input-type=module -e "
+            const m = await import('@deepl/cli');
+            const keys = Object.keys(m);
+            if (keys.length === 0) {
+              throw new Error('package entry resolved but exported nothing');
+            }
+            console.log('package entry exports:', keys.join(', '));
+          "

.github/workflows/release.yml

@@ -1,8 +1,5 @@
 name: Release
 
-# This workflow only records the GitHub Release for a tag. Publishing to npm
-# happens from GitLab, so no `npm publish` step or NPM_TOKEN secret belongs in
-# this repository.
 on:
   push:
     tags:
@@ -18,8 +15,6 @@ jobs:
     steps:
       - uses: actions/checkout@v7
 
-      # A tag can be pushed at any commit, so a mislabelled tag would otherwise
-      # mint a Release whose title disagrees with the version it contains.
       - name: Verify tag matches package version
         run: |
           tag_version="${GITHUB_REF_NAME#v}"
@@ -29,8 +24,6 @@ jobs:
             exit 1
           fi
 
-      # Release notes come from the tag's CHANGELOG section; releases are
-      # immutable once published, but notes stay editable afterwards.
       - name: Extract changelog section
         id: notes
         run: |
@@ -44,7 +37,6 @@ jobs:
             echo "has_notes=true" >> "$GITHUB_OUTPUT"
           fi
 
-      # Skipped when the release exists, so re-runs are idempotent.
       - name: Create GitHub Release
         env:
           GH_TOKEN: ${{ github.token }}

.gitignore

@@ -1,16 +1,12 @@
 # Dependencies
 node_modules/
-.npm
 
 # Build outputs
 dist/
-build/
-lib/
 *.tsbuildinfo
 
 # Testing
 coverage/
-.nyc_output/
 
 # Environment variables
 .env
@@ -19,11 +15,6 @@ coverage/
 # Secrets and credentials
 *.pem
 *.key
-*.p12
-*.pfx
-*.cert
-*.crt
-credentials.json
 
 # IDEs and editors
 .vscode/
@@ -34,47 +25,20 @@ credentials.json
 
 # OS files
 .DS_Store
-Thumbs.db
-Desktop.ini
-
-# Debug logs
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-pnpm-debug.log*
-
-# Runtime data
-*.pid
-*.seed
-*.pid.lock
 
 # Logs
-logs/
 *.log
 
-# Cache and temporary files
-.cache/
-.temp/
-.tmp/
-*.tmp
+# Caches
 .eslintcache
 
-# DeepL CLI specific
-.deepl-cli/
+# SQLite databases; the cache lives outside the repo, but a stray
+# DEEPL_CONFIG_DIR could land one here. Fixture databases are committed.
 *.db
+!tests/fixtures/*.db
 *.db-journal
 *.db-wal
 *.db-shm
 
 # Claude Code local tooling (settings, hooks, agent worktrees, session state)
 .claude/
-
-# Playwright MCP local state
-.playwright-mcp/
-
-# Beads issue tracking (local)
-.beads/
-issues.jsonl
-
-# QA harness
-qa/

.prettierignore

@@ -1,5 +1,15 @@
-node_modules
+# The format scripts only cover src/ and tests/, but prettier reaches
+# everything below when pointed at the repo root.
+
+# Build and coverage output
 dist
 coverage
-*.log
-.DS_Store
+
+# Generated from GET /v3/languages; check:languages compares the raw text, so
+# reformatting it would report permanent drift.
+src/data/language-entries.ts
+
+# Fixtures are byte-exact test inputs. Some encode the very thing under test:
+# en-reserved-words.yaml quotes "yes"/"no" so YAML 1.1 cannot read them as
+# booleans, and prettier rewrites those quotes.
+tests/fixtures/