chore(deps): update dev dependencies (major) - #823
Merged
Conversation
TS 6.0.3 changes (from the renovate major bump) deprecate and remove
several options the project was using. Migrating to the modern
equivalents and dropping redundant settings while we're in here.
Required for the build to pass under TS 6:
- Drop `baseUrl` from libs/tsconfig.base.json, packages/tsconfig.base.json,
tsconfig.eslint.json, and docs/tsconfig.json. TS 6 turns the existing
deprecation into a hard error. Since TS 5.0+, `paths` resolves relative
to the tsconfig file's directory without baseUrl.
- Prefix path entries with `./` (TS 6 requires path values without
baseUrl to be explicitly relative).
- In docs/tsconfig.json, rewrite paths so they're relative to docs/
(the previous baseUrl was "..", so each path string was anchored
at the repo root; now they need `../` prefixes).
Modernization layered on top:
- Add `verbatimModuleSyntax: true` to both base configs. Forces
`import type {}` for type-only imports; what you write is what
ships. Codebase already uses type-only imports consistently — no
code changes needed. Supersedes `isolatedModules`, which is now
dropped from packages base.
- Add `noUncheckedSideEffectImports: true` to both base configs.
Catches typo'd side-effect imports (e.g., `import "react-domz"`)
that today silently noop.
- Drop `forceConsistentCasingInFileNames`. Became the implicit default
in TS 5.0; the option is no longer meaningful.
- Drop `allowSyntheticDefaultImports` from packages base. Redundant
with `esModuleInterop: true`, which implies it.
- Drop `allowJs` from packages base. No `.js` files exist in any
`libs/*/src` or `packages/*/src`; removing skips the JS scanner.
docs/tsconfig.json audit:
- Remove deprecated `@rotorsoft/act-sse` path + include (functionality
moved to the `@rotorsoft/act-http/sse` submodule, which is already
referenced).
- Add missing libs that docs prose references but were never wired up:
`@rotorsoft/act-diagram`, `@rotorsoft/act-pino`, `@rotorsoft/act-tck`.
- Keep `@rotorsoft/act-http/webhook` and `@rotorsoft/act-http/sse`
subpath entries — those are the canonical surface (`act-http` has
no root export, only the two subpaths).
`erasableSyntaxOnly` deferred — would require refactoring ~16 sites
of constructor parameter properties in act/src/{types/errors,act,
adapters/in-memory-store}.ts and act/src/internal/{correlate-cycle,
settle}.ts. Mechanical but mid-size; tracked as a follow-up.
Coverage: 100% statements / 100% branches / 100% functions / 100% lines.
…ties
TypeScript 6's `erasableSyntaxOnly: true` (added to libs/tsconfig.base.json
on this branch) bans three non-erasable constructs: enums, value-bearing
namespaces, and constructor parameter properties. The codebase used the
third in 27 sites across 8 files; this refactor converts each to an
explicit field declaration + constructor body assignment.
Why erasableSyntaxOnly is on the libs base:
- Node 22.6+ ships `--experimental-strip-types`. It refuses to run
files with non-erasable syntax because it strips types rather than
compiling them — there's no place for the auto-synthesized fields
or sequencing constructor assignments to go. The compiled output
has lines the source doesn't.
- Type-strippers like tsx and swc skip ahead a few microseconds per
file when nothing has to be synthesized from constructor signatures.
- Every field a class has is now declared in one obvious place. No
hidden side-channel where reading a constructor signature reveals
invisible state.
Convention adopted while we were renaming everything (added to CLAUDE.md):
- Private/protected fields: `_snake_case` with underscore prefix
(matches the existing `_drain_controllers`, `_reactive_events`).
- Public fields: plain snake_case, no prefix.
- Constructor parameter names stay camelCase (they're the external
call surface); the field rename to `_snake_case` happens on the
assignment line inside the body.
Renamed private fields:
CorrelateCycle:
registry → _registry
staticTargets → _static_targets
hasDynamicResolvers → _has_dynamic_resolvers
cd → _cd
onInit → _on_init
SettleLoop:
deps → _deps
defaultDebounceMs → _default_debounce_ms
DrainController:
deps → _deps
LruMap:
_maxSize → _max_size
Public fields (errors.ts, InMemoryStream, Act.registry) kept their
names as-is, just moved out of the constructor signature into
explicit declarations.
Also drops a TS `enum` in test/builder-type-explosion.spec.ts (Zod
`z.enum(...)` doesn't need a runtime enum) — replaced with a `const`
object. Same shape, fully erasable.
One test reference (`act.spec.ts` poking at `_correlate.staticTargets`)
updated to the new `_static_targets` name.
Coverage: 100% statements / 100% branches / 100% functions / 100% lines.
|
🎉 This PR is included in version @rotorsoft/act-v1.5.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
4 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
May 30, 2026
# [@rotorsoft/act-v1.5.1](https://github.com/rotorsoft/act-root/compare/@rotorsoft/act-v1.5.0...@rotorsoft/act-v1.5.1) (2026-05-30) ### Bug Fixes * **docs:** docusaurus deploy — jsx flag + drop dead act-sse references ([ae68f30](ae68f30)), closes [#823](#823)
|
🎉 This PR is included in version @rotorsoft/act-diagram-v1.0.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^20.5.3→^21.0.2^20.5.3→^21.0.2^5.2.0→^6.0.2^9.2.1→^10.0.0^16.4.0→^17.0.5^5.9.3→^6.0.3~5.9.3→~6.0.3^7.3.3→^8.0.14Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v21.0.2Compare Source
Bug Fixes
v21.0.1Compare Source
Note: Version bump only for package @commitlint/cli
v21.0.0Compare Source
BREAKING CHANGES
Co-authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com
20.5.3 (2026-04-30)
Note: Version bump only for package @commitlint/cli
20.5.2 (2026-04-25)
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v21.0.2Compare Source
Note: Version bump only for package @commitlint/config-conventional
v21.0.1Compare Source
Note: Version bump only for package @commitlint/config-conventional
v21.0.0Compare Source
BREAKING CHANGES
Co-authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com
20.5.3 (2026-04-30)
Note: Version bump only for package @commitlint/config-conventional
vitejs/vite-plugin-react (@vitejs/plugin-react)
v6.0.2Compare Source
Allow all options in reactCompilerPreset (#1189)
This is a type only change. Only
compilationModeandtargetoptions were available forreactCompilerPreset.v6.0.1Compare Source
Expand
@rolldown/plugin-babelpeer dep range (#1146)Expanded
@rolldown/plugin-babelpeer dep range to include^0.2.0.v6.0.0Compare Source
open-cli-tools/concurrently (concurrently)
v10.0.0Compare Source
💥 Breaking Changes
Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.
It's now possible to
require(esm). See here for interoperability.The colors used to default to
reset(which does nothing). Concurrently now automatically selects a color, out of the box.The list of colors used is not jarring nor carries semantic meaning, and reads well in both dark and light terminal backgrounds.
--name-separator: use commas instead.killOthers: usekillOthersOninstead.✨ New Features
#ff0000.bold) - #450rgb(),hex(),bgRgb(), etc) - #578bg#RRGGBB- #578--shellCLI flag/shellAPI option - #288, #589, #556concurrently distinguishes between cmd.exe, powershell, and POSIX-based shells.
[{color}{name}{/color}]- #583, #587🐛 Bug fixes
It should now also be possible to run commands like
"/some/command" foo bar"🔐 Security
shellquote- #591Other changes
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.2.1...v10.0.0
lint-staged/lint-staged (lint-staged)
v17.0.5Compare Source
Patch Changes
1f67271- Correctly set the--max-arg-lengthdefault value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.v17.0.4Compare Source
Patch Changes
#1788
f95c1f8- Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:<file>it is staged withgit add <file>, and then committed withgit commit<file>it is committed withgit commit --allwithout explicitgit add<file>it is committed withgit commit <pathspec>without explicitgit addThere's new test cases which actually setup the Git
pre_commithook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.v17.0.3Compare Source
Patch Changes
06813f9Thanks @iiroj! - Fix lint-staged behavior when implicitly committing files without usinggit addby either:git commit -am "my commit message"where-a(--all) means to automatically stage all tracked modified and deleted filesgit commit -m "my commit message" .where.is an example of a pathspec where matching files will be stagedv17.0.2Compare Source
Patch Changes
88670caThanks @iiroj! - Enable immutable GitHub releasesv17.0.1Compare Source
Patch Changes
4a5664bThanks @iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.v17.0.0Compare Source
Major Changes
#1745
e244adfThanks @iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!#1676
0584e0bThanks @outslept! - Lint-staged now tries to verify the installed Git version is at least2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!#1745
2dcc40aThanks @iiroj! - The dependencyyamlis now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:If you're using
.lintstagedrcas the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to.lintstagedrc.jsonto avoid needing to installyaml.Minor Changes
#1748
809d5efThanks @iiroj! - Add new option--hide-allfor hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.#1759
f13045aThanks @iiroj! - Update dependencies, includingtinyexec@1.1.1to fix the following issues:#!/usr/bin/env nodeshebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the onewhich nodepoints to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.nodeexecutable available inPATHis a symlink pointing to Snap itself. The sandboxing features of Snap prevented lint-staged from spawning scripts with the#!/usr/bin/env nodeshebang, because it meant lint-staged tried to spawn Snap via the symlink. This resulted in anENOENTerror when trying to runprettier, for example. Now, since the realnodeexecutable's directory is available in thePATH, lint-staged will instead spawn the script with the realnodebinary succesfully.#1761
d3251b1Thanks @iiroj! - Lint-staged now runsgit update-index --againafter running tasks, instead ofgit add <originally staged files>. This should improve compatibility when using non-default indexes, for example when committing with a pathspecgit commit -m "message" .instead of adding files to the index.#1745
a9585acThanks @iiroj! - Removecommanderas a dependency and use the built-inparseArgsfromnode:utilto parse CLI flags.Patch Changes
#1755
c82d30bThanks @iiroj! - All tests now pass on the Bun runtime (latest).#1750
a401818Thanks @iiroj! - Remove manual handling forgit stash --keep-indexresurrecting deleted files, because the issue was fixed in Git2.23.0and lint-staged requires at least Git2.32.0.#1771
c4b8936Thanks @iiroj! - Fix documentation about multiple config files and the--cwdoption. When using it, all tasks will be run in the specified directory. For example, to run everything in the actualprocess.cwd(), uselint-staged --cwd=".".microsoft/TypeScript (typescript)
v6.0.3: TypeScript 6.0.3Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
vitejs/vite (vite)
v8.0.14Compare Source
Features
Bug Fixes
Miscellaneous Chores
Code Refactoring
Tests
v8.0.13Compare Source
Features
onEnd(#22357) (47071ce)Bug Fixes
write=false(#22328) (158e8ae)name/originalFileNamein syntheticassetFileNamescall (#22439) (8e59c97)isBundledper environment (#22257) (a576326)Miscellaneous Chores
v8.0.12Compare Source
Features
Bug Fixes
rolldownOptionsinstead of deprecatedrollupOptionsin messages (#22400) (b675c7b)build.targetto worker bundle (#22404) (3c93fde)Miscellaneous Chores
v8.0.11Compare Source
Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
Tests
v8.0.10Compare Source
Features
Bug Fixes
hmrClient.logger.debugandhmrClient.logger.errorlooked different from other HMR logs (#22147) (a4d828f).css?inline(#22292) (83f0a78)Code Refactoring
v8.0.9Compare Source
Features
Bug Fixes
watchChangehook (#22188) (fc08bda)?rawimports (#22148) (3ec9cda)Documentation
Miscellaneous Chores
v8.0.8Compare Source
Features
Bug Fixes
dns.getDefaultResultOrdertemporary (#22202) (15f1c15)v8.0.7Compare Source
Bug Fixes
v8.0.6Compare Source
Features
Bug Fixes
Performance Improvements
getLocalhostAddressIfDiffersFromDNSwhen DNS order isverbatim(#22151) (56ec256)Miscellaneous Chores
v8.0.5Compare Source
Bug Fixes
server.fsafter stripping query as well (#22160) (a9a3df2)v8.0.4Compare Source
Features
Bug Fixes
hasBothRollupOptionsAndRolldownOptionsshould returnfalsefor proxy case (#22043) (99897d2)vite/modulepreload-polyfill(#22126) (17330d2)#(#22038) (3460fc5)Documentation
environment.fetchModuledocumentation (#22035) (54229e7)Miscellaneous Chores
Code Refactoring
v8.0.3Compare Source
Features
Bug Fixes
metaidentifier insideimport.metawhen a binding namedmetaexists (#22019) (cff5f0c)Miscellaneous Chores
Tests
getCssFilesForChunk(#22016) (43fbbf9)v8.0.2Compare Source
Features
Bug Fixes
Miscellaneous Chores
v8.0.1Compare Source
Features
Bug Fixes
Miscellaneous Chores
Code Refactoring
Tests
v8.0.0Compare Source
Today, we're thrilled to announce the release of the next Vite major:
⚠ BREAKING CHANGES
import.meta.hot.acceptresConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.