mirror of
https://github.com/sharevb/it-tools.git
synced 2026-11-21 21:44:40 +03:00
dc031dfe2cdf3175dc40cfc5088cf4e329cf8897
2278
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
dc031dfe2c | fix(i18n): correct Traditional Chinese terminology and spacing | ||
|
|
dd688a23a9 |
i18n: add Traditional Chinese (zh-TW) locale
- locales/zh-TW.yml: converted 1:1 from the freshly reviewed zh.yml (#584), 8459 keys, key parity and {placeholder} parity both verified (0 diffs) - src/tools/fstab-generator/locales/zh-TW.yml: per-tool locale converted as well - src/components/NavbarButtons.vue: register the display name Method: OpenCC s2twp + a manual Taiwan terminology pass (104 phrase fixes). Locales are auto-discovered via import.meta.glob, so the new file needs no further wiring. |
||
|
|
bb00dcb8de |
i18n(zh): review the Simplified Chinese translation (#584)
Fix machine-translation errors, make terminology consistent, add spacing between CJK and Latin text, use full-width punctuation, and add the two missing database-builder keys. Restore the externalAccess "null" sentinel that had been translated as 无效的 and restore code samples that had been translated. Refs sharevb/it-tools#571 Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
de40fc7a98 |
fix(visualsubnetcalc, zpool-calc): escape user data before inserting HTML
Visual Subnet Calculator loads its subnet map from `?c=` shareable links and imported configs, then wrote subnet keys, notes and colours into the table HTML unescaped. A crafted link could run script on the it-tools origin. addRow() now escapes the network, note and ancestor keys in join cells, and only accepts hex colours. Allocation results, validation issues, warnings, the network-boundary notice and caught exception messages are escaped as well. zpool-calc wrote the vdev type <select> value with .html(); use .text(). Both are vendored files; reapply if they are updated from upstream. Fixes CodeQL js/xss-through-dom and js/xss-through-exception alerts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
a891be1a13 |
fix(scripts): make extract-tools-desc quote matching linear
`(?:[^']+|(?<=\\)')+` nests quantifiers and backtracks exponentially on long
unterminated values. Use one `'(?:[^'\\]|\\.)*'` pattern for both extracting
and replacing. Extraction used `(.*?)`, which stopped at the first escaped
quote (`'It\'s'` became `It\`); it now reads the whole value and decodes
JS string escapes (\n, \xHH, \uHHHH, \u{...}, \') before writing the
locale file.
Fixes CodeQL js/redos alerts in scripts/extract-tools-desc.mjs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
1b8d4879ac |
fix(database-builder): quote names and passwords in generated SQL
The database name, account and server address are prefilled from URL query parameters and were pasted into the script as is, so a crafted link could add statements to the SQL a user copies and runs (e.g. a database name containing `` `; DROP DATABASE prod; -- ``). A password containing `'` also produced invalid SQL. - Quote identifiers and string literals per dialect. - PostgreSQL passwords containing a backslash are emitted as E'' strings, which parse the same whatever standard_conforming_strings is set to. - Oracle has no escape for `"` in quoted names or passwords, so either one containing `"` shows a validation error instead of generating SQL. Plain Oracle names stay unquoted since quoting makes them case-sensitive. - Newlines in values that land in SQL comments are flattened. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
0203c2388a |
fix(random): use crypto.getRandomValues for generated secrets
`src/utils/random.ts` was built on Math.random(), and it backs the token
generator, htpasswd salts and the passphrase suffixes. The PIN code
generator and the database builder's default password called Math.random()
directly. All now go through crypto.getRandomValues() with rejection
sampling, so indices are unbiased, for ranges up to 2^53.
The passphrase generator no longer calls generateSillyPassword(), which also
picks words with Math.random(). It uses the package's word lists with the
secure helpers, and skips pulling lodash and zxcvbn into the bundle.
Behaviour changes that came with it:
- randIntFromInterval() now includes its upper bound. The lorem ipsum
sliders could never reach their maximum and the passphrase generator never
put a number on the last word. The coin flipper used `0..10 % 2`, which
would be biased with an inclusive range, so it now draws 0 or 1.
- randIntFromInterval() orders reversed bounds, rounds fractional ones
inward and returns NaN for non-finite input instead of throwing.
- The lorem ipsum generator falls back to its defaults for malformed
`paragraphs`, `sentences` and `words` URL values and clamps them to the
slider ranges, so a link like `?sentences=[1,4294967297]` cannot freeze
the page.
- Passphrases whose length equals the min or max length are accepted.
- Multi-word list entries ("wide eyed") count as one word, so the word count
and number placement match the settings.
- Token generator draws each character independently instead of shuffling
the alphabet repeated `length` times.
Fixes the CodeQL js/insecure-randomness alert in the passphrase generator.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
d785329e74 |
fix(layout): escape every bracket and paren in footer package links
String replace() only replaced the first `[`, `]`, `(` and `)`, and link text backslashes were left as is. Use global regexes and escape backslashes too. Fixes CodeQL js/incomplete-sanitization alerts in the tool layout. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
f1b20c7c18 |
refactor(turndown): remove text-node escape rules that never run
Turndown only applies rules to element nodes; text nodes always go through its built-in escape(). The `escapeText` rules and their `escapeMarkdown` helpers in HTML to Markdown, HTML to data and EPUB to Markdown were never called. They also escaped `|` twice, which would have produced `\\|` had anyone wired them up. Output is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
3872432a07 |
fix(markdown): escape backslashes in generated table cells
Pipes were escaped but backslashes were not, so a cell ending in `\` turned the added `\|` into `\\|` and the pipe split the cell. The object-array Markdown export also left newlines in cells, which broke the row; they now become `<br>` like in the Markdown table generator. Fixes CodeQL js/incomplete-sanitization alerts in the Markdown table generator and the object-array export. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
9b655473bc |
fix(json-viewer): unescape JSON strings in a single pass
Unescaping backslashes before `\n`, `\t` and friends decoded escaped backslashes twice: `\\n` in an escaped JSON string became a raw newline instead of `\n`, so parsing failed with "invalid character". A single replace with a lookup table decodes each escape exactly once. Fixes the CodeQL js/double-escaping alert. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
b688f528bd |
fix(objgen): comment detection and whitespace stripping
The comment check passed its pattern as a string, so every `\s` became a literal `s`. Lines starting with `s` that contained `//` or ended in `/` (e.g. `site = https://example.com`) were dropped as comments. Lines are already trimmed, so only `//` and lone `/` lines need skipping. `spacesRegx` and `newLineRegx` lacked the global flag: prop names kept all but their first space, and whitespace-only lines were treated as content. Fixes CodeQL js/useless-regexp-character-escape and js/incomplete-sanitization alerts in src/utils/objgen.ts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
3e7f8459ff | i18n: rewrite Italian locale with human-quality translations (#582) | ||
|
|
4e5c0fd401 |
fix(docker): serve precompressed static assets (#583)
Generate gzip sidecars for JavaScript, CSS, and WebAssembly assets during the image build. Serve them through nginx when clients accept gzip, including proxied requests, while preserving uncompressed fallback and runtime HTML base-path rewriting. |
||
|
|
e179bd5b9b | docs(zpool-memo): reformat vdev type table | ||
|
|
44f1298471 | docs(locales): improve zh UFW generator translations | ||
|
|
f196182261 | feat(zpool-memo): add localized content and recategorize | ||
|
|
cba443dc39 | i18n: update translations for iptables and fstab generator tools | ||
|
|
fad759efda | chore(version): release 2026.09.27 v2026.9.27 | ||
|
|
fd37ca3dda | docs(changelog): update changelog for 2026.09.27 | ||
|
|
51cb09339c | chore: fix release script | ||
|
|
6aa2e1cebb | i18n: extract and translate remaining | ||
|
|
90b779356f | chore: update deps | ||
|
|
da38faa9be |
ci: pnpm 12, pnpm/setup v3, faster and pinned CI, single Vercel deploy workflow (#577)
* ci: move to pnpm 12, pnpm/setup v3 and faster, pinned CI
pnpm 12.6.0 is declared in devEngines.packageManager instead of
packageManager, so pnpm/setup, the Dockerfile and local installs all pick
the same version; the lockfile records the resolved binary. Every workflow
moves to pnpm/setup v3, and the Vercel workflows gain a setup step so
`vercel build` runs with that pnpm rather than whatever is on the runner.
CI time:
- ci runs format check, lint, unit tests, typecheck and build as parallel
steps instead of one after another.
- E2E builds the app once and shares dist with the three browser jobs
instead of rebuilding it in each.
- ci and E2E cancel superseded runs on the same ref.
- The Docker latest/baseurl workflows no longer repeat ci's checks. They
run on workflow_run after ci succeeds for a push, and build the commit
ci tested.
Runners are pinned to ubuntu-26.04-arm. CodeQL stays on x64
(ubuntu-26.04): only the x64 image ships the CodeQL bundle in its tool
cache. The Playwright cache key now includes the runner architecture.
Every action is pinned to its latest release by commit SHA with a version
comment, the Dockerfile base images by digest, and the pnpm and Vercel CLI
installs to exact versions, matching the Renovate presets already enabled
(helpers:pinGitHubActionDigests, docker:pinDigests).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017s2w39tKNdBdD8kyfThuLy
* ci: deploy to Vercel from one workflow with previews and a concurrency group
Replaces sharevb-vercel-preview.yml and sharevb-vercel-prod.yml with
deploy.yaml, which builds here and deploys the prebuilt output:
- One concurrency group per ref with cancel-in-progress, so a burst of
pushes costs one deployment instead of one per push.
- A GitHub environment per run (Production or Preview), which restores the
Environments sidebar and the PR's "View deployment" button.
- Pull requests build their own head commit, named after the PR branch so
Vercel shows the branch rather than "HEAD"; runs from forks are skipped,
since they get no secrets.
- Fails early on missing secrets, refuses to deploy a build without
index.html, and pins the Vercel CLI.
The production hostname for sitemap.xml and robots.txt comes from the
VERCEL_PRODUCTION_URL repository variable instead of being hardcoded, so
the same file serves any deployment. Secrets can live on the repository
or on the Production/Preview environments.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017s2w39tKNdBdD8kyfThuLy
* build: stop compiling tree-sitter's native addon
curlconverter depends on tree-sitter and tree-sitter-bash for its Node
shell parser, but the app only uses curlconverter in the browser, where its
`browser` field swaps in web-tree-sitter (WASM). The native addon is never
loaded.
Building it anyway broke installs: tree-sitter 0.21 ships prebuilds only for
darwin-x64 and win32-x64, so Linux compiles it from source, and its C++17
flags fail against Node 24.21's headers, which require C++20. That is what
failed pnpm install on the arm64 runners.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017s2w39tKNdBdD8kyfThuLy
* ci(e2e): run the browser jobs on x64
On ubuntu-26.04-arm the Playwright suite ran over 7x slower: chromium was
still in the test step after 27 minutes, against under 4 on x64. The build
job stays on arm; its output is architecture-independent.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017s2w39tKNdBdD8kyfThuLy
* test(e2e): stop the preview server with SIGTERM so runs exit
pnpm 12 starts the script it runs in its own process group. Playwright
stops its webServer by SIGKILLing the `pnpm preview` process group, which
no longer contains vite: vite survives, keeps the output pipes open, and
Playwright waits on it forever. The E2E jobs finished every test and then
hung until the job timeout.
pnpm 12.6 forwards SIGTERM to the script it runs, so stop the server with
SIGTERM instead. Locally with pnpm 12.6.0: 112 tests in 1.8 min, clean
exit, nothing left listening on the port.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017s2w39tKNdBdD8kyfThuLy
* Revert "ci(e2e): run the browser jobs on x64"
The slowdown blamed on arm was the Playwright webServer hang fixed in the
previous commit: every test had finished and the job was waiting on an
orphaned vite process. The suite is not slower on arm, so the browser jobs
go back to ubuntu-26.04-arm like the rest.
This reverts commit
|
||
|
|
7fc4b79172 |
feat(Timezone Converter): add POSIX string filterable list
Fix #579 |
||
|
|
641fa857b4 |
perf(bundle): improve initial load + loading of tools (#575)
* perf(bundle): improve initial load + loading of tool Render the sider once and only build the parts of it that are visible. - App.vue renders BaseLayout around the layout switch instead of inside each layout, so moving between a plain route and a tool route no longer unmounts and rebuilds the whole sider (~460 menu items) on every navigation. - CollapsibleToolMenu mounts a category's items the first time it opens. Every category starts collapsed, so the menu was built entirely out of view. - Its menuOptions computed no longer folds in the collapsed/active flags, which rebuilt every category's tools array -- and re-rendered every item -- per route change. They are read from the template instead. - MenuItemTooltip measures truncation with scrollWidth/clientWidth rather than a canvas measureText(), dropping a throwaway <canvas> and a getComputedStyle per menu item. Production build, 3 runs each, fresh profile per run: first contentful paint 2476-2735ms -> 814-974ms main-thread blocking 1806-2024ms -> 250-294ms requests at boot 384 -> 208 click a tool from home 991-1014ms -> 178-197ms switch between tools 281-322ms -> 74-125ms Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Fix small width in mermaid exporter --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: sharevb <sharevb@gmail.com> |
||
|
|
0f4c7b1d68 |
feat(JSON Editor): store data and add an auto height option
Fix #572 |
||
|
|
c96fd39482 |
feat(new tool): Restic Command Generator (#573)
Generates restic CLI commands, with the focus on getting data back out of a repository when the Backrest UI is not available: a full restore, a restore limited to some files or a subfolder, a single-file dump, or a FUSE mount. Covers the backends Backrest points at (S3 compatible such as Backblaze B2, B2 native, local, SFTP, REST, rclone, Azure, GCS, raw URI), builds the matching environment setup without ever putting a secret in the command (the default reads them with `read -rs`), and turns the Backrest plan and instance IDs into the `plan:` / `created-by:` tag filters restic expects. Also generates the whole recovery sequence (snapshots, find, ls, restore, mount) from the same repository settings, and ships a small Backrest cheat sheet pointing at the config file, the data directory and the tag formats. Generator only: nothing is executed and no input leaves the browser. |
||
|
|
bc1d9a3199 |
feat(Keys Generator): add fingerprint
Fix #574 |
||
|
|
c80a08be64 |
feat(new tool): EPC QR Code Generator
Fix #570 |
||
|
|
0039bd7213 |
feat(new tool): URL Redirection Checker
Depending on https://github.com/sharevb/network-utils-ws Fix #550 |
||
|
|
62ab0bf92f |
fix: c-link to vs href
Fix #569 |
||
|
|
a049d1c519 | chore: remove fm:check ypass | ||
|
|
bc44870665 | chore: global code formatting | ||
|
|
5bf94bc567 |
Restructure and enhance cheat sheets for improved readability (#566)
* docs(cheatsheets): expand and align the chmod, git, docker and swarm memos Unify the four cheat sheets on one layout: short intro, emoji section headings, grouped command blocks with aligned inline comments, reference tables and a resources section. Placeholders are consistently <angled>. - chmod: ls -l breakdown, octal and symbolic tables, special bits, umask, recursive/selective changes, recipes, related commands and gotchas; fix the directory access matrix (r alone does not grant file access) and the --preserve-root default - git: config and aliases, staging, commit, branching, merge/rebase with conflict flow, remotes, stashing, inspection, cherry-pick, tags, undo with a reset-mode table, cleaning, bisect, submodules and worktrees - docker: contexts and events, build flags, registries, run/exec/inspect, volumes and mounts, networks, the full compose workflow, cleanup and one-liners - swarm: required firewall ports, node and manager operations, live service updates, job modes, placement expressions, publish modes, health checks, secret and config rotation, task states and a troubleshooting table * docs(cheatsheets): put descriptions above commands so each line copies clean Trailing inline comments meant selecting a single command also picked up the padding and its description. Move every description onto its own line above the command it documents, keeping one code block per topic. - each command now stands alone on its line: triple-click copies exactly the command, nothing else - no comment column to re-pad when a longer command is added later, so adding a line no longer reindents the whole block - code lines drop from a median of 78 columns to ~22 (p90 42), so blocks no longer scroll sideways on narrow screens - wrap the three remaining long commands over several lines - reword the descriptions that only made sense trailing a command * docs(cheatsheets): rework the tmux, screen, zellij, nano, jq, zpool, CSS and JSONPath memos Bring eight more cheat sheets onto the same layout as the Docker and Git ones: short intro, emoji section headings, one code block per topic with the description above each command, reference tables, resources at the end. - tmux: session/window/pane/copy-mode tables, scripting with send-keys and capture-pane, a starting .tmux.conf - screen: shared and detached attach modes, split regions, copy mode, logging and monitoring, nested-screen prefix - zellij: correct the pane-mode bindings (d/r split, not v/h), add tab, resize, move, search and session modes, layouts, zellij run/edit/action - nano: add the command-line options and .nanorc settings the sheet was missing, drop the stray H1 and broken headings - jq: flags, core syntax, object/array/string tables, conditionals, variables, reduce, and runnable recipes; drop the stale AWS AMI note and the HTML pipe entities - zpool: vdev and support-vdev types, import/export, properties, dataset and snapshot/replication commands, tuning notes - CSS selectors: split one 60-row table into basic, combinator, attribute, structural, state, form, functional and pseudo-element groups; add :is()/:where()/:has() and a specificity table - JSONPath: RFC 9535 functions, worked example document, filter operators * docs(cheatsheets): rework the Dockerfile, Compose and kubectl memos - Dockerfile: instruction reference table, BuildKit cache/secret/bind mounts and heredocs, COPY --chown/--chmod/--from, HEALTHCHECK, STOPSIGNAL, a CMD vs ENTRYPOINT table, build commands and a worked multi-stage example - Compose: drop the obsolete version: framing, merge the two duplicated "Compose vs Swarm" sections into one table, correct the claim that file-based secrets are Swarm-only, and add depends_on conditions, profiles, watch mode, include/extends/anchors, env interpolation and the full CLI section - kubectl: replace the removed rolling-update and the retired Heapster section, add contexts, custom-columns and JSONPath output, rollouts, debug containers, port-forward, secrets, labels, node maintenance and one-liners; tag the code blocks so they highlight * docs(cheatsheets): rework the sed, regex and common-regex memos - sed: how the pattern space works, an addressing table, the full command reference including hold-space and branching, multi-line recipes, and a warning about BSD/macOS -i; merge the duplicated deletion and addressing sections - regex: add flags, lazy quantifiers, named groups and backreferences, Unicode property escapes, replacement tokens, the JavaScript methods that expose groups, and a gotchas section (stateful /g, catastrophic backtracking, escaping user input) - common-regex: rewrite the patterns that markdown escaping had mangled into unusable text, group them by subject, and add UUID, semver, CIDR, MAC, ISO 8601, duration, log-line and CSV patterns Every pattern in common-regex now compiles, and the ones people copy most (IPv4, UUID, semver, E.164, ISO dates, password rules, slug, duration, MAC) were checked against matching and non-matching input. * docs(cheatsheets): rework the XPath, conventional-commits and RJ45 memos - XPath: give every table a CSS-equivalent column, fix the broken "only children of type" expression, flag which functions are 2.0+ and give the 1.0 workarounds for ends-with and case folding, add the axes short forms, worked examples, and how to run XPath from devtools, xmllint, lxml, Selenium and Playwright - conventional commits: types table with the release effect each one has, description do/don't table, footer reference, both ways to mark a breaking change, a version-bump table, and husky v9 hook syntax - RJ45: keep the colour swatches and the pinout image, add what each pin carries on 10/100 vs Gigabit, the PoE standards table (correcting the claim that the blue pair is the PoE pair), gigabit crossover, Cat8, length and solid-vs-stranded rules, and a fault-finding table * docs(cheatsheets): rework the nginx and PowerShell memos - nginx: the whole sheet was a single 218-line code block; split it into sections with a service/CLI block, a file-layout table, location matching priority, root vs alias, reverse proxy and WebSocket headers, load-balancing methods, TLS, rate limiting, caching and gzip, a variable reference and a 502/504 troubleshooting table - PowerShell: add discovery (Get-Help/Get-Command/Get-Member), functions and param blocks, try/catch and error preferences, Invoke-RestMethod and JSON/CSV conversion, services, jobs, remoting, modules and execution policy, PowerShell 7 operators, an alias table, and repair the mangled escape-character rows * docs(cheatsheets): rework the vim and bash memos Both sheets were a single unbroken code block with ASCII banners, so the whole page rendered as one <pre> with nothing to scan. Rebuild them as sections with key/action tables and runnable blocks. - vim: explain the count + operator + motion grammar, add the text-object table (ciw, ci", da(), registers and why "0p exists, the :g and :v global commands, folds, completion, diff mode, undo by time, a :set reference and a starter vimrc - bash: parameter expansion, arrays including associative ones, the test operator tables, redirection and process substitution, job control and traps, set -euo pipefail with its caveat, shellcheck, and an ANSI colour table in place of sixty lines of colour variables The vim sheet dropped roughly a hundred lines of one person's leader-key mappings and plugin bindings (NERDTree, Taglist, sparkup, PHP DOC), which only worked with their dotfiles; a note now explains that leader mappings come from your own vimrc. |
||
|
|
a5607e04ad | add proxmox helper script (#568) | ||
|
|
39c616f609 |
feat(QRCode Generator): add embeddable link and cropy dataurl
Fix #555 |
||
|
|
002a211ca5 |
Enhance Docker Swarm documentation (#564)
Updated Docker Swarm documentation with improved clarity and additional details on commands and features. |
||
|
|
0a1f5dc450 |
feat(docker): serve the app from any subpath with a runtime BASE_URL (#565)
* feat(docker): serve the app from any subpath with a runtime BASE_URL
BASE_URL was a build argument, so hosting under a subfolder meant building
your own image (or pulling the separate baseurl-it-tools tag, which is only
ever right for /it-tools/). Make it a runtime setting instead, so the regular
image works anywhere:
docker run -e BASE_URL=/it-tools/ ghcr.io/sharevb/it-tools:latest
The build is now path-agnostic. Vite's base is relative, so hashed assets and
lazy chunks resolve against the chunk that imports them, and the single
absolute anchor left in the output is a `<base href="/">` injected into
index.html. nginx rewrites that one tag per request (sub_filter) from the
normalised BASE_URL, and the app reads its base back from it at runtime
(src/utils/base-url.ts) for the router and for every URL it builds into
public/ -- import.meta.env.BASE_URL is meaningless in a relative build.
Also handled:
- both reverse-proxy styles: the prefix may reach the container (stripped by
the rewrite) or be stripped by the proxy first (nothing to do). The assets
location matches with or without it, so a missing chunk is still a 404
rather than the SPA shell.
- `/it-tools` redirects to `/it-tools/`, with a relative Location so the
scheme of the proxy hop does not leak into it.
- the PWA: manifest URLs are relative to the manifest, workbox precache
entries relative to the service worker, and the worker is registered
against the runtime base rather than the build-time one.
- BASE_URL is normalised (`it-tools`, `/it-tools`, `/it-tools/` all work) and
rejected if it is not a plain path, since it lands in an HTML attribute and
in an nginx regex.
Defaults are unchanged: with BASE_URL unset the rendered config and the
served page are what they were, except that index.html loses ETag/Last-Modified
to sub_filter. On a read-only filesystem the template cannot be re-rendered,
so BASE_URL is ignored there and the container now says so, like it already
had to for PORT.
Building with --build-arg BASE_URL still works but only moves the image
default; the baseurl-it-tools tag is now just latest with that default.
Closes sharevb/it-tools#403
* fix(docker): restore the PWA update reload, escape BASE_URL in the nginx regexes
Follow-up from review of the runtime BASE_URL change.
- registerSW() in autoUpdate mode reloaded the page when a newly deployed
worker took over (workbox-window's `activated` handler); hand-rolling the
registration dropped that, so a tab kept running the previous bundle until
it navigated. Reimplemented on `controllerchange`, guarded so a first
install -- which also claims the page -- does not reload. Verified by
counting document loads across an install and a simulated deploy: 1 load on
first visit, exactly 1 reload when a new worker takes over.
- The comment justifying the hand-rolled registration was wrong: register()
does resolve a relative URL against `<base href>`. The real reason is
workbox-window's own urlsMatch(), which resolves against location.href, so
a relative sw URL misidentifies the worker on a route deeper than one
segment. Comment now says that.
- BASE_URL allows `.`, which is a metacharacter in the two nginx regexes it
is spliced into: `/it.tools/` also matched `/itXtools/`. The entrypoint now
exports regex-escaped forms for those, keeping the literal value for the
sub_filter replacement and the redirect target.
- Dropped `$uri/` from try_files. Nothing in the build is a directory with an
index, so the only thing it ever produced was nginx's trailing-slash
redirect -- computed after the prefix rewrite, so `/it-tools/figlet-fonts`
answered `301 /figlet-fonts/` and bounced the browser out of the app.
- The sub_filter comment claimed index.html was the only response losing
ETag/Last-Modified; public/visualsubnetcalc/calc.html is HTML too and is
equally affected. Comment corrected.
- README: in the prefix-stripping proxy setup, `/it-tools` without the
trailing slash never reaches the container, so the proxy has to redirect it
(as the sample does). Said so.
- The new e2e test reloaded a page that had just started pulling in a tool's
chunks; WebKit cancelled the load ~1 run in 3 (the app reloads itself on an
aborted chunk fetch). It opens the URL in a second tab instead: 8/8 on
WebKit, 3/3 browsers green.
* fix(build): validate BASE_URL before it reaches the <base href>
From Copilot's review of #10.
The container validates its runtime BASE_URL, but the build-time one went
straight into an HTML attribute unchecked: a value carrying a quote rewrote
the tag around it, and one carrying a space or `..` quietly produced a page
that loads from the wrong place. Apply the same rule the entrypoint does --
a plain path of unreserved characters -- and fail the build otherwise.
Also: "can not" -> "cannot" in the read-only filesystem warning.
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
||
|
|
ec740dd063 |
ci: rework the test and lint toolchain — per-browser E2E, scoped jsdom, type-aware oxlint (#561)
* ci(e2e): one job per browser with three workers Replace the 3-way shard matrix with a per-browser matrix. Each job now runs one Playwright project with three workers instead of three jobs each running a mixed slice of all browsers at one worker. The old layout gave each of three runners a single worker, so each job used one of its four cores; a browser failure also showed up as "shard 2/3" with no indication of which engine broke. - `workers: 1` -> `3` on CI. Measured on a 4-core box: 9.4 min at one worker vs 5.1 min at three, with the box ~95% busy. A fourth worker added nothing and left no core for the preview server. - `fail-fast: false` so one engine failing still reports the other two. - Install and cache only the browser a job actually needs, instead of all three in every job. - Fix the cache key, which read `.dependencies.playwright` and always resolved to `null`; the package is `devDependencies["@playwright/test"]`, so the key never changed when Playwright was upgraded. - `set_node_mem.sh` grows a `NODE_MAX_OLD_SPACE_MB` override, used to cap each worker at 4GB. Playwright workers inherit `NODE_OPTIONS`, so otherwise every worker claims a machine-sized heap ceiling. The script is now POSIX. It is sourced from package.json scripts, which run under dash, where `[[` does not exist -- every run was logging "[[: not found" and silently falling through to the Linux branch, so the macOS detection never worked when invoked that way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * refactor(set_node_mem): capture memory sizes before the arithmetic Addresses review feedback on the sourced heap-sizing script. Reads closer to the original, which also assigned the raw value first. Behaviour is unchanged: dash still produces --max-old-space-size=15051 by default and honours NODE_MAX_OLD_SPACE_MB. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * fix(e2e): give CI more timeout headroom now that workers share a runner The webkit job failed on `markdown-diff`, which mounts a Monaco diff editor -- the heaviest tool in the suite -- on the slowest engine: 1 failed [webkit] markdown-diff Has correct title 1 flaky [webkit] markdown-diff Diff editor is visible with two panes 107 passed (9.3m) Both are first-paint timing, not behaviour. The 15s expect timeout was sized for one worker per runner; with three sharing four cores, first paint of a lazy-loaded tool takes longer, and the failure survived two retries. Raise the CI budget to 30s for assertions. The test timeout has to move with it -- it defaults to 30s, so a 30s expect timeout would trip the test timeout first and report a timeout instead of the failing assertion. Local runs keep the previous 15s/30s. Timeouts are upper bounds, so passing tests are unaffected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * fix(e2e): drop the inline timeout that caps markdown-diff below the CI budget Raising the CI expect timeout to 30s fixed one of the two webkit failures in markdown-diff but not the other: before: 1 failed + 1 flaky, 107 passed after: 1 failed, 108 passed The surviving failure asserts the title with an inline `{ timeout: 15000 }`, which overrides the global expect timeout, so it kept the old budget while its neighbour picked up the new one. The inline value only restated what the global used to be, so removing it is a no-op locally (still 15s) and lets CI use its 30s budget. The four inline overrides in mermaid-exporter are left alone: those raise the timeout to 30s rather than capping it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * perf(test): scope jsdom to the suites that need it `test:unit` ran `vitest --environment jsdom`, which builds a jsdom for every test file. Only 7 of 128 need one -- the other 121 are pure functions and pass unchanged under the node environment. Measured on a 4-core box, `pnpm test`, warm cache: before 89s wall, environment 128.79s, tests 4.70s after ~56s wall, environment 7.37s, tests 5.30s Environment setup was the single largest cost in the run and is now ~7s. The tests themselves were always ~5s. Default to the node environment and let the 7 DOM-dependent suites opt in with a `// @vitest-environment jsdom` docblock: src/ui/c-input-text (@vue/test-utils mount) src/ui/n-input-number-i18n (@vue/test-utils mount) src/tools/certificate-key-parser (webcrypto-liner-shim) src/tools/extract-text-from-html src/tools/markdown-preview src/tools/file-splitter src/tools/django-secret-generator Same 128 files and 1035 tests pass before and after. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * test: drop jsdom from three more suites and fix two assertions Down from 7 jsdom suites to 4. The three removed did not need a DOM; they needed it by accident. certificate-key-parser The service and its infos module each did a side-effect `import 'webcrypto-liner-shim'`. That shim polyfills WebCrypto for browsers without a secure context (see README: WebCrypto needs HTTPS), and it touches browser globals at import time, so pulling it into a node process fails before any test runs. Node has WebCrypto natively, so the polyfill only belongs on the browser path. Move the import to certificate-key-parser.vue, which is what pgp-keygen.vue and pgp-encryption.vue already do. It now also evaluates before sshpk rather than after it, and no longer loads eagerly through the tool's infos module. That let the test drop its jsdom workaround too: it was replacing global.TextEncoder/TextDecoder with the text-encoding-utf-8 polyfill, which node does not need. The `no-restricted-globals` disable existed only for those writes and is gone with them. Side effect: the run no longer emits the shim's asm.js linking warning, which was the only warning left in the unit suite. extract-text-from-html `validateHtml` parsed the input with DOMParser, discarded the document, and validated with a regex instead. `parseFromString` with 'text/html' recovers from bad markup rather than throwing, so the catch was unreachable and the whole block was dead -- and the only reason the file needed a DOM. django-secret-generator Used `window.crypto`; `globalThis.crypto` is the same API in browsers and in node. Two assertions did not test what they claimed: expect(getTextFromHtml('<p>..</p>')).toString(); `.toString()` on the assertion object asserts nothing -- this passed even if the function returned null. Now checks the type. expect(getSecretKey()).toMatch(/[a-z0-9!@#$%^&*(-_=+)]{50,60}/); `toMatch` searches rather than anchors, so any key of 50 chars or more passed regardless of length. Split into an explicit length range and an anchored charset check. The old class was also wrong: `(-_` reads as the range `(` to `_`, which accepts digits and uppercase. Also moved a valid-html case that sat in the invalid block, and fixed the `invlid` / `django-secret-generato` typos. 128 files pass, 1035 tests -> 1036 (the django assertion is now two). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore(deps): drop the now-unused text-encoding-utf-8 The certificate-key-parser test was the only consumer: it replaced global.TextEncoder/TextDecoder with this polyfill so the suite could run under jsdom. That workaround went away when the suite moved to the node environment, which provides both natively. pnpm also prunes an orphaned transitive crypto-js@4.2.0, whose own metadata marks it as no longer maintained. The lockfile change is 22 deletions and no additions. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * ci: enable oxlint type-aware linting, drop typecheck from build and CI Adds oxlint-tsgolint and turns on `options.typeAware`, which brings 59 type-aware rules from typescript-eslint into `pnpm lint`. It found 59 issues; `--fix` resolved 3 (useless `= undefined` defaults). The remaining 56 are semantic -- floating promises, base-to-string, misused string spread -- spread over ~20 files, so they are staged as `warn` rather than fixed blind in a CI change. Lint exits 0 and the findings are visible in the output, ready to burn down by rule. TypeScript stays on 6.0.3. The docs ask for TypeScript 7+, but that is about tsgolint's own toolchain, not the project's: oxlint-tsgolint ships a self-contained binary with no npm dependencies, and produces the same 56 findings against TypeScript 6. Upgrading the project to TypeScript 7.0.2 was tried and reverted -- it breaks the build: [@vue/compiler-sfc] No fs option provided to `compileScript` in non-Node environment. File system access is required for resolving imported types. Isolated by rebuilding with the same scripts on 6.0.3, which passes. TS 7's native port also drops the `./lib/tsc` subpath export, so vue-tsc cannot start at all -- neither 3.3.6 nor the current 3.3.10. Script and workflow cleanup: - `build` no longer runs `vue-tsc --noEmit` first; it just builds. - The `ci` workflow drops its Type check step. It already runs `pnpm lint`, which now carries the type-aware rules. No other workflow had a typecheck step. - `precommit` and the PR template drop `pnpm typecheck` for the same reason. The `typecheck` script itself is kept, and so is vue-tsc. tsgolint analyses no .vue files at all -- 0 of the 59 findings came from one -- so vue-tsc remains the only thing that type-checks single-file components, and deleting it would drop that coverage with nothing replacing it. It is simply no longer wired into the build or CI. Renovate's TypeScript toolchain group gains oxlint-tsgolint, whose version tracks TypeScript releases. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * refactor(oxlint): move config to oxlint.config.ts Replaces .oxlintrc.json with a typed config built from oxlint's own `defineConfig`, so rule names and options are checked by the editor instead of being free-form JSON strings, and the staged type-aware rules can carry an explanation next to them. Verified as a faithful translation by diffing `oxlint --print-config` between the two: identical resolved rule set (167 rules), no rule added, dropped or re-levelled, and `options.typeAware` equal. Same 56 warnings and 0 errors either way. TypeScript configs are auto-discovered but marked experimental upstream and require running under Node, which `pnpm lint` already does. Also records why vue-tsc stays, since oxlint's vue plugin invites the opposite conclusion: those 46 vue rules are style and correctness lint rules, not a type checker. Planting const deliberateTypeError: number = getSecretKey(); in a .vue script block is reported by neither `--type-aware` nor `--type-check` -- oxlint exits 0 -- while vue-tsc catches it as TS2322. tsgolint only analyses .ts files. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * ci: restore typecheck and run lint + typecheck on every build path oxc-project/oxc#15761 ("oxlint: better vue support") is the tracking issue for Vue in oxlint. It is open, unimplemented, and scoped to parsing template bindings so structural lint rules can work -- not to type checking. Even once it ships it would not cover what vue-tsc does, and the maintainer notes eslint-plugin-vue cannot be fully replicated because Vue templates carry no JavaScript bindings for the linter. So vue-tsc stays and goes back into CI. Confirmed the gap is real by planting `const x: number = getSecretKey()` in a .vue script block: oxlint exits 0 under both --type-aware and --type-check, vue-tsc reports TS2322. Every job that runs `pnpm build` directly now runs lint and typecheck first: sharevb-ci + typecheck sharevb-docker-nightly-release + typecheck sharevb-docker-realease-latest + typecheck sharevb-docker-realease-baseurl + typecheck sharevb-github-pages-publish + lint, typecheck (had none) sharevb-releases + lint, typecheck (had none) The two publish workflows were building and shipping without any check at all. Left alone: the nightly github-release job, already gated by `needs: ci` on the same commit, and the e2e workflow, whose three browser jobs build on the same commit that the ci workflow is already checking in parallel. `precommit` and the PR template get typecheck back for the same reason. oxfmt config moves to oxfmt.config.ts alongside oxlint's, using oxfmt's own defineConfig. Same 832 files are flagged before and after, so the translation is faithful. Format checking is deliberately NOT wired into CI yet: `pnpm fmt:check` currently fails on 832 of 1613 files (410 .vue, 359 .ts, 50 .md, 12 other). The scripts exist but have never been enforced, so the tree has drifted. Enabling the gate needs a repo-wide reformat, which belongs in its own commit rather than buried here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * ci: report formatting drift without enforcing it Adds `pnpm fmt:check` to the ci workflow with continue-on-error, so the 832 files that predate oxfmt being run in CI are visible on every PR without blocking anything. Drop continue-on-error once a repo-wide reformat lands. Only the ci workflow gets it. It is the one that runs on pull_request, so it is where a non-blocking signal is actually read; adding it to the docker and release workflows would just add noise to logs nobody opens. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * refactor(test): pin the timezone in config instead of every script `TZ=UTC` was repeated across four scripts, including once redundantly (`test` set it and then called `test:unit`, which set it again). It is genuinely load-bearing for the unit suite. Running vitest on America/New_York fails 7 tests across 5 files -- date-time-converter, days-calculator, crontab-generator and friends assert on formatted dates and offsets. Moved to `test.env` in vite.config.ts, which is enough on its own: the full suite passes with the host on America/New_York and on Asia/Tokyo with no inline prefix. That also fixes `pnpm coverage`, which never had the prefix and so would fail those same 7 tests on any machine not set to UTC. For e2e it was doing nothing. The browser timezone is already pinned by `timezoneId: 'Europe/Paris'`, and the specs do no date maths on the node side -- the one `Date.now` override runs inside `addInitScript`, so it is browser-side. The timezone-sensitive specs pass on Asia/Tokyo without it. Pinned in playwright.config.ts anyway so the runner stays deterministic if a spec ever does compute a date in node. Also switches `test` from `npm run` to `pnpm run`, since everything else in the repo uses pnpm. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: drop the `test` alias in favour of `test:unit` `test` was a pass-through to `test:unit` and nothing else, so it only added a level of indirection and a second name for the same thing -- confusing next to `test:e2e`, which is a different suite. Repointed all five callers: the ci, nightly-release and two docker release workflows, plus the README's "Run Unit Tests" snippet. Note `pnpm test` no longer resolves, since npm's implicit test lifecycle has nothing to fall back on now. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * refactor(e2e): fold test:e2e:dev into test:e2e The two scripts were not two environments, they were two answers to "who owns the web server": test:e2e Playwright starts `pnpm preview` on :5050 and tests the production build test:e2e:dev assumes `pnpm dev` is already up on :5173 and starts nothing That is one variable, not a second workflow, so it does not need a second script. The config now derives it: if E2E_BASE_URL points somewhere other than the preview URL, you are supplying the server and Playwright leaves the lifecycle alone. NO_WEB_SERVER is gone -- it only ever restated what a custom base URL already implies. Renamed BASE_URL to E2E_BASE_URL along the way. vite.config.ts reads BASE_URL as the app's base path (`/it-tools/`, set by the Pages and Docker builds), so one exported value meant two incompatible things and would have pointed Playwright at a path instead of a URL. Both paths verified: pnpm test:e2e 5/5, preview started E2E_BASE_URL=http://localhost:5173 pnpm ... 5/5, dev server reused Documented both in the README, which had no e2e section at all -- the script was the only place the dev flow was written down. Also notes that a cold dev server compiles on demand and can blow the assertion timeouts on a first run; that cost 2 failures until the routes were warmed. Also fixes webServer.command, which shelled out to `npm run preview`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: delete set_node_mem.sh The script raised the V8 heap to total RAM minus 1GB and was sourced by build, test:unit and test:e2e. Nothing needs it any more. The build does not come close to the heap. It completes on Node's default (2096MB here) and still completes when capped at 512MB -- a thirtieth of what the script was handing out: cap 15051MB (script) 92s, 93s default 2096MB 94s, 103s cap 1024MB 91s cap 512MB 95s Unit tests are the same story: 35s and 37s with, 36s and 37s without. No measurable difference anywhere, so the script was not buying speed either. The reason is that the build is not a JavaScript-heap workload. It peaks around 6.5GB of system memory while running fine under a 512MB heap cap, because rolldown does the work in Rust, outside V8. The README's "you need around 16GB" dates from the old JS bundler; corrected to ~8GB with the measured figure. Removing it also retires two things it dragged along: the NODE_MAX_OLD_SPACE_MB override added for Playwright, which existed only because every worker inherited a machine-sized ceiling from this script, and a POSIX bug where `[[` failed under dash on every single run. Verified with NODE_OPTIONS unset, so at the 2096MB default CI will see: build 87s, 129 files / 1072 unit tests, e2e 5/5. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * fix(e2e): key the browser cache on the installed Playwright version The key read the range from package.json, so it was `^1.62.0` rather than `1.62.0`. Those agree today, but the range also matches 1.62.3 and 1.63.0: a lockfile bump inside the same range leaves the key unchanged, so the run restores browsers for the old version and the cache is never refreshed, because that key already exists. Read node_modules/@playwright/test/package.json instead. pnpm/setup has already installed dependencies by this step, so the resolved version is available. Raised by Copilot on the upstream PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
2912cf3eb9 |
Fix regex to clean base64 data URI (#563)
Fix #562 |
||
|
|
fbc7d47fbd |
ci: use pnpm/setup for pnpm and Node setup, pin Node in package.json (#560)
* ci: use pnpm/setup for pnpm setup and install Replace the corepack bootstrap + actions/setup-node + separate `pnpm install` steps with a single `pnpm/setup` step, which installs pnpm (version read from package.json `packageManager`), installs Node, caches the pnpm store and runs `pnpm install`. Node 24 stays pinned via `runtime: node@24`, and the GitHub Pages workflow drops `pnpm/action-setup` in favour of the same step (it now caches the store too). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: pin Node in package.json, bump pnpm to 11.22.0 Move the Node version out of the workflows and into package.json, so the `pnpm/setup` steps are just `cache: true`: - `engines.node` pins Node 24 as package metadata. - `devEngines.runtime` is the field `pnpm/setup` actually reads to pick the runtime, and pnpm itself uses it to run scripts, so it is needed for the pin to take effect. Bump `packageManager` from pnpm 11.11.0 to 11.22.0 (latest 11.x). pnpm records the runtime in the lockfile (`node@runtime:24.19.0`), and the 11.22.0 resolver writes peer suffixes differently from 11.11.0, so pnpm-lock.yaml is regenerated. Lint, typecheck, unit tests and build all pass on the updated lockfile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: bump .nvmrc to Node 24.19.0 The repo was already on Node 24 everywhere else (Dockerfile, workflows, and now engines/devEngines in package.json) while .nvmrc still selected 22.19.0. Align it with the rest, matching the node@runtime:24.19.0 version pnpm resolved into the lockfile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
d39255ac20 |
fix(deps): move the two remaining deprecated direct dependencies onto supported versions (#559)
* fix(deps): move @xmldom/xmldom off the versions upstream flagged as critical Upstream deprecated 0.8.13 and 0.9.10 with 'this version has critical issues, please update to the latest version'. 0.8.14 and 0.9.11 are the patched releases of those same lines. The direct dependency moves to ^0.8.14, which also lifts xml-crypto and xml-encryption since both accept the whole 0.8 line. @boxyhq/saml20 pins 0.9.10 exactly, so a version scoped override takes it to 0.9.11. epubjs asks for ^0.7.5 and the 0.7 line has no release that is not deprecated, so 0.7.13 stays until epubjs moves; overriding it across two minors of an xml parser is not something to do blind. Also refreshes the stale minimumReleaseAgeExclude entry, which still named 0.8.12 and 0.8.13. The policy is not currently switched on, but 0.8.14 was published three days ago and the list is where this repo records that. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * test(crontab-generator): pin the cron dialect detection and the execution times getLastExecutionTimes was only asserted to return five items, and getCronType only covered four expressions. Neither is enough to move a cron library under. Adds a classification table spanning the standard and aws dialects, including the six field expressions where they overlap, and freezes the clock so the returned execution times can be pinned exactly, timezone offsets included. No behaviour change: this is the reference the cron-parser v5 upgrade has to reproduce. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * fix(deps): upgrade cron-parser to v5, keeping the aws dialect detected Upstream deprecated v4 with 'v4 is no longer maintained, upgrade to v5'. The rename is mechanical (parseExpression -> CronExpressionParser.parse) but the upgrade is not, because v5 accepts the six field aws dialect that v4 rejected. getCronType relied on that rejection: it tried the standard parser first and treated a throw as the signal to fall through to event-cron-parser. Under v5 '0 11-22 ? * MON-FRI *' parses as standard, so aws expressions would have been classified as standard, given the wrong next execution times and reported as invalid whenever the aws dialect was requested. Detection now keys off the '?' marker, which AWS EventBridge requires in one of the two day fields and which standard cron gives no meaning to. Checked against v4 over a 32 expression corpus spanning both dialects: identical classification everywhere, including '* * * * * *', which is valid in both and stays standard. getLastExecutionTimes keeps returning string[]: v5 types toJSON() as nullable and the caller joins the array, so a hole would have silently rendered as a blank line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * fix(build): stub bare fs/promises, which cron-parser v5 reaches for cron-parser v5 adds CronFileParser, exported from the package entry, and it does require('fs/promises') to read crontab files. The browser build has no business loading that, and the alias list only stubbed 'node:fs/promises'. Vite matches aliases by prefix, so the bare 'fs' entry rewrote 'fs/promises' into '_empty.ts/promises' and the build failed with UNLOADABLE_DEPENDENCY: 'Not a directory'. The new entry has to sit before 'fs' for that reason. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * refactor(crontab-generator): run each cron parser at most once per classification From review feedback. getCronType could evaluate the standard branch twice for an expression that is neither dialect, and getLastExecutionTimes asked for the type twice, which repeated the whole classification. The '?' marker now selects which dialect to try first and each parser runs once; the caller keeps the type in a local. Behaviour is unchanged, the 30 assertions of the untouched test file still pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
903ffb8b90 |
refactor(websocket-tester): use the native WebSocket instead of w-websocket-client (#558)
* refactor(websocket-tester): use the native WebSocket instead of w-websocket-client
w-websocket-client ships a single 1465 byte UMD that wraps the platform
WebSocket: it builds `${url}/?token=${token}`, wires four handlers and returns
the socket. It nevertheless declares wsemi and lodash-es as runtime
dependencies, which its published build never imports, and wsemi alone pulls in
20 packages. Installing all of that to avoid writing twenty lines is a bad
trade, so the wrapper now lives here, behind tests.
Removes 14 packages from the lockfile (w-websocket-client, wsemi, diff2html,
tippy.js, @popperjs/core, seamless-scroll-polyfill, tree-kill, eventemitter3,
xxhash-wasm and their own transitives), and drops the Node-only `ws` from the
browser app's dependency graph; `ws` now only comes in through ethers.
Two follow-on effects:
- wsemi was the only subdependency wanting xlsx, which is why the xlsx CDN
override forced pnpm's blockExoticSubdeps protection off repo-wide. Only this
package depends on xlsx now, so the protection goes back to its default. A
forced re-resolution of all 2484 packages passes with it enabled and leaves
the lockfile byte identical.
- Connecting with an invalid url used to return { error } from the wrapper
instead of a socket, so the next send() threw 'wsc.send is not a function'
and nothing was ever logged. The failure is now reported in the log.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq
* fix(websocket-tester): make connection errors readable and normalize the url
Both from review feedback on the pull request:
- The log showed 'Error: [object Event]' for a failed connection, because the
native onerror handler receives a bare Event whose reason the websocket spec
deliberately withholds. formatWebSocketError() turns it into 'connection
failed', keeps the message of a real Error, and stringifies anything else.
The old client had the same flaw, but this pr claims to report connection
failures in the log, so it should actually report something.
- buildWebSocketUrl() now trims a trailing slash, so 'ws://host/' produces
'ws://host/?token=...' rather than 'ws://host//?token=...'. This is a
deliberate deviation from the previous client, which concatenated blindly.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq
---------
Co-authored-by: Claude <noreply@anthropic.com>
|
||
|
|
5e4972e285 |
chore(deps): replace the five deprecated packages from the dependency dashboard (#557)
* test: extract testable services and pin current crypto behaviour Move the hashing, hmac, crc and ULA logic out of the single file components into service modules next to them, and cover them with characterization tests that pin the exact digests, encodings and ciphertexts the tools produce today. The encryption tool had no tests at all; it now has round trip coverage for every algorithm plus pinned ciphertexts for the deterministic ones, including OpenSSL salted payloads produced by previous versions of it-tools. No behaviour change: this is the reference point the dependency replacements that follow have to reproduce exactly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * chore(deps): replace the five deprecated packages flagged by renovate Renovate's dependency dashboard lists five deprecated or replaced packages; this removes all of them, keeping the observable behaviour identical. - crypto-js -> crypto-es. Upstream discontinued crypto-js; crypto-es is its maintained ESM/TypeScript successor and is byte for byte compatible, which the characterization tests added in the previous commit verify: the same 1012 assertions pass before and after the swap, including the OpenSSL salted ciphertexts of the encryption tool. It ships its own types, so @types/crypto-js goes away too. - plausible-tracker -> @plausible-analytics/tracker, the official replacement. The app keeps providing the same 'plausible' injection shape, so nothing downstream changes. apiHost maps onto the new endpoint option and keeps posting to the very same url, trackLocalhost onto captureOnLocalhost, and the pageviews that enableAutoPageviews() used to start are now captured by init() itself. init() throws without a domain, unlike the old tracker, so an enabled but domain-less config now falls back to the no-op instance instead of breaking the app bootstrap. - svg2png-wasm -> @resvg/resvg-wasm, the replacement named in its deprecation notice. The renderer moves into a service covered by tests that rasterize real svg content, and the 2 MB binary no longer has to be committed under public/: vite emits it from the package as a hashed asset, so it can never drift from the js glue on upgrade. - @types/bcryptjs and @types/uuid are deprecated stubs, bcryptjs and uuid having shipped their own types for a while. Also drops the now dead renovate rules that only existed to keep uuid and @types/uuid in lockstep, and fixes the tool metadata a new guard test caught: the encryption tool advertised 'crypto-s' and the wysiwyg editor still advertised monaco and prettier. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * test: pin that svg text is actually drawn, document the load bearing empty iv The resvg swap is pixel identical to svg2png-wasm for shapes and gradients, and it also fixes text that names the embedded Roboto family: svg2png-wasm returned an empty canvas there, so the assertion guards a real improvement rather than only the image dimensions. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq * fix: address review feedback on the plugin and renderer initialization Two of the review comments are real regressions against the behaviour the replaced packages had, so both are fixed with a test that fails without the fix: - The plausible plugin called init() on every install. init() throws on the second call, so installing the plugin on a second app instance (tests, hot reload) would have taken the app down, where the old tracker was happy to be constructed repeatedly. The tracker is now initialized once and reused. The api host also gets its trailing slash trimmed so the endpoint cannot end up with a double slash. - initializeSvgRenderer() memoized the initialization promise including its rejections, so one failed wasm download left the tool broken until a page reload. The old code only latched its flag after a successful load. A failed attempt is no longer cached. Also extends the tool metadata guard to the removed stub type packages, and pins the negative counters that verifyHOTP walks through when the window is wider than the counter: their hexadecimal form keeps the minus sign, which the hex parser reads as ffffffff rather than rejecting, and crypto-es reproduces that exactly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf5V2jMpFFXxGVXZU5rHBq --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
8b7bc0a650 |
fix(docker): run on read-only filesystems, IPv6-less hosts and cpu-limited containers (#556)
Five fixes to the Docker image, found while running it-tools on OpenShift, where containers run as an arbitrary UID. No application code is changed. Start on a read-only filesystem. `docker run --read-only` and Kubernetes readOnlyRootFilesystem crash-loop the container, because 20-envsubst-on-templates.sh checks its output directory with `[ ! -w $dir ]`. That only reads permission bits, so a read-only mount passes the check, the write fails with EROFS and `set -e` stops the entrypoint. 19-skip-envsubst-if-readonly.envsh now tests the directory with a real write and, on failure, points NGINX_ENVSUBST_TEMPLATE_DIR at a missing path so the envsubst script exits early. That is only safe if the config in the image is already correct, and today it is nginx's stock welcome config, so the Dockerfile renders the template at build time as well. Writable setups are unchanged: the write test passes, nothing is exported and the config is rendered at startup as before, so a custom $PORT still works. Skip IPv6 when the host has none. nginx.conf always listens on IPv6, so where IPv6 is off nginx fails with `socket() [::]:8080 failed (97: Address family not supported by protocol)`. 25-remove-ipv6-listen-if-unavailable.sh comments those lines out, using the same /proc/net/if_inet6 check as nginx's own 10-listen-on-ipv6-by-default.sh, and exits at once when IPv6 works. It probes the directory before editing, because `sed -i` rewrites through a temporary file there, so a writable file in a read-only directory is not enough, and it tolerates a failed edit so it can never stop the entrypoint. Match workers to the cpu limit. `worker_processes auto` counts the host's cores, not the container's cpu limit, so the image starts 256 workers on a 256-core host in any container size. `docker run -m 192m` is enough to be OOM-killed at startup. Setting NGINX_ENTRYPOINT_WORKER_PROCESSES_AUTOTUNE enables the script nginx already ships. Containers without a cpu limit keep one worker per core. This is the only change that affects a deployment that works today. Return 404 for missing assets. All paths fall back to index.html, so a missing build file returns 200 and text/html, and the browser reports a confusing MIME error instead of a 404. /assets/ now skips the SPA fallback. Sub-folder requests such as /it-tools/assets/... still match `location /`, so those deployments do not change. Stop remapping js. nginx.conf includes mime.types, which already maps js, then maps it again, so every startup logs a duplicate extension warning. mime.types has no entry for mjs, so mjs stays and js goes. Signed-off-by: Sebastian Danielsson <sebastian.danielsson@proton.me> |
||
|
|
69f508442c | Optimize the Chinese translationUpdate zh.yml (#549) | ||
|
|
c82794af62 | Update FUNDING.yml to include Buy Me a Coffee | ||
|
|
07102a6128 |
Fix French translations in fr.yml (#551)
* Fix French translations in fr.yml * Refine French translations in fr.yml Updated various French translations for clarity and accuracy. |
||
|
|
04cfee6f3e |
feat: add i18n internationalization for memo and cheatsheet (#552)
* feat(git-memo): add i18n support and Chinese translation - Dynamically load locale-specific markdown content - Add comprehensive Chinese translation for git memo - Apply theme-aware styles for tables and links * feat(git-semantic-commit-memo): add i18n support and table styling Load memo markdown dynamically based on locale, add Chinese translation, and apply theme-aware styles for tables and links. * feat(jq-memo): add i18n support and Chinese memo Support multiple languages for the jq memo tool by dynamically loading locale-specific markdown files based on the current i18n locale, and add the Chinese translation (jq.zh.md). * feat(jsonpath-memo): add i18n support for memo component Dynamically load localized markdown files based on the current locale, falling back to the default English memo. * feat(markdown-cheatsheet): add i18n support with Chinese content Load locale-specific memo content dynamically using glob import and provide the Chinese translation for the Markdown cheatsheet. * style(markdown-cheatsheet): add table and link styling Add borders, padding, and collapse for tables, and set link color using theme variables. * feat(nano-memo): add i18n support and table/link styling - Dynamically load locale-specific content markdown based on the current language - Add Chinese translation content file - Apply theme-aware border and link colors for tables and links * feat(nginx-memo): add i18n support and styling improvements - dynamically load localized content based on current locale - add Chinese (zh) translation for nginx memo - add table and link styling using theme variables - fallback to default content if localized version is missing * feat(powershell-memo): add i18n support and Chinese translation Load localized Markdown content based on the current locale, falling back to the default English version. Include the complete Chinese translation file. * feat(sed-memo): add i18n support and zh docs * feat(tmux-memo): add i18n support and Chinese translation - Dynamically load locale-specific markdown content - Add Chinese translation (tmux-memo.content.zh.md) - Fall back to default content if locale file not found * feat(vim-memo): add i18n support and zh content - Implement dynamic locale-based content loading - Add comprehensive Chinese translation file - Update styles for tables and links using theme variables * feat(xpath-memo): support locale-based markdown loading Load the appropriate markdown file based on the current i18n locale, falling back to the default when a localized version is not available. * feat(zellij-memo): add i18n support for memo content Load locale-specific markdown files dynamically based on the current language setting, falling back to the default when a translation is unavailable. * feat(chmod-memo): add i18n support and Chinese docs - load locale-specific markdown via dynamic imports - add chmod.zh.md with detailed Chinese documentation - fall back to default chmod.md if no locale match * feat(screen-memo): add i18n support with Chinese translation Add dynamic locale-based markdown loading for the Screen Memo tool and include the complete Chinese (zh) translation. * feat(regex-memo): add i18n support with Chinese translation Load locale-specific markdown content dynamically based on the selected language. |